![]() ![]() If you have clients that are strictly running on virtual machines which are reloaded or re-imaged on a regular basis, create a separate client group for those clients. If you know in advance that a group of systems are going to be re-imaged, you can remove those clients from the console ahead of time. Solution 1: Remove the client from SEPM if it is going to be rebuilt or re-imaged. ![]() There are 2 solutions for this issue as it relates to systems or sessions that have been re-imaged/reloaded. The second cause for this is related to an issue with moving clients to a different OU in Active Directory. So if this changes and the re-imaged system checks in, it is recognized as a new client.Įxample: The IP and computer name are the same, yet the database still shows a different Unique ID. Things we know: Each installation of Symantec Endpoint Protection (SEP) randomly creates a "Unique Identifier" for the client. Symantec Endpoint Protection 11.x and 12.1Ĭurrent Theory: The first possible cause for this is when an Endpoint has been re-imaged (whether in a virtual machine or on a physical system). Duplicate clients are appearing in Symantec Endpoint Protection Manager (SEPM) console. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |