How-to: Create a universal windows XP image using mysysprep.exe and VM Ware



  • I decided to throw together a really quick video walk through of how to create a universal windows xp image using fog.

    In this demo walk through I’m using Windows XP Professional OEM + SP3 slipstreamed. I HIGHLY… [B]HIGHLY[/B] suggest that you use a vanilla OEM disk and NOT a stamped disk such as a dell / hp oem disk. These oem disks come with the hologram typically.

    It’s also important to note that you can actually sysprep an OEM vanilla image. I’m using an OEM SLP key found here - [url]http://technet.microsoft.com/en-us/library/bb457078.aspx[/url] , and runing oemscan.exe after the machine is imaged to fully activate it on oem hardware.

    To simplify things I’ve also included a copy of my sysprep folder (see below). This folder is ~50MB due to it including 2 driverpacks (mass storage / lan) for NT5 x86. It already has a pre-built sysprep.inf file you can edit and use for your own =)

    1. Create a Virtual Machine using Virtual Box or VM Ware.
    2. Make sure that the VM you create has an [B]IDE hard drive[/B] option selected (not SCSI) and a SINGLE PROCESSOR with [B]TWO CORES[/B]. Also make sure the lan is BRIDGED
    3. Install Windows XP Pro (OEM if you don’t have a VLK), or VLK if you have that license agreement and key
    4. Run all updates on the computer, install any software, configure the OS the way you want / etc.
    5. Capture a snapshot of the OS using the software (VM Ware has this built in, as does virtualbox)
    6. Simply download sysprep.zip and unzip the file and move it to C:\sysprep (if you are using windows xp pro vlk you will need to modify the supplied key)
    7. Run spdrvscn.exe and hit box #1, #2, #5 (save) and close the application
    8. Run sysprep.exe from a command prompt as follows “sysprep.exe -bmsd” This will run sysprep and pull all the mass storage drivers and lan drivers down into the sysprep.inf file
    9. Make any last changes you want to your image (if you are using a VM I suggest that you snapshot as you go along)
    10. Install the Fog client service
    11. Manually register the host by MAC address on the fog server. You can find this by running ipconfig /all
    12. Once registered assign it to a new computer image in fog, and select “upload”
    13. On the virtual machine run setupmgr.exe and modify the sysprep.inf to your liking (change the password / name / etc.)
    14. Once saved run mysysprep.exe and tick the box that says “run mini setup” as and then “reseal”
    15. Wait about 15-20 min’s for sysprep to run and shut down the VM
    16. Turn the VM on and smash F12 on your keyboard to PXE boot the OS.
    17. FOG will now boot and capture the image. =) You are set! This image will now work on any model hardware you throw it at (well just about)

    The above steps are pretty cut and dry. If you have ever run sysprep.exe before on Windows XP most of this should be fairly familar to you. All that was added in this guide was we have added drivers using the sysprep driver scanner, and chanloaded mysysprep.exe instead of the standard sysprep.exe (giving us the ability to inject HAL’s into the install).

    [SIZE=4][U][B]Required Files[/B][/U][/SIZE]

    1. sysprep.zip - [URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVZnhQUjRSaWFoNHM’][B]https://docs.google.com/open?id=0B6xOimbg2JqVZnhQUjRSaWFoNHM[/B][/URL]
    2. oemscan.exe (only needed on oem builds of Pro. Run the .exe as a snapin or manually + reboot. It will then be activated if run on a supported oem system (dell hp / compaq / etc.) with a supported OEM SLP key - [URL=‘https://docs.google.com/open?id=0B6xOimbg2JqVS2R6bXFad1Rka28’][B]https://docs.google.com/open?id=0B6xOimbg2JqVS2R6bXFad1Rka28[/B][/URL]

    If you have any questions let me know.

    EDIT

    Thank you Boon for re-hosting / uploading these files while I was out of the states on work.

    thanks.



  • [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!


  • Senior Developer

    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.



  • 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.



  • [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.



  • 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?



  • 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…



  • [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.



  • [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=“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=“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. :)



  • Thanks Boon, never heard of this, but I think it might be my new best friend! :)



  • [URL=‘http://www.autopatcher.com/forums/topic/3108-the-autopatcher-download/’]AutoPatcher[/URL] does the trick.



  • How are you fully updating the machine (Windows/Microsoft Updates) if the machine isn’t activated? I just used that SLP key, and my virtual machine can’t update using it… Thanks



  • 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=“ssx4life, post: 2754, member: 268”]
    [SIZE=4][U][B]Required Files[/B][/U][/SIZE]

    1. sysprep.zip - [url]http://asapload.com/info?id=132110[/url]
    2. oemscan.exe (only needed on oem builds of Pro. Run the .exe as a snapin or manually + reboot. It will then be activated if run on a supported oem system (dell hp / compaq / etc.) with a supported OEM SLP key - [url]http://asapload.com/info?id=132109[/url]
      [/quote]

    Hi This links don’t open, can upload files again please?

    Regards



  • [quote=“SMoRZ3, post: 4430, member: 1375”]Does anybody know where you can get an XP Pro OEM disc? I have a Dell version, but it doesn’t take the Perserving OEM Actication key thats provided by Microsoft.

    Basically the version I have cant be activated, so then i cant do updates which makes using the VM useless as far as saving time…

    Thanks[/quote]

    Legally we can’t distribute these due to copyright law.

    Please post your MGADIAG.exe logs so we can better help you =)

    [url]http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&sqi=2&ved=0CFIQFjAA&url=http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D52012&ei=qYzsT_L_O9L1qAH_lLzOBQ&usg=AFQjCNH5Zcs6VID448dqfDkoyf9nzmkx7w&sig2=RpxaEKLIe4K0Q8fzL-_D2Q[/url]



  • [quote=“buckITall, post: 4074, member: 101”]Thanks for your time ssx…have you been able to upload the “sysprep.zip” files yet, I can’t seem to find the posted link.[/quote]

    @sid @buck @scsi

    I have been out of the states on work for the last 3 weeks. I won’t be back till the 2nd week in July.

    I tried to wake on lan my pc at home, but the packet isn’t getting to my server for some reason, and I can’t remotely turn it on any other way.

    Once back I’ll re-host these files.

    Thanks for being patient, I’ll get back to you shortly on this.



  • Does anybody know where you can get an XP Pro OEM disc? I have a Dell version, but it doesn’t take the Perserving OEM Actication key thats provided by Microsoft.

    Basically the version I have cant be activated, so then i cant do updates which makes using the VM useless as far as saving time…

    Thanks



  • Thanks for your time ssx…have you been able to upload the “sysprep.zip” files yet, I can’t seem to find the posted link.


Log in to reply
 

358
Online

38982
Users

10712
Topics

101678
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.