re: Single WIM Deployment of Windows XP Professional and Tablet PC Edition (and Other Operating Systems)

Michael Murgolo — Tue, 20 Apr 2010 17:22:30 GMT

JoelJGarrett,

I had not tried the /integrate option to update the source files. That may work just fine for that step. I imagine that the simple xcopy will likely be faster. However, I needed the full SP3 media anyway so as to have the Support\Tools folder at the correct SP for the Sysprep files.

As far as the code for copying updated Sysprep files that includes code for x64 architecture, I lifted a lot of that from LTISysprep.wsf. LTISysprep.wsf had this code so I didn't change it. Simple as that.

Michael Murgolo

re: Single WIM Deployment of Windows XP Professional and Tablet PC Edition (and Other Operating Systems)

JoelJGarrett — Tue, 20 Apr 2010 12:43:52 GMT

Mike, I'm a little confused in your section called "Updating the \Windows\Source" - I understand the need to have updated copies of the sysprep/deployment files and to have an updated Source directory, but why not just apply the directory using the /integrate: option to the c:\Windows\Source directory directly as an application instead of having to do all that copying and shuffling around? Is this just for the sake of having a more complete C:\Windows\Source folder available on the machine than would normally be left behind by a regular MDT install?

Also, your code for copying updated Sysprep files includes code for x64 architecture? We're trying to get the SP3 files which are only relevant to the x86 architecture for XP, correct? Or is this .wsf somehow overriding the standard sysprep 'prep' steps in the process?

Thanks for the great series of articles on "single-image" processing of WinXP. I've definitely learned some useful things from reading through them and looking through the code and .ini files.

Regards,

Joel