Move kaseya agent tonew server
- #Move kaseya agent tonew server how to#
- #Move kaseya agent tonew server install#
- #Move kaseya agent tonew server windows#
Please edit the SSRS URL from the System > Configure page. NOTE: If you are using SSRS for Reporting, After a restore of a database the SSRS URL may be invalid and need to be reset. NOTE: It has been reported that you may need to restart all your Kaseya services and WWW services (or reboot the server) to complete the process in some cases. One can expect the system to be busy after moving the DB, however, as soon as the new SQL server catches up with its assigned tasks, the performance should be back to normal. If everything is running, the transfer was done with success and the OLD SQL server is history. Verify again if the Kaseya VSA still running.
Before doing this go to this machine and just STOP SQL service on this OLD server. You should see the IP address or machine name for the new SQL server.ġ1) If this is correct, it means that you can turn off the OLD SQL server.
#Move kaseya agent tonew server windows#
Password: This will be your SA account passwordĩ) Click on "Apply" - The system will then connect to the new SQL server and as soon as this is done, the system will be back to normal operating status. Refresh the VSA, and re-login.ġ0) On the server where Kaseya is installed, search for "Reinstall Database Schema" in the Windows Start menu and select this page to begin this process which will load a browser showing a progress bar running through a number of operations and checks. To double check if the transfer has completed 100%, log back in and visit the System > Server Management > Configure page and scroll all the way down.
SA Username - This will be your SA account username The IP address/hostname of the new SQL server This is also known as 'Mixed-Mode Authentication'.Ħ) Now, using the Kaseya VSA, visit the System > Server Management > Configure page.ħ) On this page, click the 'Change DB.' Button. Right click Databases > Restore Databases option.ĥ) Make sure the new backend SQL db-based machine is set to Windows and SQL Authentication. You can do this by using SQL Server Management Studio (SSMS) on the new database server to restore the ksubscribers database. You can do this by clicking "Backup Now" button in the System > Configure page.Ĥ) Copy the database backup file to the database server you wish to connect to - Restore this backup to the new back-end. See the 'More Information' field below for the Management Studio specific to these respective its SQL version installer.ģ) Create a new ksubscribers backup from the old back end.
#Move kaseya agent tonew server install#
ForSQL 2005, update this toSP2 installed (minimum). Make sure the system meets system requirements for the appropriate Kaseya version.Ģ) Install SQL Management Studio in this new back end db-based machine. Have the new backend SQL installation fully patched. Please follow the below process to transfer SQL and the database from one computer to another:ġ) Install SQL using the same collation as the `ksubscribers` database had on your old server.
#Move kaseya agent tonew server how to#
Note: This process describes how to proceed if the VSA admin wants to move the SQL server and the database to a new machine, while leaving the Kserver "frontend" on the original machine. How do I move SQL and the Ksubscribers database to another computer?