It did however remove all my policies associated with OUs and I spent two hours on phone with Engineer and then another four fixing settings/policies in my SEPM. It did not remove or correct my duplicates issues. I had a Engineer call and we walked through the above steps together. I have chatted with Symantec support numerous times on this. Setting this value to 1 or 2 will likely cause all your clients to be removed after a weekend.Ī recommended value for large enterprise environments would be 7 to 14 days.īE wary of these directions, I have been struggling with duplicate in SEPM for a while now.
#Symantec endpoint manager add clients Offline#
It is important to consider clients that are offline over the weekend. NOTE: In version 12.1 of the SEPM, the location for adjusting the setting to delete clients which have not connected for X number of days has moved:ģ) Under Tasks, select Edit Domain Properties.Ĥ) In the Edit Domain Properties window, on the default General tab, note the option to "Delete clients that have not connected for specified time."ĥ) Configuring a low value for this setting would clear up the duplicates more quickly. Solution 2: Configure SEPM to remove clients which have not connected within a specific number of days.ģ) Right click on the Site where your management servers are located and choose Edit PropertiesĤ) Check "Delete Clients that have not connected for _ Days"
#Symantec endpoint manager add clients how to#
When it comes time to re-image them, they will be easier to locate when placed in their own group.ġ) How to prepare a Symantec Endpoint Protection 12.1 client for cloning (image)Ģ) How to repair duplicate IDs on cloned Symantec Endpoint Protection 12.1 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.