none
Server 2012 Join Domain issues RRS feed

  • Question

  • This issue isn't specific to MDT but I'm hoping that if anyone is running into this issue, it would be people using MDT. The issue is when you deploy Server 2012 with a static IP, the domain join during OS customization fails which is expected, but it takes 15 minutes to fail. This seriously slows down the build process. With 2008 and 2008R2, the failure was pretty fast and the recover from domain task took care of the domain join. 

    Has anyone else run into this and figured out how to make this process go faster?

    Thanks,
    Rich

    Tuesday, March 25, 2014 2:59 PM

Answers

  • Remove the Domain Join section from your unattend.xml template file in your task sequence.

        <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
          <Identification>
            <Credentials>
              <Username></Username>
              <Domain></Domain>
              <Password></Password>
            </Credentials>
            <JoinDomain></JoinDomain>
            <JoinWorkgroup></JoinWorkgroup>
            <MachineObjectOU></MachineObjectOU>
          </Identification>
        </component>
    


    Keith Garner - keithga.wordpress.com

    Tuesday, March 25, 2014 10:37 PM
    Moderator

All replies

  • Remove the Domain Join section from your unattend.xml template file in your task sequence.

        <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
          <Identification>
            <Credentials>
              <Username></Username>
              <Domain></Domain>
              <Password></Password>
            </Credentials>
            <JoinDomain></JoinDomain>
            <JoinWorkgroup></JoinWorkgroup>
            <MachineObjectOU></MachineObjectOU>
          </Identification>
        </component>
    


    Keith Garner - keithga.wordpress.com

    Tuesday, March 25, 2014 10:37 PM
    Moderator
  • Remove the Domain Join section from your unattend.xml template file in your task sequence.

        <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
          <Identification>
            <Credentials>
              <Username></Username>
              <Domain></Domain>
              <Password></Password>
            </Credentials>
            <JoinDomain></JoinDomain>
            <JoinWorkgroup></JoinWorkgroup>
            <MachineObjectOU></MachineObjectOU>
          </Identification>
        </component>


    Keith Garner - keithga.wordpress.com

    I know this is an old thread, but I'm seeing this exact behavior on a Windows 10 deployment. It gets stuck on a specific DC which rejects the credentials (for around 15 minutes), before moving on with the process and contacting a different DC at the end of the TS process and successfully joining the domain.

    Is there any way to skip this process (the join in the middle) without editing the unattend.xml file?

    Thursday, March 30, 2017 5:35 PM