Duplicate PC's for AD intergrated folders

[Jaap 0]

In era every workstation is created 40+ times resulting in 20.000 objects and counting. I have no idea why en and how to solve this.

Every workstation is reinstalled with MDT so there cannot be a duplicate SID. PC names do get reused but most pc's haven't been reinstalled in ages.

I do notice on the workstation (mixed windows 7 and Windows 10 LTSC) lot's of reinstall of  reconfiguration of the agents after each reboot.

 

Howto resolve / debug this?

Btw this is an upgraded ERA VM....

 

 

[MartinK 378]

I would recommend to check configuration/existence of following tasks that could possibly result in this:

• Client task "Reset cloned task": please check whether there exists any instance of this task and if so, disable it.
• Serve tasks for synchronization: I would recommend to disable AD synchronization tasks, just to be sure they are not source of this problem.

Also you mentioned that AGENTs are reconfigured after reboot. Could you double check your method of deployment? Cloning as described in your post would be also result of repeated uninstallation+installation of AGENT - is there any chance AGENT gets uninstalled after reboot? Asking because this was one of workaround for ERAv6 problems with cloning devices, but it has been resolved by release of ESMC 7.0 where native support for detection and remediation of cloned devices was introduced.

 

[Jaap 0]

Hi Martin,

Sorry for the long delay, I've missed your response due to holliday's.

I did indeed have a client task running and (because I couldn't find a  disable option) deleted it.  The import task for AD accounts has been changed for now so i hope it doesn't import any pc's anymore.

Apperently I've not been clear enough on cloning: we don't do cloning anymore. Every PC is reinstalled with MDT from the original MS ISO.

The next question is: how to get rid of all the duplicate entries in our database?

[MichalJ 434]

There are multiple options how to remove the devices: 

1. Delete not connecting computers task
2. Static group synchronization task, with correct setting for computer extinction handling 
3. Manually (will take some time, as this is a resource heavy operation). 

[Jaap 0]

I did choose option 1. and created a new task wich should run every month, set to delete computer that haven't connected in 30 days or more. I did run the job immediately and went on a holiday.

2 weeks later I've looked into it and it didn't delete anything. The job is stil "running" but I can't find any detail logging in the gui or console what is happening or where it stuck.

The default import job (option 2) has always have had the delete option selected....

What's the next step (if any) and where are the detailed logs from a server task?

 

[MichalJ 434]

@Jaap I have discussed this with developers, and what i would recommend is to contact ESET technical support in the Netherlands. It looks that something is not behaving correctly in your environment, and without proper set of logs we won´t be able to provide further advice. You can reference this thread when creating the support ticket. 

[Jaap 0]

On 9/21/2019 at 3:08 PM, Jaap said:

where are the detailed logs from a server task?

Ok I'll do that. Last question: see above, where to look for the (and all other logs)?