I posted this to an MS newsgroup also. Here is a copy/paste of the reply I got. ----------------------- 1) the task squence properties 'os info' tab has the edit sysprep.inf button, there is also already a sysprep.inf file within the wim file I captured via mdt, so which is used? both (merge)? Correct. If no sysprep.inf is in the wim than the entire sysprep.inf from distribution\Task Sequence directory is copied to machine. If they are in both places a merge happens. 2.)so the unattend.txt and sysprep.inf from the task squence properties 'os info' tab is simply not used? False The script that makes the merge happens is "ZTIConfigure.wsf." It reads ZTIConfigure.xml and based on all the properties as defined there a merge occurs. Values which are present in the sysprep.inf from the distribution directory win. If you open the xml file look for "mapping id" to the the values checked. In this way you can manage the sysprep.inf from 1 central location. Ultimately, you could mount the captured wim with imagex and remove the sysprep.inf from the image but this should not generally be necessary. XP needs sysprep.inf tp be present so that MassStorage drivers will be included when that image is captured. Dave Guenthner [MSFT] ------------------------------- |