Chat now with support
Chat with Support

KACE Systems Management Appliance 9.1 Common Documents - Administrator Guide

About the KACE Systems Management Appliance (SMA) Getting started
Configuring the appliance
Requirements and specifications Power-on the appliance and log in to the Administrator Console Access the Command Line Console Tracking configuration changes Configuring System-level and Admin-level General Settings Configure appliance date and time settings Enable Two-Factor Authentication for all users Verifying port settings, NTP service, and website access Configuring network and security settings Configuring Agent settings Configuring session timeout and auto-refresh settings Configuring locale settings Configuring the default theme Configure data sharing preferences About DIACAP compliance requirements Configuring Mobile Device Access Enable fast switching for organizations and linked appliances Linking Quest KACE appliances Configuring history settings
Setting up and using labels to manage groups of items Configuring user accounts, LDAP authentication, and SSO Using Replication Shares Managing credentials Configuring assets
About the Asset Management component Using the Asset Management Dashboard About managing assets Adding and customizing Asset Types and maintaining asset information Managing Software assets Managing physical and logical assets Maintaining and using manual asset information Managing locations Managing contracts Managing licenses Managing purchase records
Setting up License Compliance Managing License Compliance Setting up Service Desk Configure the Cache Lifetime for Service Desk widgets Creating and managing organizations Importing and exporting appliance resources
Managing inventory
Using the Inventory Dashboard Using Device Discovery Managing device inventory
About managing devices Features available for each device management method About inventory information Tracking changes to inventory settings Managing inventory information Finding and managing devices Provisioning the KACE SMA Agent Manually deploying the KACE SMA Agent Using Agentless management Adding devices manually in the Administrator Console or by using the API Forcing inventory updates Managing MIA devices Obtaining Dell warranty information
Managing applications on the Software page Managing Software Catalog inventory
About the Software Catalog Viewing Software Catalog information Adding applications to the Software Catalog Managing License assets for Software Catalog applications Associate Managed Installations with Cataloged Software Using software metering Using Application Control Update or reinstall the Software Catalog
Managing process, startup program, and service inventory Writing custom inventory rules
Deploying packages to managed devices
Distributing software and using Wake-on-LAN Broadcasting alerts to managed devices Running scripts on managed devices Managing Mac profiles Using Task Chains
Patching devices and maintaining security
About patch management Subscribing to and downloading patches Creating and managing patch schedules Managing patch inventory Managing Dell devices and updates Maintaining device and appliance security
Using reports and scheduling notifications Monitoring servers
Getting started with server monitoring Working with monitoring profiles Managing monitoring for devices Working with alerts
Using the Service Desk
Configuring Service Desk Using the Service Desk Dashboard Managing Service Desk tickets, processes, and reports
Overview of Service Desk ticket lifecycle Creating tickets from the Administrator Console and User Console Creating and managing tickets by email Viewing tickets and managing comments, work, and attachments Merging tickets Using the ticket escalation process Using Service Desk processes Using Ticket Rules Run Service Desk reports Archiving, restoring, and deleting tickets Managing ticket deletion
Managing Service Desk ticket queues About User Downloads and Knowledge Base articles Customizing Service Desk ticket settings Configuring SMTP email servers
Maintenance and troubleshooting
Maintaining the appliance Troubleshooting the KACE SMA
Appendixes Glossary About us Legal notices

Setting up License Compliance

Setting up License Compliance

About License Compliance for Software Catalog applications
Customize the License Asset Type
Add License assets for Software Catalog inventory
Add License assets for Software page inventory
Importing license data in CSV files

To track License Compliance information for applications, you need to create License assets. License assets can be associated either with applications in the Software Catalog inventory or the Software page inventory. License assets cannot be associated with both inventory types at the same time.

The options for tracking licenses, and the requirements for setting up License Compliance, differ for Software Catalog inventory and for Software page inventory.

About License Compliance for Software Catalog applications

About License Compliance for Software Catalog applications

About license upgrades
About license downgrades

The KACE SMA enables you to view License Compliance information for applications in the Software Catalog inventory. This information appears on the License Compliance page and in the License Compliance Dashboard widget.

After you configure License assets for applications in the Software Catalog inventory, you can view the number of seats installed on Agent-managed devices, the number of seats available, the type of licenses applied, and, if metering is enabled for the application, usage information. In addition, the KACE SMA leverages information in the Software Catalog to automatically apply the correct licenses to application versions that are classified as upgraded or downgraded.

To set up License Compliance for applications in the Software Catalog inventory:

•
(Optional) Customize the License Asset Type to meet your information management requirements. See Customize the License Asset Type.
•
(Optional) Enable metering for Software Catalog applications. When metering is enabled, the License Compliance page shows whether applications have or have not been used in the past 30, 60, and 90 days. See About software metering.
•
Create License assets and associate them with applications in the Software Catalog inventory. See Add License assets for Software Catalog inventory.
•
(Optional) Set the threshold levels for License Compliance used on the Dashboard widget. The default Warning Threshold is 90. The default Critical Threshold is 100. See Customize license usage warning thresholds.

About license upgrades

About license upgrades

Application maintenance plans often enable users to upgrade to newer versions of applications when those versions become available, and the License Compliance page shows the number of installations that are considered to be upgrades.

To track upgrades, the KACE SMA uses the information in the Software Catalog and the license details to determine whether to associate new versions of applications with existing licenses. For example, if a License asset was created for the 1.0 version of an application, and the maintenance plan entitles users to upgrade, the 2.0 version of the application is automatically covered by the License asset when it is released. In this example, the License asset must be configured as follows:

•
The Includes Maintenance field must be set to Yes.
•
The Maintenance Expiration Date must be later than the version 2.0 GA (General Availability) date in the Software Catalog.
•
The License Mode must be Enterprise or Unit License.
•
The Include Upgrade Rights must be set to Yes or Yes - Select from list.

For more information about these settings, see Add License assets for Software Catalog inventory.

About license downgrades

About license downgrades

Vendors often allow users to apply licenses for newer versions of applications to older versions, and these types of installations are referred to as downgrades. The License Compliance page shows the number of installations that are considered to be downgrades.

License seats are first allocated to installations of the latest version of the application. If additional seats are available, and if the vendor allows downgrades, the seats are automatically allocated to installations that are considered downgrades.

Licenses for upgrades are always allocated before licenses for downgrades.

Related Documents