Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all articles
Browse latest Browse all 9126

I want to run Sysprep at the end of my deploy task sequence so that OOBE runs for the next tech who starts the machine

$
0
0

I am building an 'offline' deployment solution to give to our "OEM" or whatever you call them, the people who prep and deliver our Dell and HP machines. 

One of the things they do is image the machines. I have an SCCM (non MDT) task sequence that lays down our Windows 7 x64 .wim file, does a few minor tweaks, and then SHOULD run sysprep /oobe /shutdown /unattend:unattend.xml.

The idea is that when the machines show up, the tech will unbox them, power them on, and then run through the OOBE. The only thing we want them doing during that OOBE is creating a local account for them to login.

I can see Sysprep run, but it can't find the unattend.xml file, but the step before I run Sysprep, I copy the unattend.xml to C:\Windows\System32\Sysprep.  Also, there is a login type error (sorry I will try and screencap it) that is shown before the machine shuts down, and the smsts.log says something like "Cant take the machine out of provisioning mode."

So, I feel like my method so far is not the right way to go about this. Can anyone help?

This is the step that copies the unattend file:

This is the step that runs Sysprep



Viewing all articles
Browse latest Browse all 9126

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>