I’m curious if there’s a way to have the postdownload scripts only run for certain images and not all of them.

@george1421 I was only utilizing one unattend.xml file. I went to my root and did a scan for my whole drive and the only unattend was in C:\Windows\Panther. And yes, after logging into windows I saw that the unattend.xml was in fact changed to what I had the postinstall script do, but my computer name was not what was in that file.

Should I inject a new one to that location, or modify the old one? Because if it’s just modify the old one, that’s where my problems mainly were. I originally followed your posts to do this.

My original steps were:
Created the unattend.xml in C:\Windows\Panther
Ran sysprep with /unattend pointed to the one I created
Would capture image after shutdown with sysprep
When deploying image I would use the postdownload script to modify the ComputerName
Upon login, none of the unattend file changes were there

Hello! I’m currently facing an puzzling issue… I have attempted to build a base image then run the sysprep /generalize /oobe /shutdown (and sysprep /generalize /oobe /unattend:C\Users\admin\Documents\unattend.xml /shutdown) and my system seems to not run the unattend files after reboot. During the sysprep preparations it passes all of the unattend file and makes changes before reboot. After the shutdown I’ll capture the image and during deployments it seems as if the unattend file is ignored. (It skips the setup but doesn’t implement the changes that I put in with sed)

An example is during the specialize pass I have the <ComputerName> tag set to TECH and the postdownload script does change it to what I want it to, but for some reason windows is naming the computers WIN-(random characters)