Follow

Software Deployment Update Licensing information/issues

 

PROBLEM

Negative license count in KSDU>Licensing page

2014-12-09_11_31_45-Kaseya_-_Agent.jpg

CAUSE

Normally this issue occurs when profiles assigned to the machines are more than available licenses.
When using Policy management to assign ksdu profiles and scheduling scan make sure you have enough licenses to assign those profiles . If the profile policy applies to more machines than available license then license left count will show as negative.

RESOLUTION

Check if the policy is deploying ksdu profiles to the right machines. Remove those extra machines from the profiles to bring the  license count to  normal.

Sometimes the sync between frontend and backend is required to resolve the ksdu incorrect license count issue. 
This can be done by running reapply of schema from System>Configure page

 If the issue still persist then please create a support ticket for assistance.

 

Details on KSDU Licensing

 

Once a KSDU license is used on a machine, it is locked on that machine until 30 days from the day it was used. After the thirty days, if the license was removed or the agent was removed, then the license gets freed up. Please see this below information


For any particular machine, a KSDU license is consumed under any of the following conditions:

a scan is performed
a deployment is performed
a machine is assigned to a profile, or remains assigned to a profile.

A machine can only consume one KSDU license.


If there are 31 days of inactivity (no scans, no deployments, and unassigned from all profiles), the KSDU license goes back into the pool of available KSDU licenses

 

 

 

Applies to  all versions.

 

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.