We are building Vista images that support various models of hardware and sysprep is failing to create the image. A lot of time has gone into troubleshooting, duplicating hard drives prior to sysprep, identifying troublesome drivers etc. The bottom line is that this is KILLING our productivity. We didn't used to have this problem with XP. When we successfully create the image, we then use ghost 7.5 on a server to load 20 machines on an internal net at a time.
My question is-- Is there an alternative to Sysprep to prepare the image? Have other people run into this problem with Vista and found an alternative? I am NOT involved in the nuts and bolts of this issue but our image creators continually wrestle with Sysprep and it just isn't working!!!!!
How are other people doing it?
We aren't cloning per se but building an image that will install on different pieces of hardware, can be named and have drivers installed during the imaging process. At the end, we finish any drivers and join them to a domain where they get a domain sid.
The image build process starts with a Vista box, preconfigured with software and drivers, it is then sys-prepped and then that is made into a Ghost image that is put on a server to be distributed on a closed network to 20-ish computers.
I'm going to get a hold of the procedures and read up on them to better clarify the current process so we can get an alternative. I will ask about ImageX but I don't know if the newSID will be a benefit because we are on a domain.