Tchater maintenant avec le support
Tchattez avec un ingénieur du support

KACE Systems Management Appliance 13.2 Common Documents - KACE GO 8.2 Release Notes

Privacy policy

Privacy policy

Collected information

The KACE development team collects the following information, for internal use:

Mobile device permissions

KACE GO requires access to the camera on your mobile device to support uploading image attachments to Service Desk tickets.

The Android version of KACE GO also requires the Android GET_ACCOUNTS permission which was required for Google Cloud Messaging push notifications. For Ice Cream Sandwich and newer versions of Android, this permission is no longer required for push notifications, and will be removed in a future version of KACE GO for Android.

Use of personal information

The collected data is used by the KACE development team to make product improvements. Apart from the information required by the Apple and Google push notification services, none of this information is ever shared with a third party.

If you have any questions about this policy, you can contact Support at

New features

New features

This release of the KACE GO does not include any new features.

For complete information about the features available with the KACE GO mobile app, see the Getting Started Guide.

Resolved issues

Resolved issues

The following is a list of resolved issues and product enhancements available in this release.

Table 1. iOS Resolved Issues

Resolved issue

Issue ID

Editing an asset's subtype and then cancelling caused KACE GO to crash.


Table 2. Android Resolved Issues

Resolved issue

Issue ID

Push notification did not show ticket ID and details when app was working in the background.


KACE GO only displayed the first 50 user names in the Service Desk ticket user field.


Displaying ticket details caused KACE GO to crash.


Known issues

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 3. General known issues

Known issue

Issue ID

iOS: KACE GO can fail to create a new asset if multiple asset associations fields (Asset_xxx) are used.


iOS: KACE GO can fail to create a ticket if the queue has a custom single select field with values populated through a database query and default value is set.


Android: 400 Error reported due to an unrecognized value for select field custom_xx in case of new ticket creation when the queue has a single/multi select custom field.


Android: A new Asset cannot be created when the user applies a set of rules in the Asset field.


Tickets always show change text in English, regardless of the locale setting of the appliance.


The first time a use you type a server name for a KACE Systems Management Appliance that has a self-signed certificate, a dialog box appears, indicating that the certificate is currently untrusted, and allows you to accept it and continue, or stop processing that server. This is expected behavior.

However, if the appliance is also configured for SAML (Security Assertion Markup Language) and you attempt to use SAML to log, a browser is shown, to perform the SAML login. At that point, the browser also reports the self-signed certificate, asking you to approve the certificate a second time.


My Tickets count is wrong for administrators. This is caused by the fact that the Service Desk API only returns owned tickets in the query, not both owned and submitted tickets, as expected.


Certain type of custom Asset fields are not fully supported in KACE GO. The following custom fields appear as read-only fields: Label, Locale, Asset-Multiple Select, Asset-Parent and Software Catalog.


Asset attachments are not supported at this time.


Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation