Deploy Win 10 with OOBE

[techie17]

Update: xcopy works through deployment but not booting oobe, I missed the restart between installing sccm client and removing it. So think that might have caused it. Otherwise its my answerfile. Though can't this just be ran as a powershell script after os install instead of waiting for the post install variable to run the script?

 

Ive set the answerfile and its still not booting to OOBE, just goes through to the login screen so maybe my answerfile needs different settings

[jslate1980]

Same here. powershell script not running. Must be answer file. Instead of running PowerShell script from variable. Testing to deploy after os install.

[MYK-IT]

Not sure if these resources will help??? Currently testing myself using MDT to deploy a WIMWITCH created image (e.g. stripped out apps, applied latest updates etc) with automatic Intune enrolment (devices). Although I have it working, I am just trying to resolve some the deployment errors when I attempt to inject the device-specific drivers via MDT (as opposed to having them part of the WIM). It works fine for a normal, domain-joined MDT Lite Touch deployment, so must have missed something out of the TS!

 

https://osddeployment.dk/2018/12/08/how-to-deploy-autopilot-device-fast-with-mdt/

https://msendpointmgr.com/2020/03/04/deploying-autopilot-with-mdt-on-usb-a-wim-witch-use-case/

[MicrodigitUK]

We do exactly this in one of our task sequence. The trick is uninstalling the SCCM client at the very last minute and then sys prepping for OOBE. If I get a chance in the morning I’ll take some screenshots of the steps taken to achieve this in task sequence. The good news is it works really well just gotta get the order correct to ensure it removes the SCCM client.

[jslate1980]

Update: xcopy works through deployment but not booting oobe, I missed the restart between installing sccm client and removing it. So think that might have caused it. Otherwise its my answerfile. Though can't this just be ran as a powershell script after os install instead of waiting for the post install variable to run the script?

 

To answer my own question, you cannot remove sccm client through task sequence. It can only be removed after the sequence has finished. That is why it is called with the SMSTSPostAction variable.

[techie17]

To answer my own question, you cannot remove sccm client through task sequence. It can only be removed after the sequence has finished. That is why it is called with the SMSTSPostAction variable.

 

Got ya. So im my case it doesn't run the SMSTSPostAction however if i log on to the device and run it manually, it does run. The task sequence step looks correct

[jslate1980]

Got ya. So im my case it doesn't run the SMSTSPostAction however if i log on to the device and run it manually, it does run. The task sequence step looks correct

So I have it booting to OOBE, though the task sequence is set differently. As @MicrodigitUK said the task needs to be set as the last item in the list.

Here is my copy script

Here is the SMSTSPostAction Variable

Only issue is I can't get command prompt in OOBE, but that may be down to me using a vm.

Edited January 21, 2022 by jslate1980

[techie17]

So I have it booting to OOBE, though the task sequence is set differently. As @MicrodigitUK said the task needs to be set as the last item in the list.

Here is my copy script

[ATTACH=CONFIG]64307[/ATTACH]

Here is the SMSTSPostAction Variable

[ATTACH=CONFIG]64308[/ATTACH]

Only issue is I can't get command prompt in OOBE, but that may be down to me using a vm.

 

Mines like for like with yours and still doesn't go to OOBE. Doing my head in now! Are you able to share your unattend.xml file? At least i can rule that out.

[jslate1980]

Mines like for like with yours and still doesn't go to OOBE. Doing my head in now! Are you able to share your unattend.xml file? At least i can rule that out.

Here you go.

 

   
	
		
			true
			3				
			true
			true
			true
		
		
		
		
       
   

[techie17]

Helps if i spell Execution properly!!!! i will try again!

[slugshead]

Use a task sequence as follows

 

* Restart in PE

* Partition Disks

* Apply operating system - Just feed this a fresh ISO from the volume portal, golden image days are over.

* Install drivers

* dism generalize/oobe

[techie17]

Mines like for like with yours and still doesn't go to OOBE. Doing my head in now! Are you able to share your unattend.xml file? At least i can rule that out.

Nope still not running the powershell script and i have double checked the command line. Its copying the file just not running it. I have exactly the same answer file as you also so the only thing left for me to try is a different image

[techie17]

Nope still not running the powershell script and i have double checked the command line. Its copying the file just not running it. I have exactly the same answer file as you also so the only thing left for me to try is a different image

Different image makes no difference either.

[jslate1980]

The only thing I can add is the script didn't run until the pc had brought up the login screen.

[techie17]

The only thing I can add is the script didn't run until the pc had brought up the login screen.

 

Ahh so on your test VM it didnt run the powershell script until it went to the login screen?

[jslate1980]

Ahh so on your test VM it didnt run the powershell script until it went to the login screen?

Correct then restarted into OOBE. I would leave it 5 minutes.

[techie17]

Correct then restarted into OOBE. I would leave it 5 minutes.

 

Still doesn't work. Not sure what else to check from this point as everything else seems correct.

[MS1]

Did you ever manage to get command prompt working? I am having the same issue, OOBE is working via task sequence but command prompt seems to be disabled.