Automating the Installation of the Agent

You can use the following methods to automate the installation of agent install packages:

Logon

• Windows - Set up an NT logon procedure to run the install package every time a user logs into the network. See system requirements.
• Apple - Set up an Apple OS X Login Hook Procedure to run the install package every time a user logs into the network. See Apple KB Article HT2420.

Procedure

1. Create the deployment package using the Agent > Manage Packages wizard.
   • The KcsSetup installer skips installation if it detects an agent is already on a machine if the /e switch is present in the installer package.
   • You will probably want to select the silent install option.
   • It may be necessary to bind an administrator credential if users running the logon procedure don't have user rights.
2. Download the appropriate KcsSetup installer package using the dl.asp page and copy it to a network share which users can execute programs from.
3. Add KcsSetup with its network path to the logon procedure.

Email

Email KcsSetup to all users on the network. Download the appropriate install package from the Manage Packages page, then attach it to an email on your local machine. You can also copy and paste the link of the default install package into an email message. Include instructions for launching the package, as described in the Manual bullet below.

Discovery by Network or Domain

Use the Discovery module to discover machines on Networks and Domains, then install the agents on discovered machines, either manually or automatically.

Automatic Account Creation

You should be aware that automatic account creation is enabled using System > Check-in Policy to automatically create a machine ID account when an agent install package is installed. This option is enabled by default when the VSA is installed.

Assigning New Machine IDs to Machine Group by IP Address

You may choose to create a "generic" install package that adds all new machine accounts to the unnamed group ID. When the agent checks in the first time, the System > Naming Policy assigns it to the correct group ID and/or sub-group ID using the IP address of the managed machine. Agent settings can be configured afterward by policy or template. See:

• Configuring Agent Settings Using Policies
• Configuring Agent Settings Using Templates