I am experiencing problems with machines not joining the domain correctly during a Windows 10 SCCM MDT integrated task sequence build.
SCCM CB 1806
Latest ADK & MDT installed.
Boot Image updated
Unique Active Directory Organisational Units (OU) per office are specified in a customsettings.ini file. The task sequence completes but machine accounts are not created in the correct OU. In addition, sometimes machine accounts are not created, and finally sometimes machine accounts are created but the trust relationship is broken.
This only occurs on Windows 10, our current Windows 7 build experiences no issues. Machine accounts are created in the correct OU and no trust relationship issues. The same customsettings.ini file is used in both the Windows 7 and Windows 10 build.
Customsettings.ini – screenshot shows example of one of the rules of the default gateway section, the MachineObjectOU specifies the AD OU I want the machine account to be placed into.
ZTIGather.log - Output shows correct information has been processed during a gather.
However, the netsetup.log shows the OU specified for UK_Manchester gateway section within the customsettings.ini file is ignored. The machine account is created in the default OU specified in the Apply Network Settings Task Sequence step. The en-GB settings appear to be processed as the locale is set to UK English.
In addition, sometimes the machines are not able to logon to the domain when the build completes. The task sequence completes but the following message is displayed “We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organisations network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.”
If the machine account object is deleted from Active Directory, the subsequent build domain join is successful albeit the machine account is not created in the correct OU. As previously stated, the customsettings.ini file works correctly with my Windows 7 x64 build.
The AD account used to join the machine to the domain has full control over all AD OU’s and I am able to use the account to join domain’s manually. Also, the same account is used in our Windows 7 build without any issues.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I am experiencing problems with machines not joining the domain correctly during a Windows 10 SCCM MDT integrated task sequence build.
Unique Active Directory Organisational Units (OU) per office are specified in a customsettings.ini file. The task sequence completes but machine accounts are not created in the correct OU. In addition, sometimes machine accounts are not created, and finally sometimes machine accounts are created but the trust relationship is broken.
This only occurs on Windows 10, our current Windows 7 build experiences no issues. Machine accounts are created in the correct OU and no trust relationship issues. The same customsettings.ini file is used in both the Windows 7 and Windows 10 build.
Customsettings.ini – screenshot shows example of one of the rules of the default gateway section, the MachineObjectOU specifies the AD OU I want the machine account to be placed into.
ZTIGather.log - Output shows correct information has been processed during a gather.
However, the netsetup.log shows the OU specified for UK_Manchester gateway section within the customsettings.ini file is ignored. The machine account is created in the default OU specified in the Apply Network Settings Task Sequence step. The en-GB settings appear to be processed as the locale is set to UK English.
In addition, sometimes the machines are not able to logon to the domain when the build completes. The task sequence completes but the following message is displayed “We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organisations network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.”
If the machine account object is deleted from Active Directory, the subsequent build domain join is successful albeit the machine account is not created in the correct OU. As previously stated, the customsettings.ini file works correctly with my Windows 7 x64 build.
The AD account used to join the machine to the domain has full control over all AD OU’s and I am able to use the account to join domain’s manually. Also, the same account is used in our Windows 7 build without any issues.
Any help or suggestions would be appreciated.
Share this post
Link to post
Share on other sites