System > Migrate VSA
Show me an explanation of the items on this page.
How do I copy/move accounts from one server to another?
The Migrate VSA function allows administrators to copy client machine accounts from one server to another. The function is initiated on the target machine (new server) and copies client machine accounts from the old server to the new one. To original account is left on the old server.
Note: The VSA connects directly to the MS-SQL server on the remote VSA. The MS-SQL port on the remote VSA must be open. Microsoft uses port 1433 as the default for MS-SQL.
To copy client machine accounts, follow these steps from the new server:
Enter the IP address or hostname of the source (old) machine in the Remote Server field.
Enter Master Administrator login name in the Master Admin field.
Enter the administrator password in the Password field.
Select the number of client machine accounts and administrators you would like to view after the accounts are obtained from the source server by using the Rows/Page dropdown menu. The choices are 10, 30, and 100.
Press connect. The Group ID list box, Machine.Group ID and Assigned Admin columns populate with the groups, client machines, and administrators, respectively, from the source server.
In the Group ID list box, select the group whose client machine accounts you would like to view. The client machine accounts of the group are displayed in the Settings column. If <All Groups> is displayed, all client machine accounts are displayed in the Settings column.
In the Machine.Group ID column, select the checkboxes next to the client machine accounts you would like to copy to the target server. To select all available client machine accounts, click Select All.
In the Assigned Admin column, select the administrator accounts you would like to copy to the target server. All administrators, master and standard, with an account on the source server are displayed. To select all available administrator accounts, click Select All.
Select Overwrite Duplicate Data if you would like to overwrite the accounts on the target Server with the same client machine accounts and administrators.
Select Copy Public Scripts and Reports if you would like to import all public scripts and reports from the remote VSA.
Press Copy.
After the accounts have been copied from the source Server to the new target Server, they must be edited on the new Server to update the KServer's hostname / IP address.
On the new target Server, select the Agent tab.
Click on the Check-In Ctl function.
Enter the hostname or IP address of the new server in the Primary KServer text edit field.
Enter the hostname or IP address of the new server in the Secondary KServer text edit field.
Select All Groups in the Group ID filter in the Specify Accounts area below the function tabs.
Click Select All to check the boxes beside every managed machine.
Click the Update button.
Finally, configure the Agents to check in to the new target Server.
On the old source Server, select the Agent tab.
Click on the Check-In Ctl function.
Enter the hostname or IP address of the new server in the Primary KServer text edit field.
Select All Groups in the Group ID filter in the Specify Accounts area below the function tabs.
Click Select All to check the boxes beside every managed machine.
Click the Update button. Upon the next check in to the old source server, the Agents will receive the new server's address as the primary KServer. Subsequently, the Agent will check in to the new server.
How do I re-install a Kaseya VSA server on another Windows server and maintain all of the existing managed machine data?
The following procedure should be followed when you have installed a Kaseya VSA server on a new Windows server and you wish to copy all of the machine data to the new server. This procedure assumes that the new server will be a replacement for the old server and that it will take the external hostname / IP address of the old server. If your new server will have a different external hostname or IP address, refer to the section below. This procedure may also be used if you are upgrading the operating system or the SQL server on your current server.
Log in to your current VSA server as a master administrator.
Select the System tab.
Click on the Server Info function.
Click the Backup Now button. An SQL database backup will run within the next two minutes.
To confirm the completion of the database backup, locate the SQL database backup file named <Kaseya_Installation_Directory>\UserProfiles\@dbBackup\ksubscribers_db_yyyymmddhhmm.BAK. By default, the <Kaseya_Installation_Directory> is c:\Kaseya\. The yyyymmddhhmm portion of the filename contains the current year, month, day, hour, and minute of the database backup.
Copy the entire directory <Kaseya_Installation_Directory>\UserProfiles\ to your new server. This directory contains the files associated with your managed machines.
With the exception of the subdirectory VSAHiddenFiles, copy the entire directory <Kaseya_Installation_Directory>\WebPage\ManagedFiles\ to your new server. This directory contains the scripts and managed files belonging to each administrator.
WARNING: Do not copy VSAHiddenFiles from an old system to a new system. This directory contains many system helper files. Your new system installation contains the latest versions of these files.
If you are re-installing the operating system or SQL server on this same Windows server, then save the directories in Steps 6 and 7. After re-installing the server and VSA, copy back the two directories.
Log in to your new VSA server as a master administrator.
Select the System tab.
Click on the Server Info function.
Click the Restore button.
Select the link containing the date of the SQL database backup from the list that matches the backup created in Step 5. Click the Restore button to confirm the database restore operation.
After the database restore completes, you will have to log back in to the VSA server using one of the original administrator accounts.
If necessary, set the external name or IP address of the new server to match the server that you have replaced by selecting the System tab and clicking on the Server Info function.
What if I am putting the new server at a different IP address or external hostname?
Prior to shutting down the existing VSA server, you will need to configure the Agents to check into the new VSA server’s IP address or external hostname if it will be different.
Log in to your current VSA server as a master administrator.
Select the Agent tab.
Click on the Check-In Ctl function.
Enter the hostname or IP address of the new server in the Primary KServer text edit field.
Enter the hostname or IP address of the current server in the Secondary KServer text edit field.
Select All Groups in the Group ID filter in the Specify Accounts area below the function tabs.
Click Select All to check the boxes beside every managed machine.
Click the Update button.
The new settings will appear in red at first. Once an Agent has checked in and received the new setting, it will be displayed in black again. Wait for all machines to check in and receive the updated check in configuration before taking the current server offline.
Explanation of items on this page
Migrate allows administrators to switch servers without the need for downtime. Administrators setup the system on the new server. Then, using the Migrate function from the new server, they connect to the old server and copy over existing client machine accounts and administrator accounts. Since accounts are copied, and not moved, the administrator must manually delete the accounts from the old server. Otherwise, the accounts are left intact. To ensure that the deployed Agents can find the new server, be sure that the host name/IP address settings are correct, as specified in Server Info.
Note: The VSA connects directly to the MS-SQL server on the remote VSA. The MS-SQL port on the remote VSA must be open. Microsoft uses port 1433 as the default for MS-SQL.
The following elements are displayed in the Migrate VSA function:
Remote Server
The fully qualified host name or IP address of the source server. This is the server that user accounts will be migrated from.
Master Admin
A Master Administrator login name valid on the remote server.
Password
The Master Administrator password that corresponds with the Master Admin field.
Group ID
Shows a list of the group IDs on the remote server. All groups can be selected or multiple groups can be selected by holding down the <CTRL> key while clicking on the group names.
Select/Unselect All
Select All will select all user accounts on all account pages. Unselect All will unselect selected user accounts on all account pages. For individual accounts, select the checkbox next to the machine.group ID.
Initiates the connection to the server specified in the Remoter Server field.
Copy
Starts copying the selected machine accounts from the source server. Hence that it is a copy command; the original accounts are not deleted or moved from the source server.
Overwrite duplicate data
Selecting this checkbox prompts the server to automatically overwrite any duplicate machine accounts on the new server.
Copy Public Scripts and Reports
Selecting this checkbox copies any public scripts and reports from the source server. Otherwise, only private scripts are copied from the remote Server, assuming that the corresponding administrator accounts are also copied.
Shows the client machines according to the group(s) selected in the Group ID list. Check the checkboxes next to the client machine accounts that are to be copied to the new server from the source Server.
Settings and private data
Shows all of the master and standard administrators on the source machine. Private scripts are copied along with the administrator accounts if their corresponding checkbox is selected. Check the checkboxes next to the administrators that are to be copied to the new server from the source Server.