Symantec Endpoint Protection Manager is showing over deployment of clients

Article:TECH168121  |  Created: 2011-08-25  |  Updated: 2012-03-29  |  Article URL http://www.symantec.com/docs/TECH168121
Article Type
Technical Solution


Environment

Issue



The Symantec Endpoint Protection Manager (SEPM) shows over deployment of clients


Error



In the licensing field it says "Attention Needed", and if clicked, it will show that the SEPM is over deployed with "x" number of clients


Cause



Clients have been removed from the network without first uninstalling the Symantec Endpoint Protection (SEP) client and are still showing as using a license seat.


Solution



The following procedure will cause the SEPM to remove clients from its database that have not checked in within the past 24 hours, and thereby reclaim these license seats. If the number of installed clients is more than the license seat count then this will not resolve the issue. In that case more seats would need to be purchased.

For SEPM 12.1 Release To Manufacturing (RTM) version (version number 12.1.671.4971) :

1: In the SEPM go to Admin > Servers
2: Right-click on the entry with the database servers name and instance, possibly localhost, under Local site and go to "Edit Database Properties"
3: Under the General tab change the option "Delete clients that have not connected for" to be 1 day then click OK
4: Right click on database again and click on "Rebuild indexes now" and "Truncate transaction log now"

For SEPM 12.1 RU1 (version number 12.1.1000) or later :

1: In the SEPM go to Admin > Domains
2: Select Domain and under Tasks "Edit Domain Properties"
3: Under the General tab change the option "Delete clients that have not connected for" to be 1 day then click OK
4: Go to Admin > Servers
5: Right-click on the entry with the database servers name and instance, possibly localhost, under Local site and go to "Edit Database Properties"
6: Under the General tab change the options and check on "Rebuild indexes" and "Truncate the database transaction logs"





Article URL http://www.symantec.com/docs/TECH168121


Terms of use for this information are found in Legal Notices