KACE Systems Management Appliance 13.2 Common Documents - KACE Service Desk Administrator Guide

Table 42. Device or machine variables and mappings
Appliance variable	Appliance MACHINE database table column	LDAP attribute mapping
KBOX_COMPUTER_NAME	NAME	cn \| name
KBOX_COMPUTER_DESCRIPTION	SYSTEM_DESCRIPTION	description
KBOX_COMPUTER_MAC	MAC	macAddress
KBOX_COMPUTER_IP	IP	ipHostNumber
KBOX_USER	USER_NAME
KBOX_USER_DOMAIN	USER_DOMAIN
KBOX_DOMAINUSER	USER
KBOX_CUSTOM_INVENTORY_*	CUSTOM_INVENTORY

A statement or policy that is displayed to users when they log in to the Administrator Console, Command Line Console, or User Console. See Enable or disable the Acceptable Use Policy.

A cataloging request is a form you can submit to request that an application that is not included in the Software Catalog (Uncataloged) be added to the public Software Catalog. When Quest receives a cataloging request, that request is evaluated to determine whether or not the application should become part of the public Software Catalog. In addition, applications are automatically added to the local version of the Software Catalog on the appliance when cataloging requests are submitted. See Adding applications to the Software Catalog.

The Administrator Console is the web-based interface used to control the appliance. To access the Administrator Console, go to http://<appliance_hostname>/admin where <appliance_hostname> is the hostname of your appliance. If the Organization component is enabled, you can access the System-level settings of the Administrator Console at http://<appliance_hostname>/system. To view the full path of URLs in the Administrator Console, which can be useful when searching the database or sharing links, add ui to the URL you use to log in. For example: http://<appliance_hostname>/admin.

The KACE Agent is an application that can be installed on devices to enable device management through the appliance. Agents that are installed on managed devices communicate with the appliance through the agent messaging protocol. Agents perform scheduled tasks, such as collecting inventory information from, and distributing software to, managed devices. Agentless management is available for devices that cannot have Agent software installed, such as printers and devices with operating systems that are not supported by the Agent. See Provisioning the KACE Agent.

Agentless device management is a method of managing devices without the need to deploy and maintain the KACE Agent software on those devices. Agentless management uses SSH, SNMP, and other methods to connect to Agent-intolerant devices, such as printers, network devices, and storage devices, and report inventory in the appliance Administrator Console. This is useful for operating system versions and distributions that are not supported by the KACE Agent, and where Agentless management is preferred over installing the Agent. See Managing Agentless devices.

Broadcast alerts are messages, such as pop-ups, that can be broadcast from the appliance to be displayed on Agent-managed devices. Displaying alerts is useful when you need to communicate urgent information, or notify users before running actions or scripts on their devices. See Broadcasting alerts to managed devices.

An alternate download location can be any network location that has all the files required to install a particular application. You can distribute packages from alternate download locations including a UNC address or DFS source. The CIFS and SMB protocols, Samba servers, and file server appliances are supported. You specify the location when you create a Managed Installation. See Using Managed Installations.

See ITNinja .

See KACE GO .

Appliance linking enables you to log in to one appliance and access all linked appliances from the drop-down list in the top-right corner of the Administrator Console, without having to log in to each appliance separately. You can link all of the Quest K-Series appliances you manage. See Linking Quest KACE appliances.

The appliance is available as a physical or hardware-based appliance, and as a virtual appliance. The virtual appliance uses a VMware infrastructure. The same system management features are available on both the physical and virtual appliances. See About the appliance components.

Application Control enables you to mark applications as Not Allowed and block them or prevent them from running on Agent-managed Windows and Mac devices. This is useful if you want to restrict specific applications from running in your environment. See Apply the Application Control label to devices.

Support for complex license compliance reporting, building on the framework of data collected through the appliance Inventory process. Asset Management also enables you to track additional data about managed devices, including purchase dates, support contracts, asset tags, and so on. See About the Asset Management component.

Assets and Asset Types used in the Asset Management component include physical and logical items, such as devices, applications, printers, licenses, departments, locations, and vendors. The Asset Management component enables you to build relationships between assets, track inventory data, view records of changes, and report on changes to assets. Assets are based on Asset Types. You can modify default Asset Types, create custom Asset Types, and import asset information as needed. See About Asset Types. Asset Subtypes are subcategories of assets that you can add to any Asset Type, including custom Asset Types. This enables you to identify and manage subtypes of assets, such as Device assets that are computers, printers, or routers, and Software assets that run on Windows, Mac, or Linux systems in the appliance inventory. See About Asset Subtypes, custom fields, and device detail preferences.

Your appliance license agreement entitles you to manage a specified number of devices that are categorized as Assets, and these Assets differ from assets used in the Asset Management component. Assets that count toward your are license limit include devices that 1) have been added to the appliance inventory but do not meet the definition of Managed Computers or Monitored Servers and 2) were not added to inventory manually, through the WSAPI, or through mobile management. Examples of Assets include printers, projectors, network gear, and storage devices.

See View product licensing information.

See Acceptable Use Policy .

Labels that are applied automatically, such as Smart Labels. See Setting up and using labels to manage groups of items.

A statement or policy that is displayed to users when they log in to the Administrator Console, Command Line Console, or User Console. See Enable or disable the Acceptable Use Policy.

A cataloging request is a form you can submit to request that an application that is not included in the Software Catalog (Uncataloged) be added to the public Software Catalog. When Quest receives a cataloging request, that request is evaluated to determine whether or not the application should become part of the public Software Catalog. In addition, applications are automatically added to the local version of the Software Catalog on the appliance when cataloging requests are submitted. See Adding applications to the Software Catalog.

The Administrator Console is the web-based interface used to control the appliance. To access the Administrator Console, go to http://<appliance_hostname>/admin where <appliance_hostname> is the hostname of your appliance. If the Organization component is enabled, you can access the System-level settings of the Administrator Console at http://<appliance_hostname>/system. To view the full path of URLs in the Administrator Console, which can be useful when searching the database or sharing links, add ui to the URL you use to log in. For example: http://<appliance_hostname>/admin.

The KACE Agent is an application that can be installed on devices to enable device management through the appliance. Agents that are installed on managed devices communicate with the appliance through the agent messaging protocol. Agents perform scheduled tasks, such as collecting inventory information from, and distributing software to, managed devices. Agentless management is available for devices that cannot have Agent software installed, such as printers and devices with operating systems that are not supported by the Agent. See Provisioning the KACE Agent.

Agentless device management is a method of managing devices without the need to deploy and maintain the KACE Agent software on those devices. Agentless management uses SSH, SNMP, and other methods to connect to Agent-intolerant devices, such as printers, network devices, and storage devices, and report inventory in the appliance Administrator Console. This is useful for operating system versions and distributions that are not supported by the KACE Agent, and where Agentless management is preferred over installing the Agent. See Managing Agentless devices.

Broadcast alerts are messages, such as pop-ups, that can be broadcast from the appliance to be displayed on Agent-managed devices. Displaying alerts is useful when you need to communicate urgent information, or notify users before running actions or scripts on their devices. See Broadcasting alerts to managed devices.

An alternate download location can be any network location that has all the files required to install a particular application. You can distribute packages from alternate download locations including a UNC address or DFS source. The CIFS and SMB protocols, Samba servers, and file server appliances are supported. You specify the location when you create a Managed Installation. See Using Managed Installations.

See ITNinja .

See KACE GO .

Appliance linking enables you to log in to one appliance and access all linked appliances from the drop-down list in the top-right corner of the Administrator Console, without having to log in to each appliance separately. You can link all of the Quest K-Series appliances you manage. See Linking Quest KACE appliances.

The appliance is available as a physical or hardware-based appliance, and as a virtual appliance. The virtual appliance uses a VMware infrastructure. The same system management features are available on both the physical and virtual appliances. See About the appliance components.

Application Control enables you to mark applications as Not Allowed and block them or prevent them from running on Agent-managed Windows and Mac devices. This is useful if you want to restrict specific applications from running in your environment. See Apply the Application Control label to devices.

Support for complex license compliance reporting, building on the framework of data collected through the appliance Inventory process. Asset Management also enables you to track additional data about managed devices, including purchase dates, support contracts, asset tags, and so on. See About the Asset Management component.

Assets and Asset Types used in the Asset Management component include physical and logical items, such as devices, applications, printers, licenses, departments, locations, and vendors. The Asset Management component enables you to build relationships between assets, track inventory data, view records of changes, and report on changes to assets. Assets are based on Asset Types. You can modify default Asset Types, create custom Asset Types, and import asset information as needed. See About Asset Types. Asset Subtypes are subcategories of assets that you can add to any Asset Type, including custom Asset Types. This enables you to identify and manage subtypes of assets, such as Device assets that are computers, printers, or routers, and Software assets that run on Windows, Mac, or Linux systems in the appliance inventory. See About Asset Subtypes, custom fields, and device detail preferences.

Your appliance license agreement entitles you to manage a specified number of devices that are categorized as Assets, and these Assets differ from assets used in the Asset Management component. Assets that count toward your are license limit include devices that 1) have been added to the appliance inventory but do not meet the definition of Managed Computers or Monitored Servers and 2) were not added to inventory manually, through the WSAPI, or through mobile management. Examples of Assets include printers, projectors, network gear, and storage devices.