Hello,
We use McAfee Drive Encryption, we assign laptop users to their designated laptop (from ePO v5.10 - Data Protection/Encryption Users).
Duplicate systems are causing an issue when we are trying to assign a laptop.
Is there a query or automated task available that can be set up to delete the duplicate entry based on date (last communication)?
Thanks
Solved! Go to Solution.
You first might want to look into why you are getting a lot of duplicates. Does it occur after an AD sync, or when? What version of epo and what agent version? Do you have a task or 3rd party deployment that deploys agents with a forceinstall? See kb's 60757 and 89427 for some issues. Check audit log for when one of the duplicates were created and then compare it with any tasks, server or client, that might have been running at the time to possibly cause the duplicates. Otherwise you can use this script in sql to remove duplicates. Please validate table names, as different versions of epo name them slightly different.
delete from epoleafnode where exists (select * from epoleafnode as l where l.nodename=epoleafnode.nodename and l.autoid!=epoleafnode.autoid and l.lastupdate>epoleafnode.lastupdate)
SET rowcount 1000
delete from epoleafnode where exists (select * from epoleafnode as l where l.nodename=epoleafnode.nodename and l.autoid!=epoleafnode.autoid and l.lastupdate>epoleafnode.lastupdate)
WHILE @@rowcount > 0
BEGIN
delete from epoleafnode where exists (select * from epoleafnode as l where l.nodename=epoleafnode.nodename and l.autoid!=epoleafnode.autoid and l.lastupdate>epoleafnode.lastupdate)
END
SET rowcount 0
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
You first might want to look into why you are getting a lot of duplicates. Does it occur after an AD sync, or when? What version of epo and what agent version? Do you have a task or 3rd party deployment that deploys agents with a forceinstall? See kb's 60757 and 89427 for some issues. Check audit log for when one of the duplicates were created and then compare it with any tasks, server or client, that might have been running at the time to possibly cause the duplicates. Otherwise you can use this script in sql to remove duplicates. Please validate table names, as different versions of epo name them slightly different.
delete from epoleafnode where exists (select * from epoleafnode as l where l.nodename=epoleafnode.nodename and l.autoid!=epoleafnode.autoid and l.lastupdate>epoleafnode.lastupdate)
SET rowcount 1000
delete from epoleafnode where exists (select * from epoleafnode as l where l.nodename=epoleafnode.nodename and l.autoid!=epoleafnode.autoid and l.lastupdate>epoleafnode.lastupdate)
WHILE @@rowcount > 0
BEGIN
delete from epoleafnode where exists (select * from epoleafnode as l where l.nodename=epoleafnode.nodename and l.autoid!=epoleafnode.autoid and l.lastupdate>epoleafnode.lastupdate)
END
SET rowcount 0
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center
Corporate Headquarters
2821 Mission College Blvd.
Santa Clara, CA 95054 USA