This article describes how to move Control to a new server. This only applies to a standard Control configuration: 1 database, 1 SSLIP.

1. What version of Control is installed on the existing server?
   • In Control, go to the Help menu at the top of the screen and click About Control to find the version. Alternatively, you can right-click on the Control.exe file and choose Properties, then look at the Details tab to get the version.
   • You want to install the same version of Control onto the new server. While it may seem advantageous to use the server swap as an opportunity to upgrade Control, it's best to avoid doing this. Upgrade Control before or after the server swap.
2. What version of SQL Server is installed on the existing server?
   • Is it SQL Express or a paid version such as SQL Standard or Enterprise?
   • You want to install the same version of SQL Server on the new server, or a newer version.
   • A full Control installation on the new server will install SQL Server Express. This is the recommended way to install SQL Server as the instance will be automatically configured for you.
   • The installer for Control 4.6 includes SQL 2008 R2, while the installer for the current version of Control 5.6 contains SQL 2012.
   • If a paid version of SQL Server is getting installed on the new server, that should be installed before Control by following steps 4 and 5 from this article: Control 5.1 Manual Installation#x-Explanation-Step%204%20-%20SQL%20Server.
3. Are there any custom reports? If so, they must be moved to the new server.
   • Custom reports are typically on the server PC in a folder called Reports (which is within the Control program folder)

1. Follow these instructions to install Control on the new server. These instructions work for all versions of Control 5.x:
   • Control1 - New Control 5.5 Server Install
2. If you are using Control 4.6 or earlier, first upgrade Control to the latest version, then follow the instructions from the above link.
   • Control1 - Upgrade Version 4.6 to 5.5
3. Ensure you are able to log into Control on the new server before proceeding. You will need to shut down the SSLIP on the existing server before you can run it on the new server.

1. Make sure everyone logs out of Control and the SSLIP is shut down on both servers, and stop all associated services on the old server (Chapi, CDAS, Homegate, ect.)
2. On the old server, launch SQL Server Management Studio.
3. Log into the local SQL instance that hosts your Control database (it is usually called Cyrious). You should be able to log in using Windows Authentication.
4. Expand the Databases folder.
5. Right-click on the Control database (usually called StoreData) and choose Tasks > Back Up…
6. In the backup window, remove any existing files listed in the destination box, then add a destination path and file for your backup. It's best to use the .bak extension for the backup.

1. Click OK and wait for the backup to complete.

1. Transfer the backup file created above to your new server PC.
2. Open SQL Server Management Studio.
3. Log into the local SQL instance used for Control (usually called Cyrious). You should be able to log in using Windows Authentication.
4. Expand the Databases folder.
5. Right-click on StoreData and choose Delete. Click OK in the window that pops up to delete the database.
6. Right-click the Databases folder and choose Tasks > Restore > Database…
7. In the Source section, choose Device, then click the button to the right to select your .bak file.

1. Click on Files on the left and ensure both of the files get restored to the Control program folder (usually C:\Program Files (x86)\Cyrious\Control).
2. The data file should be named StoreData.mdf and the log file should be named StoreData.ldf.

1. Click OK to restore the backup.

1. If there were any custom reports, move them to the new server. They should get placed in a Reports folder within the Control program folder (typically C:\Program Files (x86)\Cyrious\Control). If the Reports folder doesn't exist yet, create it.
2. Put all the report files into the Reports folder.
3. If they are using Document Management, this will need to be adjusted. If migrating files to a location on the new server, don't forget these.

1. Important! - Be sure SSLIP, CHAPI, HomeGate and CDAS are all shut down and disabled on the old server before starting them on the new server.
2. On the new server, run SSLIP.exe.
3. Once the SSLIP starts, verify you can log into Control. You should see the familiar list of users in the login drop-down box as the data has now been restored on the new server.
4. Do not proceed until you can log into Control successfully on the new server and you can see that you have the data that was backed up from the old server.

1. On the old server, go to Control Panel > Programs and Features and uninstall Cyrious Control.
2. If SQL Server will no longer be used on the old server, go to SQL Server Configuration Manager and set the SQL instance startup type to Disabled.

1. A customer that had our shipping module will need that repathed to the new server.
2. A customer using Production Terminal would need that set up on the new server as well.

On each Control client PC:

1. Right-click the Control shortcut and select Properties.
2. In the Target box, the path should look something like this: \\servername\cyrious$\Control\Control.exe
3. The servername part will be the name of the old server. Change it to the name of the new server. For instance, if the new server's name is CyriousServer, the full path should be \\CyriousServer\cyrious$\Control\Control.exe.
4. If there is anything in the Start In field, change the server name there to the name of the new server also. (Note: the Start In box is typically the same as the Target box, except without the Control.exe at the end)
5. Verify you can log into Control from the client PCs.