Saturday, 26 August 2017 14:07

The Case of 'Something Went Wrong'

Written by
Rate this item
(1 Vote)


As you’ve probably surmised by my blog posts and my Twitter ramblings, I like to push OSD to its limits. Besides keeping my deployments running smoothly, my vigilance sometimes helps me spot potential problems before they actually become an issue for my customers. The case opened wide when I started testing a pre-release Windows 10 1703 Insider Build based MDT task sequence. During the specialize phase, my VMs would run into a blue-ish screen stating that "Something went wrong".

The first time I ran into the issue I pressed the "Try again" button, but that made no difference and after an extensive waiting period looking at the "Wheel of Wait" I ended up with the same error message. Hitting "Cancel" would make the OSD proceed. I’d typically chalk up an error message like this to an Insider Build issue, but I hit the issue in the next Insider Build as well as in the shipping version of 1703, so I had to face the disappointing reality that there was an underlying issue that needed my attention.

This issue also only occured while trying to join machines to a domain, but not when doing workgroup based deployments. What made the situation especially frustrating was that neither the Deployment Summary nor the Windows setup logs showed any errors. Adding to the mystery, all machines ended up joined to a domain. Since I could not get visibility into what was going on, I plowed on and made an educated guess that the error was somehow related to the domain join being executed - and running into an unspecified issue - during the specialize phase: by default the unattend.xml specifies to join the domain. I quickly went through the ZTIDomainJoin log file and verified that my machines were in fact not domain joined after the first auto logon. This confirmed my assumption that the domain join step failed initially. Once the execution of the task sequence resumed and the "Recover from domain" step verified the target computer did not join a domain, the ZTIDomainJoin script performed the domain join and remedied the situation.

Confident I’d solved the mystery, I opened the unattend.xml associated with my Windows 10 1703 task sequence located in %DeployRoot%\Control\%TaskSequenceID% and removed the unattended domain join entry Microsoft-Windows-UnattendedJoin.

<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="">

I restarted the OS deployment to verify my workaround, and to my satisfaction, the task sequence completed without any hiccups. The case was closed! As for why the domain join issues started occuring in Windows 10 1703 "Creators Update", I haven’t had the time or need to investigate further. The point of this article is to highlight an issue in the shipping version of Windows 10 1703 that you might run into, especially if you deploy domain joined machines using MDT and / or SCCM.

Read 1200 times Last modified on Saturday, 26 August 2017 14:17

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.

Recent Posts

  • Automating Multi-node Tableau Server Environment
    After a few weeks off, I am delighted to announce that I have returned full time, once again delivering somewhat…
    Written on Monday, 19 February 2018 11:01
  • The Case of Missing TPM P@ssword
    As my regular blog readers will be aware (yes, all three of you), there is something increasingly traditional about me…
    Written on Thursday, 25 January 2018 10:04
  • The Case of "Just a Moment..."
    A key part of any complete end-to-end deployment project is analysis of the resulting logs to identify root causes for…
    Written on Tuesday, 16 January 2018 12:57
  • How to Automate Input Preferences during OSD
    A few days ago I stumbled upon a question on the Microsoft Deployment Toolkit (MDT) forum where a user asked…
    Written on Monday, 15 January 2018 12:36
  • Disabling Cortana Voice Support during OOBE
    Yesterday I came across a Twitter thread in which multiple users detailed their beef with the revamped setup experience of…
    Written on Tuesday, 12 December 2017 10:04
  • Fixing "Windows update reboot is pending" during OSD
    Automated OS deployment became common as IT professionals install systems using tools like Microsoft Deployment Toolkit or System Center Configuration…
    Written on Tuesday, 28 November 2017 08:44