WDS on Windows Server 2012 - Strange Domain Add behavior for Client

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.

Example:
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.

Thanks.
-Stephen
lapavoniAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
WDS only works properly if you "drop" a fully sysprepped image for deployment. If you aren't sysprepping the image first, you'll have issues, guaranteed. That's what you are hitting. You are installing an image that hasn't been prepped for deployment so existing GUIDs are gumming up the works. That isn't unique to WDS. You'd have the issue with any deployment strategy that clones images.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lapavoniAuthor Commented:
Of course, in my long description I didn't mention that the image is properly sysprepped.  Good assumption, though.
0
lapavoniAuthor Commented:
OK, it seems that in the PreStaging environment of WDS 2012, the computers are populated by the netbootGUID attribute. I'm guessing this computer physically matched to that attribute for a system in that list and the computer name was reused. That PreStaged list is not very intuitive. It's linked directly into AD. I "deleted" a couple computer names from that list and it actually deleted the computer objects from AD.  I cleared the netbootGUID attributes from all machines in that list and they all disappeared, which is what I wanted.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.