Spector CNE
Administrator's Guide
Manage Computers
When installing the Client remotely from the Control Center is impossible or too difficult, you can install the Client Recorder manually at the Client computer. This requires you to physically go to and log into the computer where you will execute the Client Install file.
Before installing the Client, make sure you have:
A Client Install File (built using the Deployment Utility).
A login account with Administrator privileges on the Client computer.
A TCP/IP connection between the Client and Server Components.
|
|
If you use the default Deployment Utility settings, you will get a QUIET installation at the Client computer. No dialog boxes will appear and the computer will automatically restart at the end of the installation. See Quiet vs. Interactive Installation for information about changing the installation. |
To install the Client at the computer:
At the Control Center computer,
navigate to the Client Install file. By default, the file is stored in
C:\Program Files\SpectorSoft\SpectorCNE\ under the
name: spsetup_Settings.sds
Use Windows to rename the file, changing the .sds file extension to an .exe file extension.
Copy this file to a CD, attach it to an email, put it into a shared network folder, or use any other means to gain access to this file from the computer on which you would like to install the Client.
At the Client computer, log in using your Administrator-level account.
Access the Client Install .exe file and run the installation. If you are installing in "Quiet Mode," there may be no prompts or dialog boxes, and the computer will automatically restart. If you have selected user interaction for the install, you will respond to the prompts you have selected. See Quiet vs. Interactive Installation.
When the computer restarts, the Client Recorder is fully installed.
Once a user logs into the computer, the Client will begin recording and will store the recorded events in the Data Vault.
|
|
See Managing in Non-Integrated Mode for further information regarding management of computers that cannot fully communicate with the Control Center. |