Previous Topic: Limitation of 32-bit Client.msi on 64-bit OSNext Topic: Client Machines - Manual Installations (setup.exe)


Before Installing on Client Machines

Before you install CA DataMinder endpoint agents, note the following issues.

Create machine accounts before installing the client software

To simplify mass deployments, you can bulk create new client machine accounts and pre-assign machines to parent servers in advance of the CA DataMinder rollout. This enables you to deploy multiple client machines using a single source image (which identifies a single parent server) while ensuring that each client machine automatically connects to its 'correct' parent server immediately after installation.

To bulk create new accounts, use the Account Import feature to import the client machine details from a CSV file.

If deploying across multiple subnets

CA DataMinder is designed to operate across subnets. If some or all of your client machines are on a separate subnet to your CMS, computer name resolution must work in both directions.

Windows XP SP2 firewall

The firewall setting ‘Don’t allow exceptions’ must be turned off on the target machine. For details about CA DataMinder and this firewall, see the reference below.

Close all applications before installing the CPSA

Close down all applications that support printing before installing the CPSA, such as Microsoft Office applications. This ensures that the CPSA can detect print jobs sent from these applications. (If an application is already running when you install the CPSA, it will be unable to detect print jobs sent subsequently from that application.)

If you anticipate users printing .EMF files (a Windows graphics file format) directly from Windows Explorer, restart the endpoint computer after installing the CPSA to ensure that it can fully control attempts to print these files.

More information:

Command Files to Import Machines