|
|
|
|
|
In this topic: |
The Client
Spector CNE acts in a similar fashion on a multi-user network as it would on a Windows Network. Multi-user networks include Citrix, Novell, or Windows Terminal Services. The biggest potential problem is if the underlying Windows Network isn’t configured properly. If all users are simply assigned a common Windows account, for instance, this could cause issues when attempting to manage Clients using the Control Center. Aside from this one potential issue, the Client records and delivers recordings normally on both a multi-user Server and a Domain.
|
|
SpectorSoft requires Citrix and Terminal Services customers to purchase a license for each user who will be logging in to the server. |
To configure for your network setup:
If the Client computers:
Log on to a workgroup - Spector CNE behaves exactly as if it were in a Windows Workgroup environment. This means that credentials are an issue. See Deploying in Windows Workgroup.
Log on to a domain - Spector CNE acts in a similar fashion on a Novell Network as it would on a Windows Network. Ensure that the Windows user account used to install the Server components is an account that either is in the domain administrator group or is an account that is in the local administrator group of each computer on the network to receive the remote installation. The Windows user account is different from the Novell Network log on account but is managed by the Novell log on procedure.
If all users are assigned a common Windows account, the Control Center will have issues managing the individual computers. For the Control Center to function properly, the current Control Center user managing the computers must be logged in under an account that is a member of the Control Center computer's Local Admin Group and a member of the Admin Group for each Client.
To install the Client on a Terminal Server:
A Spector Client will capture sessions directly from a Terminal Server or Citrix server where the “Full Desktop” is published. Simply install the Client on the server computer, using normal Client installation procedures.
Normal installation considerations apply. For example, if the server happens to be operating on a Windows Workgroup, you need to establish a local Administrator account for the Control Center or use manual Client installation.
The Client records each activity under the login name of the user who performed the activity. This means the Client will capture email, web sites visited, keystrokes, and all other activities for DOMAIN\SALLY, DOMAIN\PETER and DOMAIN\JIM as they use the terminal services, even when activity occurs simultaneously.
The data received and stored by the Data Vault is accessible for viewing “by user.”
Keep an eye on performance and usage. As more users connect and are recorded, the more difficult it becomes for the Client to take Screen Snapshots for each user every 30 seconds. Use Client Settings to reduce frequency of (or disable) Screen Snapshots, or consider disabling other activity recording.
To install the Client on workstations:
If individual applications are published on the server, the Client will NOT capture sessions at the server by user; instead you must install the Client on each workstation to record activity. Install the Client on the workstation computers, using normal Client installation procedures.
