Chat now with support
Chat with Support

KACE Systems Management Appliance 10.0 Common Documents - Release Notes

Asset Management features

Asset Management features

This release of the KACE Systems Management Appliance (SMA) includes the following Asset Management features.

Scheduled asset import: Starting in this release, you can configure a scheduled import of assets from a CSV (comma-separated value) file located on a network share, using the Import Assets wizard. The wizard includes a new page, Asset Import Selection Schedule, that allows you to choose from available schedule patterns, as required.
Ability to map the Asset Status field during asset import: The Mapping page in the Import Assets wizard now allows you to map the Asset Status field to a column in the CSV file. This is useful in cases when you need to import a high number of assets with each asset having a specific status (such as Active). If you do not specify this mapping, the default status that is associated with the selected Asset Type is assigned to each imported asset entry.
Administrators can prevent non-administrative users from deleting assets: The Asset Type Detail page now includes an option, Allow non-administrators to delete assets, that administrators can use to specify whether non-administrative users have the capability to delete assets. This option is turned off by default. Only administrators can configure this option. For other types of users, this field appears on the page, but it is disabled.
Appliance administrators can create asset types without Location and User fields. There are certain asset types (such as Purchases or Contracts) where this information is irrelevant. The Asset Type Detail page now includes the Show Location settings option that can be used to include or exclude the Location field for the selected asset type. Similarly, the Asset Assignee value only appears in Device-type assets.

Endpoint communication features

Endpoint communication features

This release of the KACE Systems Management Appliance (SMA) includes the following endpoint communication features and enhancements.

Discovering Microsoft Hyper-V or System Center Virtual Machine Manager (SCVMM) devices: If your organization uses a virtual Hyper-V-based environment, you can use the appliance to discover Microsoft Hyper-V or SCVMM devices through discovery scheduling. To scan your network for Hyper-V or SCVMM devices, and to capture information about those devices, add an Authenticated Discovery Schedule. Each SCVMM/Hyper-V device consumes an agentless license. If the device is also provisioned with a KACE agent, it also consumes a license for the agent.
Battery information added to Device Details: The Device Details page now includes a new group of fields, Batteries, that displays battery-related information for Windows, Linux and MacOS Agent-managed and Agentless devices. This group includes the following fields:
Charge: The percentage of the current battery capacity.
Chemistry: Windows and Linux devices only. The battery type, such as Lithium Ion, and so on.
Current Capacity (mWh): The current battery capacity.
Design Capacity (mWh): The maximum capacity of battery by design.
Full Charge Capacity (mWh): Current maximum capacity of battery. This value degrades over time.
Health (%): The percentage of the current battery capacity compared to its maximum designed capacity.
Manufacturer: The battery manufacturer.
Name: The battery name or model.
Plugged In: An indicator of whether the battery is currently plugged into a power source.
Recharge Count: MacOS devices only. The number of times the battery has been recharged.
Serial Number: The serial number of the battery.
Time Remaining (Minutes): The number of minutes after which the battery becomes discharged. When the device is plugged in, this field is blank.
Ability to upload and distribute cURL certificate bundles: Some environments use custom cURL (Client URL) CA (certificate authority) certificates during agent-server communication. This can be used to verify SSL certificates that are signed by an authority that is not referenced in the default agent bundle. Starting in this release, you can use the CA Certificate Bundle File setting on the Agent Settings page to upload a custom cURL CA bundle, or to revert to the default one.
Remote Control: Integration with a third-party solution for remote control management across Windows, Mac, and Linux systems. SimpleHelp now appears as an option under Device Actions on the General Settings page. For more information about this tool, see your SimpleHelp documentation.
Viewing information about devices enrolled in KACE Cloud Mobile Device Manager (MDM): The appliance displays information about Mac OS X devices that are enrolled in an integrated KACE Cloud MDM instance. The type of information available for such devices depends on whether they have a KACE SMA Agent installed.
Device management method appears in Device Details: The new Device Entry Type field on the Device Details page the selected device's management method: Agent Device, Agentless Device, Manually Entered Record, or Agent/Agentless (hybrid KACE Cloud MDM inventory).
Dissociating a device from KACE Cloud MDM: For Agentless devices enrolled in KACE Cloud MDM, to remove the device's association with KACE Cloud MDM and revert to Agent-only inventory records, on the Device Details page, simply click Remove Agentless Integration.
KBRSL removed from the appliance: KBRSL is no longer included in provisioning code. Existing KBRSL provisioning schedules are converted to use WinRM.
Integration with KACE Systems Deployment Appliance (SDA): The KACE Agent populates the KACE SDA configuration information on the KACE SMA Device Detail Inventory view.
Urgent alert mode: A new option is added to the Alert Detail page for Urgent alert mode. When selected, the alert message appears in the center of the screen, without allowing the user to move it, or to send it to the background. The alert must be addressed before any work can continue.
Addition of OS-native scripting variable for the native Windows registry space: Starting in this release, you can add NAT to HKLM (HKEY_LOCAL_MACHINE) to access 32- or 64-bit registry space in script tasks, as needed. For example: HKLMNAT\Software\ABC.

Infrastructure features

Infrastructure features

This release of the KACE Systems Management Appliance (SMA) includes the following infrastructure features and enhancements.

KACE SMA patching solution: A complete KACE SMA patching solution for MS Windows and Mac OS is added in this release. Patch packages are downloaded from Quest according to the subscription and download options you select. In some cases, patch packages are also downloaded directly from vendors. Quest provides safe, timely, and high-quality patch signatures for Windows and Mac operating systems, and many popular applications.
After upgrading to this version, an alert appears on the Summary page that lists any deprecated reports, ticket rules, or custom filters.
A new built-in report, Software Catalog Applications Discovered but Unavailable in Application Patching, is available to show software discovered in the Software Catalog that cannot be patched by KACE patching. This may help while auditing third-party software for security updates.
A new report, KACE Patch Mismatches is included in this release. During the upgrade process, existing patching data is converted to the new format when possible. This report lists patches that can not be converted.
Using Security Assertion Markup Language (SAML) for single sign-on: You can configure the appliance to authenticate users without providing their credentials on the Welcome page using a third-party authentication tool. SAML is an XML-based protocol that uses security tokens between identity and service providers. The security tokens contain assertion elements that provide information about the user's identity. Use the SAML Settings page to configure this feature.
Ability to send data to a Syslog server: You can now configure the appliance to send limited server log data to a remote Syslog server. To do that, on the Security Settings page, select Enable remote syslog, and in the Remote Syslog Server field, specify the fully qualified domain name (FQDN) or IP address and the port number of the remote Syslog server.
Number of affected devices available for software inventory: The Software list page now includes the Devices Affected field in the Advanced Search.
Shifting the focus on list pages to support barcode scanning. When loading a list page, the focus switches to the search box on the page. This can be seen by the cursor being in the text box. This is implemented to enable support for barcode scanning.

Resolved issues

Resolved issues

The following is a list of issues resolved in this release.

Table 1. Resolved Issues

Resolved issue

Issue ID

Installation through KACE Cloud Mobile Device Manager (MDM) provisioning could fail due to expired certificate with 9.1.204 Mac OS agent installer.


Mac OS profile upload may result in error.


Mac OS profile upload resulted in Class 'NetworkSettingsUtil' not found.


It was not possible to view archived parent tickets.


Special characters in Western European (ISO) encoded emails did not display correctly.


Some models of Dell Chromebooks could fail to be detected with manufacturer listed as Dell.


Backup files could be unnecessarily large.


License Compliance data might not update if it overlapped with backup window.


Patch schedule Detect Timeout and Deploy Timeout options above two hours were available for selection (and they should not be).


Comment new lines were run together when coming from Process Template.


Work information was sometimes not displayed after page reload on the Ticket Details page.


Inbound Email tokens did not work when being sent from a ticket rule.


Agent was sometimes recognized as anti-virus software due to expired certificate.


Compliance data could take unnecessarily long to update.


Incoming HTML email did not decode special characters such as non-breaking spaces (NBSP).


Wizard asset report involving custom user field was blank unless OWNER_ID was set.


Asset import did not set OWNER_ID for non-device types.


Users with no email set could see tickets that do not belong to them in the Tickets list page.


Missing in action (MIA): Archive did not work as expected for devices without corresponding assets.


Asset archival could fail to run per schedule if a backup was in progress.


Loading of a software Asset Detail page could be slow if there was a high number of installed software items.


Patching: OS Selection was removed on save without notification when selecting all devices.


Non-default permissions could prevent the Kace GO mobile app from accurately listing devices.


Change Location pop-up box did not display in French locale.


Creating new asset could set the default subtype to None instead of the default subtype.


Items removed before being completely replicated could still show up in the ToDo list.


Provisioning schedules list did not display hours or minutes for run every or run on schedule.


A warranty check of Dell devices resulting in Invalid could prevent future warranty checks of the same device.


A discovery smart label with invalid SQL could result in the entire scan failing.


Multiple users could be created when submitting ticket by email using archived user.


Email notifications of ticket updates could fail to be generated.


Links in scheduled HTML wizard reports failed when report is opened through email.


The Devices drop-down box on the Run Now script page could take a long time when using device scope labels.


Large asset history deletion could fail.


Task Schedule could sometimes fail to load on an appliance with many replicators.


The Browse Tree option in the LDAP Browser could fail to execute.


Mac Profiles failed to deploy due to an incorrect agent path.


Ticket was displayed in the All My Tickets view when a user with similar email was added to the CC list.


Dark theme text/background in the Process wizard lacked contrast.


Agent installer could mistakenly update third-party userinit values if they contained the substring userinit.exe.


Some provisioned virtual machine devices did not dislay the VMware device actions on the Device Detail page.


Canned Report: Computers listed by free capacity ranges improperly grouped results.


Parent approval required before ticket can be closed message could be seen, by mistake.


Advanced Search on the Status field was not working on the Patch Catalog page.


Metering icon could be mistakenly displayed for Windows agentless devices that had the metering label added.


Timeout setting in discovery schedules did not behave as expected.


Chip count in inventory could be wrong for Raspbery Pi.


Blank or duplicate BIOS serial number with accompanying duplicate MAC address could incorrectly cause inventory records to be overwritten.


Blacklisting processes did not always terminate the entire process tree. This caused orphaned child processes and in extreme cases could exhaust memory on the endpoint.


When using offline patching, offline source and target could have different active, inactive, and disabled counts.


Patch feed emails could fail to send due to not respecting SMTP configuration on network settings.


Advanced Search does not begin with fails for groups such as Label Names and Software Titles.


Dell BIOS update might not reboot the client when pushed, preventing it from being installed completely until after a reboot.


Canned Report: Users Added or Modified in Last 7 Calendar Days was inaccurate.


New line character in Dell Updates reboot message could cause the reboot from being completed.


Manually added devices could be mistakenly deleted by the nightly MIA cleanup process.


MI Deploy Order might not be correctly enforced between Software and Catalog Software Managed Installations (MIs).


When a software inventory item contained non-English characters, smart labels could fail to execute correctly.


The formatting in a customer defined Patch Reboot message was not respected.


LDAP Import could exclude attributes not found on all records.


A Custom user field for an asset incorrectly mapped to assigned users in reports.


The Software Inventory page could take a long time to load.


Patch download failures could be incorrectly reported.


When clicking the error link in the Patch Catalog, an incorrect No Devices Found message might appear.


Smart Labels targeting software title and version could return incorrect results.


The patching reboot message appearing on the client machine might not reflect what is configured in the patch schedule.


Erroneous question mark character '?' was observed in the KACE SMA console hosted on Azure.


Comment section for tickets did not clear when adding comment and attachment at the same time.


Ticket could be merged to a closed ticket.


Search functionality was broken for restricted user when view by option is set as My Items.


Blank Patch Detail page on clicking the patch under the Supersedes section on the Patch Detail page.


Processing agent inventories with a missing list of network interfaces might fail.


The SDA settings section was missing from the Fields to Display page of the System report wizard.


Search for devices with SDA Deployment Time was not working on the Devices list page with Advanced Search.


HTML tags sometimes appeared under in the Comments & Resolution column in Service Desk Reports.


Merging two tickets with the same submitter added them to the CC list.


Submitters could not see their tickets if tickets moved into queue where submitter did not have any permissions.


It was not possible to sort by Type column under Assigned Assets section on Location Detail page.


Related Documents