Create

Agent > Create

The Create page creates a machine ID account and agent install package for a single machine. You create the machine ID account first, then create an install package for this single machine. Typically the Create page applies to:

• Machine ID templates - In this case, no install package need be created, since machine ID templates are not intended for installation to a machine.
• Secured environments - Secured environments may require each machine be setup manually. For example, you might be required to name a new machine ID account manually and/or create an agent install package with a unique credential for a single machine. A user must be logged into a target machine locally as an administrator to install the package.

Note: Use Agent > Deploy Agents to create and distribute agent install packages to multiple machines. The Deploy Agents install package automatically creates a machine ID account when it is installed provided automatic account creation is enabled using using System > Check-in Policy.

Note: Use Install Agent to install agents on remote systems.

Re-Installing Agents

Because the Create install packages does not automatically create a new machine ID account, you can use the Create page to re-install agents on managed machines for existing accounts.

Machine IDs vs. Agents

When discussing agents it is helpful to distinguish between the machine ID / group ID and the agent. The machine ID / group ID is the VSA's user account name for a managed machine in its database. The agent is the client software installed on the managed machine. A one-to-one relationship exists between the agent on a managed machine and its machine ID / group ID account name on the VSA. Tasks assigned to a machine ID by a VSA administrator direct the agent's actions on the managed machine.

Agent License Counts

The following events affect agent license counts:

• An "unused" agent license is changed to "used" if a machine ID account is created and the agent installed.
• If the agent is deleted but not the account, the agent license is still considered "used".
• If the account is deleted, regardless of what happens to the agent, the agent license goes back to "unused".
• If an account is created, but the agent is not yet installed the first time, the account is called a machine ID template. Machine ID template accounts are not counted as "used" until you install the agent.

Including Credentials in Agent Install Packages

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.

Windows vs. Macintosh

Agent packages can be created to install agents on machines running either Windows or Macintosh operating systems.

Machine ID Templates

A machine ID template is a machine ID record without an agent. Since an agent never checks into a machine ID template account, it is not counted against your total license count. You can create as many machine ID templates as you want without additional cost. When an agent install package is created, the package's settings are copied from a selected machine ID template. Typically machine ID templates are created and configured for certain types of machine. Machine type examples include desktops, Autocad, Quickbooks, small business servers, Exchange servers, SQL Servers, etc. A corresponding install package can be created based on each machine ID template you define.

• Create machine ID templates using Agent > Create.
• Import a machine ID template using Agent > Import/Export. Sample templates can be downloaded from the Kaseya Support Forum and imported.
• Base an agent install package on machine ID template using Agent > Deploy Agents.
• Copy selected settings from machine ID templates to existing machine ID accounts using Agent > Copy Settings.
• Identify the total number of machine ID template accounts in your VSA using System > Statistics.
• Configure settings for the machine ID template using the standard VSA functions, just as you would a machine ID account with an agent.

Copy new account settings from

Click a radio button next to any machine ID listed in the paging area. Agent settings are copied from this machine ID.

Note: If you don't include a machine ID to copy from and click Create, a new, usable machine ID account is created using KServer defaults. You can copy settings between existing machine ID accounts at any time using Agent > Copy Settings.

New Machine ID

Enter a unique name for the new machine ID you are creating.

Group ID

Select an existing group ID for the new machine ID you are creating. The default is unnamed. Group IDs are created by an administrator using the System > Admin Accounts: Create / Delete page.

Create

Click Create to create the new machine ID for the selected group ID.

Set/Clear New accounts created in group ID <Group ID> copy settings from <Machine ID>

For each group ID you can specify a different default machine ID to copy settings from.

1. Select a machine ID to copy settings from by clicking the radio button next to any machine ID listed in the paging area.
2. Select a group ID from the group ID drop down list. Select a group ID.
3. Click the Set to ensure that new machine IDs you create for the selected group ID will copy settings from the selected default machine ID.
4. Click the Clear link to remove this assignment.

Set/Clear Accounts created in unassigned group IDs copy settings from <Machine ID>

This option specifies the default machine ID to copy settings from if no default machine ID is set for a group ID. This option only displays if a master administrator is logged on.

1. Select a machine ID to copy settings from by clicking the radio button next to any machine ID listed in the paging area.
2. Click the Set to ensure that new machine IDs created without a group default machine ID copy settings from the master administrator's default machine ID.
3. Click the Clear link to remove this assignment.

Entering Contact Information

When you enter contact information on this page for a new machine ID account, then create the new machine ID account by clicking the Create button, these same contact information fields populate the Agent > Edit Profile page. Contact information includes:

• Contact Email - Enter the email address of the individual using the managed machine
• Auto Assign - Check Auto Assign to automatically populate the Contact Email field with an email address that uses the following format: machineid@groupid.com. This feature assumes you are creating machine IDs and group IDs that conform to user email addresses.
• Contact Name - Enter the name of the individual using the managed machine.

  Note: This field is required to generate a new password for the Agent > User Access page.

• Contact Phone - Enter the phone number of the individual using the managed machine.
• Admin Email - Enter the email address of the individual responsible for providing IT support for the managed machine.

Check-in status

These icons indicate the agent check-in status of each managed machine:

Agent has checked in

Agent has checked in and user is logged on. Tool tip lists the logon name.

Agent has not recently checked in

Agent has never checked in

Online but waiting for first audit to complete

The agent is online but remote control is disabled

The agent has been suspended

Copy Settings

Click a radio button next to any machine ID listed in the paging area. Machine ID settings are copied from this machine ID.

Download / Email Agent Installation

Click a machine ID link to create and distribute an install package for an existing machine ID account using the Download Agent wizard.

Note: An install package created using this page is for a specific machine ID account. Use Deploy Agent to create install packages for multiple machines.

1. Select the operating system you are creating the install package for: Windows or Macintosh.
2. Optionally bind an administrator logon credential to the install package. Fill in the Administrator Credential form to securely bind administrator 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.
3. Select the method of distribution.
   • Download - Download the install package immediately to the machine you are currently using. The install package is always called KcsSetup.exe.
   • Email - Email a text message that contains a link to download the install package.

Type

The type of operating system used by the managed machine:

• Windows
• Macintosh

First Checkin

Lists the time that each agent checked into the server for the first time.

Topic 496: Send Feedback. Download a PDF of this online book from the first topic in the table of contents.