techie17 Posted January 19, 2022 Posted January 19, 2022 We currently use Endpoint Config Manager to manage clients and also deploy Win 10 but we will be moving to Intune later in the later. How do i deploy Windows 10 using SCCM so that the computer boots to the OOBE? Ive got a very basic task sequence setup but it ends up booting to the login screen and not the OOBE Thanks
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Anyone got any pointers on this? I have found the option "Deploy Windows Autopilot for existing devices" when creating a new task sequence but i dont can the clients to be co-managed in Intune, i just want a fresh install that after installing the OS via SCCM, the device goes to the OOBE Thanks
ThatBoringBloke Posted January 20, 2022 Posted January 20, 2022 Could just use WDS without an answerfile?
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Could just use WDS without an answerfile? As we already use SCCM, i wanted to use that.
Norphy Posted January 20, 2022 Posted January 20, 2022 You could put SysPrep in as the last step of your task sequence?
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Ahh okay so have a setting right at the bottom of the task sequence to run the sysprep command so do you know what command i need to put in? EDIT: IS it this one? cmd.exe /c C:\windows\system32\sysprep\sysprep.exe /oobe /reboot
Norphy Posted January 20, 2022 Posted January 20, 2022 That would do it. There's also a step called "Prepare Windows for Capture" which does much the same thing.
jslate1980 Posted January 20, 2022 Posted January 20, 2022 Sccm client will stop azure ad join due to co management. What about this https://ccmexec.com/2018/09/how-to-show-oobe-for-azuread-join-after-osd-with-sccm/
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Is this the correct location for the "Prepare Windows for Capture"? The task sequence is failing on that task
jslate1980 Posted January 20, 2022 Posted January 20, 2022 Why you capturing an image, instead of using installation media?
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Why you capturing an image, instead of using installation media? Im not, its just running a normal base installation.
jslate1980 Posted January 20, 2022 Posted January 20, 2022 That's strange at that point of my task sequence we have install sccm client. Not that.
caffrey Posted January 20, 2022 Posted January 20, 2022 Could you not just spam the windows key at the region select ? Or are you wanting it more automated ?
jslate1980 Posted January 20, 2022 Posted January 20, 2022 Actually that looks like Build and capture reference operating image in create new task sequence. Never done an OS build that way. I would start again create task sequence > install an existing image package.
techie17 Posted January 20, 2022 Author Posted January 20, 2022 That's strange at that point of my task sequence we have install sccm client. Not that. I dont want to install the SCCM client, i just want a normal base installation.
jslate1980 Posted January 20, 2022 Posted January 20, 2022 You can't with sccm you have to remove the client through the install process. As explained in the link I added. The cleanup script has this and boots you in oob
mdrabble Posted January 20, 2022 Posted January 20, 2022 Take a look at this - https://ccmexec.com/2018/09/how-to-show-oobe-for-azuread-join-after-osd-with-sccm/
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Take a look at this - https://ccmexec.com/2018/09/how-to-show-oobe-for-azuread-join-after-osd-with-sccm/ The sequence is failing on the copy script command so not sure if the command copy /y “%~dp0prepareOOBe.ps1” “C:\Windows\Temp” is the issue? Ive running that command locally and it wont copy the file however running copy /y "*.*” “C:\Windows\Temp” works locally. not tested in on the task sequence yet though.
jslate1980 Posted January 20, 2022 Posted January 20, 2022 The sequence is failing on the copy script command so not sure if the command copy /y “%~dp0prepareOOBe.ps1” “C:\Windows\Temp” is the issue? Ive running that command locally and it wont copy the file however running copy /y "*.*” “C:\Windows\Temp” works locally. not tested in on the task sequence yet though.Just set this up and testing it myself now. Will get back to you as I did the copy script different using xcopy.
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Just set this up and testing it myself now. Will get back to you as I did the copy script different using xcopy. Awesome, thanks
jslate1980 Posted January 20, 2022 Posted January 20, 2022 It didn't work, but it was my mistake. I forgot to add the xcopy command I created to the package I uploaded. Get back to you later.
jslate1980 Posted January 20, 2022 Posted January 20, 2022 Example of how I did it with xcopy for you to test xcopy %~dp0PrepareOOBE.ps1 C:\Windows\Temp\ /Q /Y
techie17 Posted January 20, 2022 Author Posted January 20, 2022 Example of how I did it with xcopy for you to test xcopy %~dp0PrepareOOBE.ps1 C:\Windows\Temp\ /Q /Y Works much better. The only thing now is that it still doesn't stop at the OOBE screen but then i have't specified an unattend.xml answerfile so is the reason why it then goes straight to the login screen?
jslate1980 Posted January 20, 2022 Posted January 20, 2022 Yes you need answer file or the variable doesn't work.
jslate1980 Posted January 20, 2022 Posted January 20, 2022 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?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now