Windows 10 Pro 1703 won't join AD domain when a dash is in machine name

Topic

New Reply

Found an odd bug this last weekend in Windows 10 Pro 1703 (and I am assuming ENT) when joining a workstation to a Server 2012 R2 domain.

If your machine naming convention includes dash(es) in the name, it may fail to join the domain with the error: “The domain controller does not meet the version requirement for this operation.”

This was not a problem with all older versions for Windows 10 Pro through 1607, and of course never with Windows 8.1 or 7 Pro.

We have long used a naming convention that includes some coded information about the machine, department, client etc.  It might look like this:  ND-CAD-W10-001 (company code ND, CAD Department, OS main version, and a number in order of build.)

When we removed the dashes from the machine name and rebooted, we were able to successfully join the domain.

So the takeaway for us is that as we approach 1703 achieving CBB status in the next month or two – it’s not ready yet!

 

Notes:  We tested with a much shorter machine name variant and the dash problem was reproducible. (So it’s not that we are close to the length limit.)

~ Group "Weekend" ~

Reply | Quote

Replies

I didn’t perform a full test, but I renamed a Windows 10 1703 already joined to a Windows 2016 domain to include dash and it worked.
There are difference from your setup.
I use a Windows 2016 Forest and Domain, while you use Windows 2012 R2 AD Domain.
My machine is already joined and only rename it.

Could you please join to AD a machine without dashes in name and rename it after it is joined to see if it works.

Reply | Quote