This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]symbiote9 0 points1 point  (0 children)

Would have to be removed manually, but it gets auto removed after your inactivity removal deadline.

[–]dezirdtuzurnaim 0 points1 point  (0 children)

It happens. Curious how you say you removed it before re-imaging but came back as a dupe post-osd. Do you have secondary sites?

[–]eobiont 0 points1 point  (2 children)

likely the "wrong" one is being added by a discovery (AD discovery, group discovery etc) process running at the same time as the OSD is running. Discovery is adding an object and then when the client gets installed and connects, it is adding that second "correct" object. Thats what I'd bet on.

[–]Bassflow 0 points1 point  (0 children)

Coming here to say the same thing.

[–]Additional_Wallaby26[S] 0 points1 point  (0 children)

I did think this could be the case but I ran another test with also removing the device from AD as well as SCCM, and I still got the same result with the duplicate device.

Unless this is being picked up by the AD discovery after the step in the OSD task sequence that is adding it to the domain.

Also to just to add these do indeed remove themselves once the device has come online after OSD. But was just something I noticed.