Hi,
Looking at the picture above, I think there is a little confusion.
You are saying you have 'duplicates' because there are multiple machines with the same host name listed in the Symantec Console. Although this is, of course, a 'duplicate', normally what I think when someone says duplicates is they have two different computers that look the same.
In your case, you have a single computer that has been reimaged and it now has a 'duplicate', as in two or more entries in the console.
Is this correct?
In MR4 and earlier Hardware ID was based on the MAC address so this wouldn't happen. RU5 changed the process, but it still has a solution.
If you want the re-imaged computer to show up as the same entry (as in, the existing entry, without creating a new 'duplicate entry), do the following.
-
If this is an MR4 or earlier client
-
Copy out the hardware ID registry key before you image the client (You can also get the HW ID out of the SEPM console if you've already wiped the drive).
-
Reimage the system, but don't let it connect to SEPM.
-
Install the RU5 (or later) SEP client if it has not been installed already. (i.e. it was not part of the ghost image)
-
Stop the SEP client ( Run: smc -stop )
Delete the hardware ID registry key and the sephwid.xml file if they exists.
-
Restore the old registry key that you copied out in step 1.
-
Start the client.
The client should now use the old HW ID key as it's HW ID. This allows the client to connect to the same entry in the SEPM console. Thus, no duplicates.
An alternate to the above is, if the sephwid.xml file has been created, just delete the registry hardware ID key and then replace the HWID value found in the sephwid.xml with the old HWID value.
If you are reimaging clients that already have RU5 or later installed, you can use the same steps, but these may be a little simpler:
-
Copy the sephwid.xml file off the client before you wipe the drive.
-
Image the drive. Do not let the client connect to SEPM.
-
Install SEP RU5 or later if it is not already installed or part of the image.
-
Stop the SEP client.
-
Place the sephwid.xml file from step 1 back onto the client (overwrite the current sephwid.xml if one exists)
-
Start the client.
Note, when I say, "Do not let the client connect to SEPM", if you prevent the client from starting, this would fulfill the same purpose.
I hope that helps!
-Jesse