How-to: Create a universal windows XP image using mysysprep.exe and VM Ware
-
[quote=“boon, post: 4519, member: 833”]I’ve uploaded the files SSX4LIFE posted here:
[URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVZnhQUjRSaWFoNHM’]sysprep.zip[/URL]
[URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVS2R6bXFad1Rka28’]oemscan.exe[/URL][/quote]
Boon, Thanks for posting the “snap in” version of OEMScan.
-
[quote=“boon, post: 4519, member: 833”]I’ve uploaded the files SSX4LIFE posted here:
[URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVZnhQUjRSaWFoNHM’]sysprep.zip[/URL]
[URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVS2R6bXFad1Rka28’]oemscan.exe[/URL][/quote]Thanks boon for covering me while I was out of the states.
i got back today, and was about to upload them when I find you’ve taken care of it
thanks.
-
[quote=“SMoRZ3, post: 4552, member: 1375”]Boon, Thanks for posting the “snap in” version of OEMScan. :)[/quote]
As a friendly reminder (I made that snapin). That if you run it as a snapin you will want to flag it for a reboot.
If you run the .exe as a stand alone and reboot it will also work (handy for a flash key)
Again… oemscan.exe will ONLY work on XP home / pro / MCE2K5, and will ONLY auto activate if you have an SLP key on oem hardware
Enjoy!
-
[quote=“ssx4life, post: 4754, member: 268”]As a friendly reminder (I made that snapin). That if you run it as a snapin you will want to flag it for a reboot.
If you run the .exe as a stand alone and reboot it will also work (handy for a flash key)
Again… oemscan.exe will ONLY work on XP home / pro / MCE2K5, and will ONLY auto activate if you have an SLP key on oem hardware
Enjoy![/quote]
Yeah, its real nice and keeps it simple, I’ve just been running it manually and restarting manually, haven’t felt like taking the time to automate it or anything yet.
Does anybody know if I use the driverpacks.net software, and tell that to keep the drivers on the hard drive, can I just sysprep and upload the image and when it gets thrown on a new PC/hardware setup it will just go through all the drivers? I’m just curious since its pretty easy to make an XP install disc with most updates and drivers integrated right into the install.
-
Ive never syspreped before, but I noticed when my virtual machine rebooted and went through the sysprep boot it asked for a win xp pro disc. Is this normal? Or did I do something wrong?
I also learned that there is an AVGPrep software that I should have ran before syspreping. It loses all of its activation after syspreping…
-
One last quick question,
I’m using an OEM key given to me from my boss that I’m pretty sure he gets from MSDN subscription.
Will using this key run out if Imaging over and over different systems?
Or will the oemscan.exe help resolve my question? -
[quote=“buckITall, post: 9087, member: 101”]One last quick question,
I’m using an OEM key given to me from my boss that I’m pretty sure he gets from MSDN subscription.
Will using this key run out if Imaging over and over different systems?
Or will the oemscan.exe help resolve my question?[/quote]I’m sure you already resolved this but I wanted to leave a note in case anyone asks.
If you have an MSDN subscription you don’t want an oem image or oem media. You want a VLK key and VLK media.
Keep apples with apples.
OEM Scan assists with entering the required files (.bin / .dat / .cat / .sig files) to pass genuine advantage legally (in the same method that dell /hp / etc. pass it for oem copies of xp)
Thanks.
-
The guide works like a charm, thanks alot for sharing it!
I’ve got a problem regarding the driver deployment:
I’m using the SAD2 tool, as we have a huge amount of different hardware and already got it running nice and smoothly on Win7. After configuring the .inf and running sysprep, the pc just won’t run SAD2 properly after a reboot / imaging. It seems that it basically does its job by starting SAD, but then the SAD is being choked off by an automatic restart.So my question is: How can I prevent / delay the first restart after running sysprep? Turning the AutoLogon off or setting its value to “0” doesnt seem to do the job.
-
I forget which file to edit would be, but you just need to add the line:
net stop “FOG Service”
Before the SAD2 tools start running.
Then after it’s complete, put in the same script:
shutdown -r -t 10
So that the system will reboot automatically after the install of the drivers are complete. This will prevent the FOG Service from restarting the system automatically.
-
[quote=“Tom Elliott, post: 14267, member: 7271”]I forget which file to edit would be, but you just need to add the line:
net stop “FOG Service”
Before the SAD2 tools start running.
Then after it’s complete, put in the same script:
shutdown -r -t 10
So that the system will reboot automatically after the install of the drivers are complete. This will prevent the FOG Service from restarting the system automatically.[/quote]
Ah, I skipped that part. Works fine now, thanks!
