Back to ConfigMgr main menu
Back to MDT Menu
In my experience it is best practice to capture your reference images using MDT build and capture task sequence. However, every now and then, you can be in a situation where a customer has provided a pre-built image (often using another deployment solution) and you have to capture this to a WIM file.
For this, you use a Sysprep & Capture task sequence. It's also an easy solution to implement.
Right click Task Sequences and choose to create one.
Enter a suitable ID and name.
Choose "Sysprep & Capture".
Choose the OS to match what you will be capturing.
No need to specify the product key.
Enter your details (you must enter details in each box to be able to continue).
No need to specify administrator password.
Review the summary and click Next.
Process has completed.
See the Scripts folder in the Deployment share. LiteTouch.wsf is available.
Now lets capture the thick image. Open a command prompt "As Administrator" on the reference computer. First, map a drive to the deployment share, so that we can enter credentials.
Then execute the following command:
cscript.exe \\UNC path\DeploymentShare$\Scripts\LiteTouch.wsf
We are presented with a menu of available task sequences. Choose "Systprep & Capture".
Enter local administrator password.
Choose to capture an image of the computer. Enter a location and file name.
Specify your network credentials.
Review the summary and click Begin.
The task sequence starts. Sysprep is executed. The computer then restarts and boots into Windows PE.
The image is being captured.
The task sequence has completed. You can now restart the computer - we do not need it any more.
Image file (.WIM) is now available to be imported into ConfigMgr.
Gerry, I get an error when I tried to run the LiteTouch.wsf file from the reference machine.ReplyDelete
1. Reference machine is not joined to the domain yet
2. I access the server from Run - \\Servername and access the C$ deployment share and selected the LiteTouch.wsf and I Get an error Unable to map a drive to the deployment share. Already connected to server as that is where this script is running from. Unable to connect to share, The network path was not found.
Do I need to join the computer to the domain?
No, you shouldn't join the computer to the domain. You need to use the FQDN of the serverDelete
Thanks Gerry, I was able to successfully capture the image using mdt. Many thanks for your help.ReplyDelete
That's good. Glad to help.Delete
Gerry, Can you please review the customsettings.ini file?ReplyDelete
We need to send a copy of the base image to the manufacturer and I'm trying to automate the deployment as much as I can. Since its an offline deployment, I want to keep the customsettings.ini as simple as possible.
TimeZoneName=A.U.S. Eastern Standard Time
SkipAdminPassword=NO (for some reason it asks me to enter the admin password every time, how do I automate it)??
SkipLocaleSelection=YES (What is this?)
SkipLocaleSelection=YES (What is LocaleSelection)?
KeyboardLocale=Not sure what to enter
Pls let me know if there are any changes required.
Is there a method to inject Drivers into the thick image? We want to build a base image that we can build off of that has the basics of every users installed as well as as many updates installed as possible.
I know how to generalize everything else (SEP, SCCM client, Office etc) but I want to be able to inject a driver store into - I know how to do it roughly externally using DISM, but is there a method to do it through MDT?
You really shouldn't add drivers to the image. Add the drivers while computers are being built using the Add Driver Package task sequence step.Delete
Gerry I love your articles.... Thank you!ReplyDelete
When I try to capture a custom image, System Drive shows up and in few seconds computer restart and image get captured with system drive as separate drive in computer.
How do I prevent this to happening?
You're welcome Farooq. I'm sorry though. I don't fully understand your question.Delete
MDTK 2013 is incredibly difficult and buggy.ReplyDelete
Ver 8443 will not show the Sysprep & Capture task steps and now ver 8330 is doing the same thing.
Frustrating and typical microsoft crap product.
Better to find something more reliable....