WDS re-imaging an existing AD machine results in DESKTOP-randomname and no domain join

Author

Comment

Wes

Senior Member
Registered:1451679330
Posts: 230

Posted 1458696678	Reply with quote #1

Hi all, We have a weird issue. Pre-existing WDS servers... We are now pushing out Win10 instead of Win8.1 If we reimage a machine that already exists in AD, it apparently fails to domain join and is named DESKTOP-randomcharacters If we delete the AD computer account and reimage, it joins fine. This is different from previous behavior where it would automatically adopt the existing computer account. Anyone have any ideas? thanks! Wes
0 0 0

Infradeploy

Senior Member
Registered:1451680221
Posts: 166

Posted 1458719617	Reply with quote #2

To be sure: The domain join account has write/delete rights on the workstation objects in AD? __________________ Have SpaceSuit, Will Travel
0 0 0

Wes

Senior Member
Registered:1451679330
Posts: 230

Posted 1458719801	Reply with quote #3

Yep, same account we've always used...
0 0 0

Infradeploy

Senior Member
Registered:1451680221
Posts: 166

Posted 1458722162	Reply with quote #4

Do you use bitlocker? If so the bitlocker object as a workstation subobject maybe can't be deleted, or reused __________________ Have SpaceSuit, Will Travel
0 0 0

Wes

Senior Member
Registered:1451679330
Posts: 230

Infradeploy

Senior Member
Registered:1451680221
Posts: 166

Posted 1458724467	Reply with quote #6

There's the netsetup.log to see why domain join failed. Anything in there? __________________ Have SpaceSuit, Will Travel
0 0 0

Wes

Senior Member
Registered:1451679330
Posts: 230

Posted 1458724742	Reply with quote #7

I've asked my helpdesk to take a look at that - hopefully more info tomorrow! Thanks :-)
0 0 0

donoli

Senior Member
Registered:1454887308
Posts: 583

Posted 1458737576	Reply with quote #8

http://superuser.com/questions/966863/windows-10-cant-rejoin-domain-to-windows-server-2003 It's not the exact problem that you have but it might give some ideas. Another site said something about using the server IP for the DNS entry. I don't know.
0 0 0

Wes

Senior Member
Registered:1451679330
Posts: 230

Posted 1458750635	Reply with quote #9

Interesting although we are all 2012r2... And we had no problem with win10 before... This just started this week. Only difference is that we are now using an LTSB image instead of a CB image...but that same LTSB image is working fine in another domain... Will see how it gots at another site/server in the same domain...
0 0 0

Previous Topic | Next Topic