Hi,
We have a task that applies a system configuration that joins a machine to the domain and into a certain OU. This task has been working for years on our Windows 7 and 8 machines but yesterday I found that it fails to join a Windows 10 machine to the domain.
When digging through the 'C:\Windows\debug\netsetup.txt" file I find the following for the account being used to perform that join.
Account: <DOMAIN>.local\1b9q5bPl3jPQ9sTEb5+DiAvHG0oFhHErmAXveDPV++WwGuA4IZUjoQUw5mgzQA7y32obYg9stL7/VG7YbeZnQ0duQLq9dPA7+AtRbTtPWi3kBgK2fRPCDU+dMege2WsGZ9g=
If i add the machine to the domain manually it works, and I see the following:
Account: <DOMAIN>.local\<USER_samaccountname>
Apologies for the heavy censoring but you I'm sure you understand. Instead of the account I get that string of letter and numbers.
Interestingly I have a number of other "Apply System Configuration" tasks that do not rename the machine or change it's domain but simply move it to a different OU. These use the exact same account and they work okay!
Anyone else experience this?
I have a support ticket open so will pass on anything we find when we do.
Howard
