Deployment Artist
   Minimize

 

The deployvista.com site is finally put to rest...

You find new content on the Deployment Research site, a site filled with articles and video-tutorials on how to deploy operating systems. If you are missing something on the new site, please let me know. You can find me on twitter on my @jarwidmark alias.

You can also search the old deployvista.com article archive below.

Regards / Johan Arwidmark


 Print   
 Blog_List Minimize

 Print   
 Blog_Archive Minimize

 Print   
 New_Blog Minimize
You must be logged in and have permission to create or edit a blog.

 Print   
 MMS 2010 - Sample Sysprep Files for Windows XP SP3, April 2010 Minimize
Location: BlogsJohan Arwidmark    
Posted by: johan 4/23/2010

 

Ever struggled with a 0x0000007B BSOD when deploying a Windows XP SP3 image?

Struggle no more, here is a working driver set and sysprep mass storage section for most current hardware models...

Instructions for adding the sample files to MDT 2010 Lite Touch

In these steps I assume you have a deployment share in the D:\MDTProduction folder, Windows XP Pro SP3 (full source) imported to the D:\MDTProduction\Operating Systems\Windows XP Pro SP3 Eng x86 Unattend folder, and that you created a Task Sequence named Windows XP Pro SP3 Eng x86 Unattend Task Sequence.

Step 1 - Download sample files

  1. Download and extract the sample files to D:\Setup\Sample Files (http://www.deployvista.com/Repository/tabid/71/EntryId/62/DMXModule/396/Download/attachment/language/en-US/Default.aspx)

Step 2 - Disable the builtin add mass storage action

  1. Right-click the Windows XP Pro SP3 Eng x86 Unattend Task Sequence and select Properties
     
  2. In the Task Sequence tab, configure the Windows XP Pro SP3 Eng x86 Unattend Task Sequence with the following setting, 
     
  3. Disable the Capture Image -> Add mass storage drivers to sysprep.inf for XP and 2003 action.
     
  4. Click OK.

Step 3 - Configure sysprep.inf

  1. Right-click the Windows XP Pro SP3 Eng x86 Unattend Task Sequence and select Properties.
     .
  2. In the OS Info tab, click Edit sysprep.inf.
     
  3. Edit the mass storage section using the D:\Setup\Samples Files\Sysprep\storage.txt sample

Step 4 - Add the drivers

  1. Using Explorer, copy the D:\Setup\Sample Files\$OEM$ folder to the D:\MDTProduction\Operating Systems\Windows XP Pro SP3 Eng x86 Unattend folder

Step 5 - Build and Capture

  1. Run the Windows XP Pro SP3 Eng x86 Unattend Task Sequence on a virtual machine.

 

Permalink |  Trackback

Comments (6)  
Re: MMS 2010 - Sample Sysprep Files for Windows XP SP3, April 2010    By Dan Van Drunen on 4/28/2010
Johan,
The instructions look good however I am getting many errors when extracting the .zip file. I have tried WinRar, 7-Zip, and IZarc and all 3 apps are reporting errors.
Could the .zip be corrupt?

Re: MMS 2010 - Sample Sysprep Files for Windows XP SP3, April 2010    By Dan Van Drunen on 4/28/2010
Disregard. I downloaded again and it worked. Must have been a bad download.

Re: MMS 2010 - Sample Sysprep Files for Windows XP SP3, April 2010    By traviskirk on 5/11/2010
Johan,
Thank you so so so so much for this updated set of instructions! I was pulling my hair out on this one. I have been struggling for months at getting around the 7B BSOD (ever since upgrading my physical machine and my VMWare version to VM7). I have a HP XW Series Workstation and I have been trying to create MDT images in my VMWare 7 environment. Previously I had been trying what you suggested on 10/28/2008 for MDT 2008; however, it did not seem to be working for me. Two key bits of information came when you included Step 4 in your instructions. First, being work from XP Source files rather than a captured WIM image! And secondly adding $OEM$ to the XP Source files. I don't know which one of those was the true key, but it worked! I still had to connect the vmscsi.flp at the "Press F6" screen when building my first "Golden Image" VM. But after capturing the fully patched WIM back into MDT, I could finally deploy at liberty!!! I am so freaking happy to have my test environment back! Thank you so so so much.
T

Re: MMS 2010 - Sample Sysprep Files for Windows XP SP3, April 2010    By carlzone on 6/5/2010
Thanks for sharing this Johan!
I have tried it out and it works like a charm for our Dell Latitude D620's with SATA drivers. But for our IBM T42's and Fujitsu Siemens S7010's with IDE we get the 0x0000007B BSOD when deploying.
In our environment I have choosed to create two TS's, one to run the unattended installation of WinXP and some base apps. And the second one to sysprep and capture the reference image. (This cause I have to make some serious configurations for one of the base apps to make it work)
According to Step 2 and 3 - In which of the two TS's should I disable the "Add mass storage drivers to sysprep.inf for XP and 2003 action" and update the sysprep.inf ? I make it in the Sysprep and Capture TS.
In your "Sample Files" the \$OEM$\$1\Drivers\Ref_IntelInf\txtsetup.oem" is missing - could this have anything to do with the problem for T42 and S7010?


Re: MMS 2010 - Sample Sysprep Files for Windows XP SP3, April 2010    By Techguy on 9/29/2011
Johan,

First, I want to thank you for sharing so much extremely valuable information in your deployment site, it has been a life saver for a project I'm working on.
Next, I badly need your help with Windows XP and mass storage drivers in MDT 2010. I have tried all your instructions and still can't seem to get MDT to load the drivers. My scenario is slightly different from some of the instruction you have provided, so perhaps this is why I'm at a stuck point. Additionally, I need to complete my deployment solution be Oct 14, 2011. Could you please contact me so I can discuss my setup and a possible solution. I would be most grateful for you help.

Re: MMS 2010 - Sample Sysprep Files for Windows XP SP3, April 2010    By johan on 10/1/2011
Sure, just post the additional info here and I will review it...

/ Johan


  
 Search_Blog Minimize

 Print   
Copyright Deployvista.com 2006-2012 (c)   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2017 by DotNetNuke Corporation