Configure

The Configure page manages the configuration of your KServer and related services.

Note: For the latest instructions on migrating an existing KServer to a new machine see the article How do I move my Kaseya Server to a new computer? (270436) in the Kaseya Support Knowledge Base Portal.

Check for Update

Click Check for Update to determine if your KServer is the latest version available. If an update exists, a message alerts the administrator that an update is currently available and is applied at the next master administrator logon. An update is only downloaded if the version currently running is older than the version available. Otherwise, no action is performed.

Version Number

Shows the version number of the system software and the hotfix level of your system.

Warn if the VSA cannot get updates from http://vsaupdate.kaseya.net on port 5721

Check this box to display a warning if your VSA cannot connect to http://vsaupdate.kaseya.net to fetch the latest hotfix checker list, the latest PCI ID list used by audit, or the VSA software update notifications. Your VSA attempts to automatically fetch this information from http://vsaupdate.kaseya.net on port 5721. Verify that port 5721 outbound is not blocked by your firewall.

Warn when the license reaches the maximum number of seats

Check this box to display a warning when the number of machine ID accounts reaches the maximum for your VSA.

Note: Each installed agent counts against your license for 30 days. If you uninstall an agent, it will count against your license for 30 more days.

Hotfixes

Several options affect how hotfixes update your KServer.

Enable automatic check - If checked, your KServer periodically checks for new only hotfixes at http://vsaupdate.kaseya.net. If any new hotfixes are available, the KServer automatically downloads and applies the hotfixes without any user interaction.
Reload - Click to load all hotfixes for the version of KServer your system is running. Checking the Enable automatic check box only checks for new hotfixes.
Get Latest Hotfix - Click to check if new hotfixes are available immediately and, if they are, download and apply them. Otherwise, if the Enable automatic check box is checked, your KServer checks periodically for new hotfixes.
Manually apply hotfixes - If your system is not connected to the internet or can not reach http://vsaupdate.kaseya.net, then click this list.
- Check Now - Click to force the system to check for new hotfixes immediately. If any new hotfixes are available, they are downloaded and automatically applied. Only new hotfixes get loaded.
- Reload - Click to re-download and apply all hotfixes for the version of KServer your system is running.

Database

Click Reapply Schema to reinstall and validate the last database schema that was downloaded using Check for Update. Reapply schema is a safe operation that users can run in an attempt to resolve a variety of problems. Reapply schema:
- Sets default values and runs basic consistency checks on the database.
- Rebuilds all pre-defined Kaseya scripts.
- Rebuilds all pre-defined Kaseya script samples.
- Reschedules default backend processing scripts for the KServer.
  This is all completed without the risk of losing any agent data. This is a good self healing routine to run if you observe:
- Scripts failing in the IF condition or in specific steps.
- Pending alerts not being processed within a two minute interval. You can monitor this using the System > Statistics page. This might indicate a problem with backend processing scripts.
Click Defrag Database to defragment the physical files on your disk arrays. Fragmented SQL Server data files can slow I/O access.
Warning: Do not use the Microsoft SQL tuning advisor against the schema. It adds keys that conflict with the smooth operation of the system.

Reload Samples

Check the Reload sample scripts with every update and database maintenance cycle box to load sample scripts automatically.
Check the Reload sample event sets with every update and database maintenance cycle box to load sample event sets automatically.
Check the Reload sample monitor sets with every update and database maintenance cycle box to load sample monitor sets automatically.
Click Reload Samples to load the latest sample scripts, sample event sets, and sample monitor sets manually.

HTTPS

Automatically redirect to https at logon page (except when accessing via localhost) - If checked, ensures all administrators logging into the VSA remotely use the secure HTTPS protocol.

API

Enable VSA API Web Service - Check to enable the VSA API Web Service.

Invalid Patch Location Notification

Enable Invalid Patch Location Notifications - Microsoft sometimes prepares patches that do not allow the File Source function to download patches successfully. If checked, this option notifies Kaseya that an "invalid patch location" exists for a patch required by any of the managed machines on your system. Notification alerts Kaseya to prepare a valid patch location manually and send it out as an updated patch location override for all customers to use. If blank, no notification is sent to Kaseya. You will still receive updated patch location overrides prepared in response to notifications reported by other customers, regardless of this setting.
Note: Notification sends no customer-specific or machine-specific information to Kaseya.

Backups

Run database backup / maintenance every <N> Days @ <Time> - The KServer automatically backs up and maintains the MS-SQL database and transaction log for you. Click Set Period to set the frequency and time selected. If your KServer is shut down at the scheduled backup time, the backup will occur the next time the KServer goes online. You can enter zero to disable recurring backups.
Backup folder on DB server - Set the directory path to store database backups in. The default directory path is typically C:\Kaseya\UserProfiles\@dbBackup. Click Change to confirm changes to the directory path. Click Default to reset the directory path to its default.
Note: Database backups older than three times the backup and maintenance period are discarded automatically to prevent your disk drive from filling up. For example, if the backup occurs every 7 days, any backup older than 21 days is deleted.
Change DB - Connect your KServer to a database on a different machine by following these steps:
1. Backup your existing database by clicking Backup Now.
2. Copy the database backup file to the database server you wish to connect to.
3. Verify your new database is set to mixed mode authentication.
  - Open the SQL Enterprise Manager.
  - Right click the database and select properties.
  - Click the Security tab.
  - Under authentication, select SQL Server and Windows.
  - Click OK.
4. Verify your KServer is on the same LAN as your new database server and port 1433 is open on the database server.
5. Click the Change DB button.
6. Enter the database location using one of the following formats:
  - computer name
  - computer name\instance name
  - IP address
7. Enter a database logon name. The default logon name is sa.
  Note: This logon is only used to configure the database. The system creates its own database logon to use going forward.
8. Enter the password associated with this logon name.
9. Click Apply. The system then connects to the remote database and configures it.
10. Click Restore to load the data from the back up file you made in step one into your new database.
Backup Now - Initiate a full database backup now. Use this function before you shut down or move your KServer, to ensure you have the latest KServer data saved to a backup. The backup will be scheduled to run within the next 2 minutes.
Restore - Click to restore the KServer's database from a backup file. A file browser displays a list of KServer database backup files you can restore from.