At this site, SEPM Groups are imported from AD. I've imported ALL of AD, not just OUs containing computer objects, so I'm susceptible to the variation on the duplicate client bug where the duplicates appear as Users in user OUs who have logged on to a computer affected by the duplicate client bug.
In MR4 MP2, I had 2 User objects in SEPM that shouldn't exist that were created by the duplicate client bug. In this case, it was triggered by a NIC change and a bare metal Windows reinstall while MR4 MP2 was installed on SEPM and client. Now, after upgrade to RU5 on both SEPM and problem client, the duplicates are still there.
On the advice of a poster in another thread, I ran the script that's supposed to remove dupes. But, as I expected, it didn't work, because the documentation
still says the script only works when the duplicates are in Default Group. In my scenario, they are in a user OU. And, unfortunately, one
still can't delete SEPM objects when they're imported from AD.
- Is there a way to surgically remove these duplicates? Or do I need to delete the AD-imported SEPM Groups, re-import them, and re-assign Policies to the newly-imported Groups?
- As far as Symantec or any users with relevant experience with AD-imported Groups knows, is the duplicate client bug with AD-imported Groups really, really fixed in RU5?
TIA