Windows Thread, Why isn't sysprep working? in Technical; Before I begin, sysprep has never really liked working for me...
I have a nice clean install of XP in ...
Before I begin, sysprep has never really liked working for me...
I have a nice clean install of XP in VMWare which I want to sysprep. This all goes fine but then it doesn't seem to pick up the sysprep.inf file (in the folder c:\sysprep) at first boot - instead it asks all the questions.
I have attached the sysprep.inf file and, as you can see, it's not rocket science - all I want is a fresh XP install with automagically generated computer name and joined to the VMWARE workgroup.
Have you tried putting the sysprep.ini file onto a floppy disk and then rebooting - You may want to disable the floppy disk drive as a boot option, or insert the disk when the XP boot screen or OS selection menu appears onscreen or the PC will try and boot up off the floppy.
Does it matter which version you use? M$ brought out a new version of sysprep for SP2. Just a shot in the dark Ric. I cannot see any faults in your sysprep.inf file which would cause any probs.
Could the issue lie with VMWare and using sysprep within the virtual environment? Have you ever been able to sysprep your vmware setup of XP or 2000? I could give this a try if that will help make things clearer.
Tried it in VMware Ric and it was successful, I ran MiniSetup and did not regenerate grace period for activation. The security identifiers were regenerated and the system was set to Shutdown. On restart I only had to insert the CD key as this had been deleted from your sysprep.inf file. Everything was okay I now have a Baines PC in my VMware app.
I always Sysprep in VMware..using SP1 and SP2 sysprep...
no problems for me. I must get a KVM at some point
I always extract the support.cab to the c: drive and go from there, using the sysprep.inf I keep on my USB pen.
That looks somewhat like ours..I'll attach it..
I always fire up a command prompt and use Sysprep -bmsd to build the mass storage section before I use the gui with "Preactivated" and "mini-setup" options.
Theoretically it should just be all in c:\sysprep, and go from there..
Ignore the last bit with the batch files..thats just to autorun our firewall killing script and install the drivers packs on our Precision 360's..*spit*
I was being an idiot and missed the tickbox for 'run mini-setup' on the sysprep dialogue - must flog myselffor being a fool! How many hours did I waste?