You have deployed multiple Windows computers, virtual or physical, by cloning a base hard drive image that includes a Symantec Endpoint Protection (SEP) 12.1 client. Now there are duplicate client IDs in the Symantec Endpoint Protection Manager (SEPM) database, and the cloned computers are reporting as the same client to the SEPM.
Duplicate Symantec Endpoint Protection client IDs occur if the base image was not prepared for cloning. For more information, learn how to prepare a Symantec Endpoint Protection 12.1 client for cloning.
There are three high-level steps to repair duplicate Symantec Endpoint Protection client IDs.
- Identify the clients
- Repair the clients
- Clean up the client view in Symantec Endpoint Protection Manager
If you already know the IP addresses or names of the systems affected by this issue you can skip to Step 2. If you have multiple SEPMs, disable any replication relationships between them and perform the steps below on each SEPM. You should do this process on all servers before re-enabling replication.
- Stop the Symantec Endpoint Protection Manager service and the Symantec Endpoint Protection Manager Webserver service. When these services are stopped, backup and then delete the client connection log file: Symantec Endpoint Protection Manager install folder\data\inbox\log\ersecreg.log
Restart the services after the log file has been deleted.
- Wait one heartbeat period so clients can reconnect to the SEPM. If your communication settings have a 30 minute heartbeat, then wait for at least 30 minutes. In the Symantec Endpoint Protection Manager, the heartbeat settings are under Clients > Policies > Communication settings.
- Run the SEPM Repair Tool using the instructions provided in ReadMe.txt (see Attachments for both). The output file from the SEPM Repair Tool is the list of clients affected by the duplicate ID issue. Save this file.
In the first steps below, you disable SMC password protection for the affected clients. If you do not have SMC password protection enabled, skip to step 4 of this section.
- Using the output list from the SEPM Repair Tool, find the affected clients in Symantec Endpoint Protection Manager and move them to a new temporary group.
- Disable the clients SMC password protection.
- In Clients > Policies > General Settings > Security Settings, uncheck Require a password to stop the client service (RU4 MP1 and earlier SEPM)
- In Clients > Policies > Password Settings, uncheck Require a password to stop the client service (RU5+ SEPM)
- Wait for one heartbeat interval to make sure the policy is updated for each client.
- Copy RepairClonedImage.exe to the computer that runs Symantec Endpoint Protection Manager.
- Rename RepairClonedImage.exe to Setup.exe.
- In the Client Deployment Wizard, deploy the renamed tool to the affected computers, using the output file from the SEPM Repair Tool as the list of clients.
If you do not wish to use the Client Deployment Wizard, you may use any software deployment method of your choice, or you can run the tool manually on the target computers. If you do not use the Client Deployment Wizard, administrator rights will be required when running the tool.
By default, the RepairClonedImage tool will run silently, with no response to the user for success or failure. You may specify the -v command line option to show notification on success or failure.
- After the tool has been deployed, the clients should show up as online in the SEPM console.
If you moved the clients to a temporary group, you may now move all of the online clients from the temporary group back to their original group.
Resetting the client IDs will result in invalid offline clients being left in the client view in Symantec Endpoint Protection Manager. This could affect licensing and reporting. There are two options for removing the clients:
- Let the clients time out according to the Symantec Endpoint Protection Manager site's aging criteria. This is 30 days by default.
- Manually delete the offline clients from the Client view page.
RepairClonedImage.zip (83.7 KB)
SEPM Repair v2
SEPMRepairTool_v2.zip (14.6 KB)
ReadMe.txt (539.0 B)
Rate this Article