Jump to content
EduGeek EdSec 2026 is Go! 27th Oct in Derby! Join us for a day of EdTech security focused talks, networking, and an evening social ×

Recommended Posts

Posted

Something I've never really understood, when I create my image the last thing I do us run sysprep.exe /generalize /oobe /shutdown /unattend:x64unattend.xml

 

The x64unattend.xml is my own XML file that I include on the image. However, in MDT in the /DeploymentShare/Control/001 folder theres another unattend.xml file in there.

 

Which one is actually being used then?

 

Or are both being used?

 

Thanks!

Posted
Its for the deployment of the os. So sysprep doesn't have one afaik. As the unattend.xml is applied to the image in depoyment. So your image is more flexible.
Posted (edited)

The unattend.xml is applied to the image when applied to a computer. You should use mdt to do the build and capture.

There is also the sysprep and capture ts. You can edit the unattend.xml for sysprep with that ts. The ts must be started from within windows.

Edited by free780
Posted

The unattended option on the *server* (for x86, x64 etc)

This is used by the Windows PE phase to automate the image selection, login, format the drive etc

You can only have one of these specified in the gui, but if you prestage a machine you can have it use a different one (handy to make different machines automatically install different images each time).

 

The unattended option on the *image* is coped to the machine during the above deployment phase, and is used when the machine reboots, in the normal manner for an unattended sysprep file.

It just means you can change the image unattended file without having to recapture etc, you sysprep the base image without one.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...