Greetings. I just migrated WDS from 2008 to 2012. The WDS process works as expected. PXE boot for the client works fine. Image is installed properly. However, I dropped an image on a system that used to have a computer account in the domain. I deleted the computer account before deploying the image. After a couple restarts, I was unable to log onto the system with a domain account. I logged on locally, renamed the computer and added it to the domain.
This part is strange. Somewhere, the computer picked up an existing GUID or ID of a random computer in AD. When I renamed the computer, it actually renamed a different computer in AD.
Imaged computer - instead of random name, it picked up *existing* AD computer name ! i.e. ComputerABC
Renamed computer i.e. ComputerDEF
Instead of a NEW "ComputerDEF" appearing in AD/Computers, "ComputerDEF" has now *replaced* one of my user machines (formerly ComputerABC) !
I fixed the problem by removing the computer from the domain, taking it off the network and giving it a completely new name. I then restored the AD object of my former computer. All was well with the new system, but the old, existing system had apparently some SID/GUID issues, so I had to manually add it back into AD from the computer itself. All is well now.
Can anyone explain to me why one computer would hijack the name (SID ? GUID ?) of an existing computer in AD ? I considered duplicated MAC addresses, but that wasn't it. I thought maybe something about PreProvisioning in WDS 2012 now ? I don't fully understand that concept - that has to do with RE-imaging an existing computer, right ? WDS keeps the GUID in sync between AD and its own database, right ? Anyway, I'd like to prevent this from happening again when I image new (or replacement) systems, so if anyone has some insight, that would be great to know.