New to ConfigMgr imaging. Sysprep? Unattend file? Audit Mode?

[torbuck]

Greetings

 

Our organization is fairly new with SCCM and its imaging process. We come from an Altiris background, so a lot of the imaging process we are relearning.

Our SCCM installation consultant left us with a imaging process where it basically takes the wim file right from the Windows install source, and then proceeds

with a number of task sequences, molds the deployment to our preferred standard.

 

We are interested in deploying our images in a different manner, where we install our Windows of choice in a Hyper-V VM, do whatever tweaks and updates

that we want, and then use this as the basis of our image. I've seen a number of procedures that outline this method, however my question is, if we do this process,

for that VM do we still follow the standard imaging process by putting that Windows VM into audit mode, as well as creating an unattend file using the Windows

System Image Manager? If there is specific tweaks that we want for all windows profiles, how is this done through the capture media process?

 

Also, we would like to use the VM to use as a reference image, so that we can periodically apply Windows updates, or make any necessary adjustments, and

then use this VM to replace the deployed image on a ongoing basis. Let me know if this is possible, and if so, any direction on how this is done would be welcomed.

 

Thank you

[anyweb]

no need for that, simply build your image on hyperv using either MDT 2013 or System Center 2012 Configuration Manager, and capture the image using the same task sequence, this is known as 'build and capture' and it's a 100% automated process.

 

you can see that described here, simply modify it to capture whatever Operating System you want, and then deploy it using configMgr

 

• CM12 in a lab - Part 7. Build and Capture Windows 7 X64
• CM12 in a lab - Part 8. Deploying Windows 7 X64

[torbuck]

 

 

I will have a look at those steps. Appreciate the feedback!