Creating an Agent Install Package

On the Agent > Manage Packages page, click Create to start the Create Agent Pack wizard. The wizard is a 7 step process.

1. Specify how the machine id is assigned.
   • Prompt the user to enter a machine ID.
   • Use the computer name as the machine ID.
   • Set the user name of the currently logged on user as the machine ID.
   • Specify a fixed machine ID for this install package.
2. Specify how the group id is assigned
   • Existing Group - Select an existing group ID from a drop-down list.
   • Domain Name - Uses the user's domain name.
   • New Group - Specify a new group ID. This option only displays for master role users.
   • Prompt User - Asks user to enter a group ID. This option only displays for master role users.
3. Optionally specify installer options using command line switches. This includes the ability to install silently without any task bars or dialog boxes.
4. Optionally select a machine from the Agents list to copy settings and pending agent procedures from. This is oftentimes a machine ID template account. All copied settings and pending agent procedures—except the organization ID, machine ID, and group ID—are applied to every new machine ID created with the package.

   Note: The statement Copy settings from unknown.root.unnamed if nothing selected is based on the machine ID or template selected by the Default Install package.

5. Select he operating system you are creating the install package for: Automatically choose OS of downloading computer: Windows, Macintosh, or Linux.
6. Optionally bind a user logon credential to the install package. Fill in the Administrator Credential form to securely bind user rights to the install package.
   • Users without administrator rights can install the package successfully without having to enter an administrator credential.
   • If the administrator credential is left blank and the user does not have administrator rights to install software, the install package prompts the user to enter an administrator credential during the install. If the package is also silent KcsSetup will fail without any dialog messages explaining this.

   Administrator Credentials - If necessary, an agent install package can be created that includes an administrator credential to access a customer network. Credentials are only necessary if users are installing packages on machines and do not have administrator access to their network. The administrator credential is encrypted, never available in clear text form, and bound to the install package.

7. Provide a name and description for the install package for easy reference later. This name displays on the Manage Packages page and the dl.asp download page.
8. Optionally set the new install package as the default install package.
9. Optionally show the install package on the download page.