Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all articles
Browse latest Browse all 11297

MDT unattend.xml trumps captured image answer file!

$
0
0

Hi! Been using MDT for awhile and have no issues until I wanted to try something new.

I have built my reference image on a VM, did my customizations and sysprepped the machine. I placed my unattend.xml file in

c:\windows\system32\sysprep

My command line (run as admin): sysprep /generalize /oobe /reboot /unattend:unattend.xml

I see sysprep processes the unattend, cleans up plugins, etc..

I reboot into WinPe and capture my image using ImageX... I then have my install.wim file.

I then open up MDT workbench, import my apps, drivers, and import my OS. I select no sysprep files are needed of course.

I then go to advanced, Media and create a media for my iso file... The iso is created. 

BUT!!! I notice that under deployshare\control\TS number\there is an unattend.xml THAT IS WAY DIFFERENT from my original one that I used for sysprep.

I need to know why MDT generates ANOTHER unattend.xml which is then used to trump the one I used when I sysprepped? Is this by design? I know a way around it which I have been doing for years is to open up my ISO, delete the unattend.xml and copy MY unattend.xml to the control\TS number directory...Save my ISO and im good to go. I'm trying to see why my unattend.xml is being trumped. 

HELP!!


Viewing all articles
Browse latest Browse all 11297

Trending Articles



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