Endpoint Protection

Using SEP 12.1.5...About a dozen of our Windows 7 SEP clients do not show in the SEPM console. What can cause this? The clients appear to be fine (no errors) and actively managed by the SEPM, since they are receiving regular definition updates and show to connect to the SEPM regularly. I've tried complete uninstalls/re-installs. I thought possibly DNS resolution, but that does not seem to be an issue between these clients and the SEPM. Any ideas or suggestions? Thank you!

Are you using clone system ?

try this

Repair duplicate IDs on cloned Endpoint Protection 12.1 clients

http://www.symantec.com/business/support/index?pag...

Hey birdman,

If u reinstall without delete instances of sepwhid.xml, still with the same Hardware ID and probably this is the cause of the problem.

Search sepwhid.xml in these locations and delete the file before u install again.

• C:\Program Files\Common Files\Symantec Shared\HWID\
• <computercode style="font-family: 'Courier New'; font-size: 12pt; color: rgb(34, 34, 34); line-height: 20px;"></computercode><computercode style="font-family: 'Courier New'; font-size: 12pt; color: rgb(34, 34, 34); line-height: 20px;"></computercode>C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Config
• <computercode style="font-family: 'Courier New'; font-size: 12pt; color: rgb(34, 34, 34); line-height: 20px;"></computercode>C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\PersistedData\
• <computercode style="font-family: 'Courier New'; font-size: 12pt; color: rgb(34, 34, 34); line-height: 20px;"></computercode>C:\ProgramData\Symantec\Symantec Endpoint Protection\PersistedData\
• <computercode style="font-family: 'Courier New'; font-size: 12pt; color: rgb(34, 34, 34); line-height: 20px;"></computercode>C:\Users\All Users\Symantec\Symantec Endpoint Protection\PersistedData

How to prepare SEP to cloning:

http://www.symantec.com/business/support/index?page=content&id=HOWTO54706

Hope it helps!

This is caused by duplicate hardware IDs. Did you follow this:

How to prepare a Symantec Endpoint Protection 12.1.x client for cloning

For fixing:

TECH163349   Repair duplicate IDs on cloned Endpoint Protection 12.1 clients