It appears that the RASOR utility does some of what I need, but before creating a new topic, I thought I'd air what i'm trying to accomplish, and get some feedback on how to best accomplish it, then decide whether a new topic is needed or not. I am responsible for developing a process to automate the creation of PC images in a heterogeneous corporate environment (no less than 50 different hardware configurations in our environment, including different brands of laptops, desktops, and workstations). Mass storage drivers (MSD's) are a major problem, both during the image building process and afterwards. They are a problem during the image build process because w/o the correct MSD, the HDD is not accessible, thus preventing the build process from continuing. They are also a problem after the images are built as well, because if the MSD issue were resolved, we'd probably be able to reduce the number of base images that we need to make and maintain. And since we are a global company whose sites don't follow standards to the letter anyway (not to mention acquisitions, divestitures, etc), we have a LOT of hardware variability at our sites, so whatever solution I end up engineering needs to deal with those "unknowables" as completely as possible. Currently, we have a separate image for every standard PC type in our environment (built according to a specific inhouse procedure). I don't think that's necessary. but since I am fairly new to the image building process, I could use some ideas on how to proceed. especially since I also need to provide guidance to our site admins so they can perform this new process independantly with minimal guidance. Needless to say, this is a daunting task for a newbie, especially when i've also been given no budget to outsource this, and the ownness is all mine. But, based on the invaluable info here at MSDN, I also think it's doable. From what i've read, I think I should be able to get XP to load on any PC type, as long as the correct MSD's exist on the distro point and are referenced in the unattend.txt. I also think I can reduce the number of images in production by adding the -factory option to sysprep, enabling me to create a generic image which will work on all desktops and laptops, and correctly detect the boot device hardware (SATA, SCSI, IDE, etc). From there, I can simply .bat out the remaining configurations for application and specific configs, i'm not too worried about that. But I do want to make sure that I get the baseline config right, and develop it in a way that makes it as generic as possible, so it will work on widest variety of PCs possible. I realize I am leaving out a lot of details here, but I am doing that intentionally so I don't skew the discussion of a solution. I'd also like to do all of this using Microsoft's Business Desktop Development Accelerator as the vehicle, if possible. For those of you who haven't seen the most recent version, it's definitely worth a look, as it mirrors alot of the work being done here at MSFN ..... and it is also FREE. (http://www.microsoft.com/technet/desktopdeployment/bddoverview.mspx) Thanks in advance for reading, sorry for the length .......