We have addressed a number of frequently asked questions below which we hope will provide an understanding of the KDA licensing process.
Q1: Why have the number of seats used increased after upgrading to KDA version 9.3?
A1: A defect existed in previous versions regarding how the number of seats were calculated on Terminal Server sessions. This defect resulted in the products under reporting of TS session counts in versions prior to 9.3.
Q2: How is KACE Desktop Authority licensed?
A2: KACE Desktop Authority is licensed based on the total number of unique seats that are managed in whole or part by Desktop Authority. “Seat” is a desktop, laptop, tablet, workstation, thin-client session, or any other user computing device\session supported by our agent (Windows only).
NOTE: In terms of KACE Desktop Authority license usage, physical and virtual computers are treated identically.
Q3: How does using Citrix XenDesktop, and having users running multiple published applications simultaneously, affect my license usage?
A3: By default, Citrix XenDesktop uses one TS (Terminal Server) session per user connection (regardless of how many published apps the users has open). This means a new TS session is established when a Citrix user launches their first published app, and the same TS session is used for any additional apps the user launches that is being hosted on the same TS/Citrix Server. So as long as the default session sharing is still enabled, each managed XenDesktop user, connected to a particular server, will only consume one license. Additionally, Citrix XenDesktop users not running the KDA script (non-managed user) will not consume any licenses.
Q4: What happens when the number of seats used exceeds the number of seats purchased?
A4: There has always been a 20% buffer built into our licensing model which allows customers to be using up to 120% of their available seats/licenses without any notifications. Once the 120% threshold has been exceeded, KDA super users are then notified when they log into the console and also when they logon to a client machine (assuming the super user account is executing the script). So as long as the default session sharing is still enabled, each managed XenDesktop user, connected to a particular server, will only consume one license. Additionally, Citrix XenDesktop users not running the KDA script (non-managed user) will not consume any licenses.
Q5: Can a Terminal Server consume multiple KDA licenses up to the maximum number of concurrently active user sessions?
Q6: Where do I look to see how many managed licenses are being used by KDA at any given time?
A6: Launch the KDA console and click on the Registration link on the lower right-hand side of the page.
Q7: I am looking at the registration screen and the number of seats used doesn’t match the number of users currently logged on to my Terminal Server.
A7: The totals are not displayed in real time. We don’t continuously count license information on Terminal Servers. Instead, we collect a “snapshot” of TS license usage using a hard coded time interval. Therefore, it is likely that the managed seats used by a TS will not be synchronized with what is observed on the registration screen.
Q9: Is there a report that displays the detail for the total I am seeing on the registration screen?
A9: Yes, a "Licensing\Managed Seats Inventory" report can be run from the console and that report is reading data from the same exact source as the registration screen but includes more detail.
All sales inquiries may be directed to https://www.quest.com/buy/
For renewals please direct your queries to https://support.quest.com/contact-us/renewals
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center