VThompson

Tripredacus, Thanks for the reply. Sorry for leaving some details out. At the point I'm trying to modify things, I am using, both a Vista currently and Win7 in development, sysprepped image using an unattend.xml file. I'll look into modifying the Windows Setup process and see if what I'm looking to do is possible. Thanks again. You've put me on the right path.

I'm using a script from Mike Vandermeer (http://mikeva206.spaces.live.com/) that allows me to edit the unattend.xml file once the image is dropped to the machine so that the machine name can be customized for each computer and still be put on the domain in one pass. My problem is I want this script to do more. I've written in some WMI and scripting that requires those packages to be loaded in order for the script to work. My problem is that initial boot environment that is instantiated before windeploy.exe is launched lacks those needed packages. Now I know how to add those packages to my boot.wim that WDS uses in order to drop the install wim to the machine, but I can't find how to build those capabilities into the install wim. Either one of two things is happening. 1. the boot.wim used by WDS is copied to the machine during the image drop and is subsequently used after the reboot to start mini-setup or 2. there is some built in version of PE in the Windows build that I can't find. If it's option 1. then that's a fairly straight forward fix by just modifying my boot.wim on the WDS server, but I doubt that is going on. Can someone point me in the right direction here, please? I'd be very grateful. How can I add in the WMI and scripting support to the PE that is used to setup the install image once the machine disconnects from WDS and reboots? Thanks much!