Migrating from Spector CNE

It is possible to migrate from Spector CNE to Spector 360 and, if you have been using Version 4.3 or later, add your existing CNE Data Vault(s) to the Spector 360 Database. Spector 360 will require installation of its own network Server Components and registration of its own serial number.

Before making the change from CNE to 360, decide whether you want to install Spector 360 over your current Spector CNE installation or on a separate computer.

To install Spector 360 on a separate computer:

1. Check the requirements.
   Make sure the new computer can handle all Server Components and databases.  

2. Install all Spector 360 components.
   Follow instructions in Installing Spector 360 to install Server Components and a Dashboard on the new computer.

3. Complete the Post-Setup Tasks.
   See the instructions below.

To install Spector 360 over your current CNE installation:

1. Check the requirements.
   Make sure your existing computer(s) can handle all Server Components and databases in addition to existing CNE Data Vaults.  

2. Back up your Spector CNE Data Vault.
   Even though the Spector 360 Setup does not overwrite the data, copy or move the C:\SpectorData folder (may have another name in your installation of Spector CNE) and its subfolders to another location for safety.  The Import Utility will allow you to point to the new location and import or use existing folders for Screen Snapshot and Email Attachment files.

3. Install all Spector 360 Components.
   Follow instructions in Installing Spector 360. You do not need to uninstall Spector CNE first.
   
   
    

4. All Spector Server components will be replaced:  
   Spector 360 Databases (with Microsoft SQL Server)
   a new Control Center
   a new Primary Server (Spector 360 registration required)
   a new Data Vault Service
   the Dashboard, which will be your "viewer"
   the Import Utility, which allows you to import Spector CNE 4.3 (or higher) data into a Spector 360 Database

5. Configuration files are preserved.
   The following files are preserved and can be reused for Spector 360 clients:
   Client configuration (.ini) files
   Network configuration (.xml) files
   These files can be used by the new Spector 360 installation, saving you work in setting up Clients. Data Vault data (C:\SpectorData folder and subfolders)

6. Your existing Data Vault is preserved.
   When the installation is complete, you can run the Import Utility to populate the new Spector 360 Database with your existing Spector CNE data.

7. Complete the Post-Setup Tasks.
   Follow the instructions below.

To deploy Spector 360 on your network:

1. Import Spector CNE data.
   If you have a Spector CNE Data Vault (version 4.3 or higher), run the Import Utility to populate your Spector 360 database with existing data. Do this before installing new Clients. See Running the Import Utility.

2. Add Computers to the Control Center.
   Open the newly installed Spector 360 Control Center and add Client Computers to the Manage Computers view using your existing netconfig.xml file. See the Spector 360 Administrator's Guide for help.

3. Build a new Client Install file.
   From the Control Center, run the Deployment Utility to build a Spector 360 Client Install file.  Use your existing .ini Client settings file, if you wish, but be sure to step through the Deployment Utility carefully as settings have changed.

4. Re-install the Client.
   At first, install only on select network computers to begin testing Spector 360. There is no need to uninstall CNE Clients before installing the 360 Client.

5. Login to the newly installed Dashboard.
   Use the SA login to view imported and Spector 360 recorded data from the Spector 360 Database. Make sure you review all Post-Setup Steps. To learn more about the Dashboard, see the Spector 360 Dashboard Guide.

6. Complete the migration.
   When you have confidence that the Spector 360 installation is recording and the Dashboard is displaying the recordings, import additional Data Vault data that has accrued.  Install the Spector 360 Client on remaining network Client computers.

Related Topics. . .