In a perfect world a device will just getting AzureAD join after it is unboxed – but there is time when this is not possible – then you need to deploy Windows 10
But still want to give the user the OOBE (Out Of Box Experience) this is a blogpost about who to achieved this goal with MDT.
First you need to run the sysprep /oobe command after the image has been deployed to the device – and you need to be sure that the MDT task sequence has ended before you run sysprep /oobe.
To achieved this I use Johan Arwidmark’s “Final Configuration” script for MDT 2013
Make the change to FinalConfig.hta :
oShell.run “c:\windows\system32\sysprep\sysprep.exe /oobe /reboot”,1,False
Created a Application in MDT with the Final Configuration script.
Add the application add the end of the MDT Task Sequence
Remember that when you do this:
- The Windows device has to be in a workgroup.
- Skip Final Summery has to be set to YES
The user experience will be like this.
For the demo purpose I can select a Task Sequence
Set a computer name
After the image deployment and run of the Final Configuration
The user will experience the standard Windows 10 OOBE.
First select the language
Here’s the legal stuff
Click Use Express settings
Select “Join Azure AD”
Any additional steps needed to get this to work? And is it possible to skip / preselect some of the oobe pages so you basically only see the Choose how you’ll connect? BR Kristian
Hi, No additional steps needed. At my knowledge it is not possible to skip/preselect any og the steps at the moment. You can only hide sections not a single page. /Per
Hi! Hmm we have not been able to get this to work. You mention making a change to the FinalConfig.hta file, however I cannot see the what the change is, to me it looks just like the original file? Should this work with 1607?
Ty for getting back to me! BR Kristian
Hi, Yes you can do that. Have been using this for over a year for Azure AD and Intune. No need for “Final Configuration” and you can use “SkipFinalSummary=YES” if you want. You must create a modified unattend.xml and set the values of the oobe pages you want to skip. Before I run sysprep I copy my modified unattend.xml to the computer. Dont use /reboot with sysprep beacuse it will breake the tasksequense. After a reboot or shutdown and start you will only see the “Choose how you’ll connect?”. I use “FinishAction=SHUTDOWN” so when the user start the computer the basically only need to log in.
“%WINDIR%\System32\Sysprep\sysprep.exe” /oobe /quit /unattend:”PathToCopiedUnattend.xml”./Tobias
Could you please give me more information how to do this. I need to create a Windows 10 1703 image for Byod computers (students). I used Windows imaging and configuration Designer with 1608 to create a ready to install USB media but this function is retired with 1703.
Oh sorry, I had compared with a previously modified FinalConfig.hta file! Now I took a fresh one from source and will do a new test. BR Kristian
I have now done a number of tests and I will cannot get it to work. Is there a good way to debug this? BR Kristian
If anyone else has this issue, I found a solution without using Final Configuration 2013. I just created a Run Command Line task with “cmd /c c:\windows\system32\sysprep\sysprep.exe /oobe /quiet /quit” as the last task in the task sequence. Together with “FinishAction=REBOOT” in the rules (CustomSettings.ini). Then you also avoid triggering the dirty environment flag. If needed add a reboot task just before the sysprep task. BR Kristian
Hello, I’m having issues with the final MDT configuration in general. For example, they said to put this final MDT configuration at the end in state restore.
But when you do that, it does trigger the dirty environment saying this task is suspended . I don’t want oobe as yet because I want to run a custom script after the creation of WIM. I’m running MDT 2013 update 2 prepping windows 10 ver 1803. Should I try your approach?
When I add the line oShell.run “c:\windows\system3\sysprep\sysprep.exe /oobe /reboot”,1,False I get a script error. error : the system can not find the specified file.
It happen when I run the script with MDT 8450 and locally on a Windows 10 device.
My scripting skills are no so much good, hopefully there is someone who can help me