When upgrading to Security Commander 2, you need to be aware of the different upgrade paths for SC1.85 and SC1.91. This document applies to upgrades from Security Commander 1.85.
Summary
Before upgrading to Security Commander 2, you will need to know which version of Security Commander you are currently running. This can be found on the 'Help > About' screen within Security Commander. This guide is for upgrades from SC1.85. For upgrades from SC1.91, refer to "Upgrading Security Commmander 1.9 to 2.02". You will need to ensure you have Administrative Rights on the Windows PC prior to upgrading. You will also need to know the existing SQL 'sa' user password.
Procedure
To upgrade from SC1.85, we will need to perform the following tasks:
- Backup the existing Alliance8300, Alliance8300Archive and Alliance8300History databases.
- Backup the Graphics (Maps and Photos).
- Uninstall Security Commander 1.85.
- Uninstall SQL Server 2005.
- Install Windows Installer 4.5 (if using Windows XP).
- Install Security Commander 2.
- Import the 1.85 backup database.
- Update the 1.85 database to 2.02.
- Re-license Security Commander.
- Update Clients (if applicable).
Ensure you have the Security Commander 2.02 Installation (available from www.interlogix.com.au/downloads) and have the License Key previously provided by Interlogix.
1. Backup the Databases
The first, and most important task is to backup your existing databases. Use the Database Maintenance tool (Start > Programs > UTC Fire & Security > Security Commander > DB Maintenance), then select Backup from the top menu.
Figure 1: DB Maintenance tool - Backup form
Enter the 'sa' password, then click Browse to select the location to store the backups. Do not store the backups in the Security Commander program folder, as this will be deleted during uninstallation. The Desktop is an ideal place to store them temporarily.
2. Backup the Graphics Files
As the graphics (i.e: Maps, Photos and Badge Layouts) are not stored in the database, these need to be backed up manually. Simply make a copy of the C:\Program Files\UTC Fire & Security\Security Commander\Images and C:\Program Files\UTC Fire & Security\Security Commander\Badge Designer folders, and place them on the Desktop of other safe location. Note: These file paths may be different, depending on your operating system. The graphics and card layouts may also be stored in another non-default location. Check you system programming to confirm their locations.
Figure 2:Images and Badge Designer Folders
3. Uninstall Security Commander 1.85
From the computers Control Panel > Add or Remove Programs window. Select Security Commander, then select Uninstall.
This will display a prompt with Remove Database and Remove CR9 ticked. Leave Remove Database ticked, but untick Remove CR9 (as we will require this for SC2.02) then select OK.
Figure 3: Uninstall Options
Enter the 'sa' password on the Database Removal tool to confirm the uninstall.
4. Uninstall SQL Server 2005
From the same Add or Remove Programs list, select SQL Server 2005 from the list and select Uninstall. There is no need to remove the other SQL components.
From the SQL 2005 Uninstall window, select the instance called "SPSQL" then continue with the uninstallation. After the uninstallation has completed, reboot the PC.
Figure 4: Uninstalling the SPSQL Instance
5. Install Windows Installer 4.5 (Windows XP only)
If you're using Windows XP, you will need to install Windows Installer 4.5 in order to proceed with the installation. Windows Server 2008, Vista, 7 and 8 already come with compatible versions.
The installer can be found on the installations CD / Download under 'redistr\Microsoft Windows Installer 4.5\WindowsXP-KB942288-v3-x86.exe'. Follow the prompts of the installer and allow the PC to reboot once complete.
6. Install Security Commander 2.x
Follow the instructions included in the 'manuals\SC Installation Manual.pdf' document.
You will select a new installation of an SQL instance when prompted. Do not choose 'existing instance' as we have removed the existing database in step 4 above.
Once complete, you will be prompted to create or upgrade a database. Skip this step by closing the Database Tools window without performing any actions.
7. Import the 1.85 Database
Use the Database Maintenance tool (Start > Programs > Tecom > Security Commander > DB Maintenance), then select Restore from the top menu.
Enter your 'sa' password, then select Browse. Navigate the folder tree and find location of the desktop or other location where the backup files were stored in Step 1. Select the Alliance8300 file, and the Alliance8300History and Alliance8300Archive files should be selected automatically. Press Restore.
Figure 5: DB Maintenance - Restore
Depending on the size of the archives, this may take some time. Do not cancel the operation; you will be shown a 'Database restore successfully completed' message when it is complete.
8. Update the Database to 2.x
Once the import is complete, go directly to the Database Tools application (Start > Programs > Tecom > Security Commander > Database Tools).
Enter your 'sa' password, then select Upgrade Database (middle button). The tool will tell you that is has detected a 1.85 database. Acknowledge this message and the upgrade will commence.
Figure 6: Database Tools - Upgrade Database
Once complete, reboot the PC.
9. Re-license Security Commander
Go to the Start > Programs > Tecom > Security Commander > License Registration application and enter the 'sa' user and password in the Database section.
If you have a registration activation code from a previous registration for this PC, you can use the same code in the Registration section. Otherwise, please contact our Customer Service department to have a new license key issued.
Start up Security Commander and confirm that the system is working.
10. Upgrade the Clients
To upgrade 1.85 clients to 2.x, you will need to uninstall the existing client through Control Panel > Add or Remove Programs
Once complete, install the new client from the SC2.x disc / download. Select Client installation and enter the PC Machine Name of the server PC.
Remember to enter the client PC Name information on the Server and ensure you have enough licenses for the clients. Refer to the SC Installation Manual for further information.
If you have any issues with this procedure, please log a ticket with our Technical Support team.
Comments
0 comments
Article is closed for comments.