Forum Discussion
Mitch_Mosier
Jun 23, 2022Copper Contributor
NETLOGON error in Active Directory
I had an employee's PC crash a few weeks ago and I had to clone the failing HDD in question over to a new SSD. When I put the PC back in place, it had the same name as the old PC so I started getting...
Kusters_IT
Jun 23, 2022MCT
Mitch_Mosier since you have a clone of the harddisk at hand, it doesn't hurt to try to sysprep the device after writing the clone to disk. SInce you mention you are able to try to rejoin the domain, I assume you have access to a local administrator user of the machine?
Try running (elevated) "sysprep.exe /generalize /shutdown /oobe"
This will reset your system's SID, which is the primary identifier for the device in the domain, and should solve your issue. If doesn't hurt to afterwards choose a different hostname if this is allowed in your environment.
- Mitch_MosierJun 23, 2022Copper ContributorThe device has already been cloned. When I cloned to the SSD the device had the same hostname as the previous machine in AD. Which is what started the NETLOGON errors. So I deleted the computer in question from the ADSI edit menu, then logged into the local admin account and rejoined the PC to the domain with a new name thinking this would resolve my issue. However it is still happening.
I'll give this command a shot though, I'll have to wait until early morning when the PC is not in use though. Thanks for the suggestion!