Everything went perfect with my XP deployments until I attempted to deploy to 2 new computers with SATA hard disks. The task sequence will not resume after the driver install the computer just keeps rebooting (both laptop, and desktop). I did some research it with XP it requires a mass storage driver initially. How do I determine what mass storage driver my hardware requires if it does not have a OS? I went to the manufacturer website but all I see is a chipset driver, how do I determine which mass storage after importing drivers is the correct one? Do I also need to apply this mass storage driver to my x86, and x64 boot images? Sorry for all the questions -Logan

The hardware I am trying to deploy is a Lenovo ThinkCentre M70e, and Dell Latitude e5400

I am not sure if there's any way to find out the kind of drive your will need if there is no OS on the computer. I usually did a quick trial and error to determine which driver works for a specific model. I know it can be a bit time consuming if there are several options listed. Hopefully someone who has worked with this specific model will reply. You do not need mass storage driver on boot image.Mayur

I installed a OS and found the correct master boot record but when I bootup in winpe, download the OS, install the drivers, right after when the computer reboots it just constantly reboots over and over again. I am confused at why it is doing this. My Lenovo desktop does not even give a blue screen. Any ideas?

A couple of thing s to try.. 1. Add OSDDiskpartBiosCompatibilityMode = TRUE before partitioning. http://blog.coretech.dk/osdeploy/config-mgr/capture-from-vpc-keeps-rebooting-when-deployed/ 2. Add script to change HAL before "Setup windows and Config.mgr". http://blog.coretech.dk/osdeploy/handling-hal-switching-during-xp-deployment-no-bsod-0x07-error/ 3. To rule out or in storage problems, switch the HD to IDE/compatibility mode in the bios, AHCI will not add performance to XP anyway. If it turns out that storage is the problem and you want to add storage drivers during the Task Sequence, remember that you will have to add the correct driver trough A driver package TS step and that you will need to point to the exact driver within the driver.. Michaelhttp://kongkuba1.spaces.live.com

In addtions to Michael's comments... Here is a good article on XP storage drivers with SCCM http://myitforum.com/cs2/blogs/rzander/archive/2009/08/07/apply-xp-massstorage-drivers-from-sccm-osd-task-sequence.aspx As for finding out info about devices, you can run old school devcon.exe in WinPE to find out info about the hardware, or the Microsoft.BDD.PnpEnum.exe from MDT 2010 Lite Touch which also runs fine in WinPE / Johan

Thank you Michael for your comments. I implimented step 1, and step 2 into my task sequence based on the articles. Step 1 works fine but step 2 fails. I ran step 2 manually from the F8 and a flash drive but it does not show a success after the hal.wsf command. I also changed the bios to compatibility mode. I still am getting a constant reboot when the computer pops up the windows splash screen. Here are some screenshots: 1. Hal task sequence http://lh4.ggpht.com/_MT5cV9Rhpwk/TOU4oiQE31I/AAAAAAAAAoQ/6fGlmSPUppk/s512/tasksequence.gif.jpg 2. HAL Folder http://lh6.ggpht.com/_MT5cV9Rhpwk/TOU4o5YdmAI/AAAAAAAAAoU/nbZTmIXWBV4/s512/hal_folder.gif.jpg 3. HAL Program file http://lh5.ggpht.com/_MT5cV9Rhpwk/TOU4o5P4JbI/AAAAAAAAAoY/iv1YDGM1fmA/hal_package.gif.jpg

In addition, if you press F8 when the machine restarts, you can select to not restart on failure, and then you will actually see the exact BSOD screen. If you get STOP 0x0000007B it is related to storage drivers, if it's something else, most likely related to HAL, WinPE uberbug or IntelPPM.sys on AMD machines... / Johan

Ok I am getting 0x0000007B error. I looked up what I think is the correct storage driver for the Lenovo ThinkCentre m70e, I used a tool called "Everest" when there was an actual OS installed out of box. The driver is INTEL 82801GB ICH7 so I went to Lenovo and downloaded the chipset. I imported the drivers into sccm and created a mass storage package. View picture: http://lh5.ggpht.com/_MT5cV9Rhpwk/TOVBgsFhLoI/AAAAAAAAAoc/sG6IZbZkZJI/s512/mass_storage1.gif.jpg

Ok so this is odd. I reininstalled the hard drive with the windows xp sp3 CD. The BIOS is set to enhanced under SATA and I no longer get 0x0000007b error. The only difference is that through SCCM I am deploying a pre-captured Windows XP SP2 image. Is there that big of a difference between SP2 and SP3? Could my pre-captured image included some old drivers? Should I create a new capture image with SP3? Do I need to include anything with my Boot image other then nic drivers?

Ok so this is odd. I reininstalled the hard drive with the windows xp sp3 CD. The BIOS is set to enhanced under SATA and I no longer get 0x0000007b error. The only difference is that through SCCM I am deploying a pre-captured Windows XP SP2 image. Is there that big of a difference between SP2 and SP3? Could my pre-captured image included some old drivers? Should I create a new capture image with SP3? Do I need to include anything with my Boot image other then nic drivers? Let me understand that correctly. You installed XP using CD and it installed correctly with no blue screen. Then you tried installing XP using SMS and you got the blue screen, right? This is most probably not because of the SP difference. Your CD may have the correct storage driver, but you will have to specify this driver in yout task sequence while deploying XP with SMS. I suspect you either have a wrong storage driver, or a wrong item selected from the drop down menu in the task sequence. 7B is a storage driver error, but you should still confirm it by following item 3 in Michael's post. The next thing to try would be to select a different items at a time in task sequence and try again. How did you create your image?Mayur

Ok here is what I have done. 1. Copied my windows xp with sp3 onto sccm, setup the package. 2. Ran a capture task sequence to capture the OS with sysprep. 3. Attached the new captured image to the deploy task sequence the only thing that has changed is the OS version (sp3). 4. Deployed task sequence with the bios settings the same and it deployed perfectly! I agree that possibily the CD has the SATA driver so when I captured the OS it included that driver. Now Hopefully the rest of my operating systems with SATA run smooth. Lenovo is a pain in the butt.

your problem was definitely HAL related.. the creation of a new image updated the build to contain a valid HAL for that particular machine, but you could still experience problems on other machines.. The HAL change script I mentioned earlier, will take care of this on all models regardless of how they are build... Just remember that you must have the MDT ZTIutillity.vbs script present in the same folder as the HAL.wsf for it to work... Michaelhttp://kongkuba1.spaces.live.com

Michael thank you for providing the script but I am receiving a error 0x000000032 "Task sequence error" when it comes to that step in the task sequence. View the below screenshots for a better understanding of how I setup the script. 1. Hal task sequence http://lh4.ggpht.com/_MT5cV9Rhpwk/TOU4oiQE31I/AAAAAAAAAoQ/6fGlmSPUppk/s512/tasksequence.gif.jpg 2. HAL Folder http://lh6.ggpht.com/_MT5cV9Rhpwk/TOU4o5YdmAI/AAAAAAAAAoU/nbZTmIXWBV4/s512/hal_folder.gif.jpg 3. HAL Program file http://lh5.ggpht.com/_MT5cV9Rhpwk/TOU4o5P4JbI/AAAAAAAAAoY/iv1YDGM1fmA/hal_package.gif.jpg

I would run it as a command line step, pointing to the package containing the script files (or better yet use MDT toolkitpackage). and always have cscript.exe infront of at script to be executed... cscript.exe HAL.wsf this should give you an idea http://blog.coretech.dk/osdeploy/capture-none-syspreped-image-using-sccm-running-imagex-from-a-ts/http://kongkuba1.spaces.live.com

I am still receiving the error message 0x0000007B even after running Michael's HAL script which runs right before "setup windows and config mgr". I assume since I set the BIOS to compatibility I do not need to include a mass storage driver, am I correct? I have also tried setting to AHCI and using all mass storage drivers I could think of it still did not work. Is there anything I can provide to you guys that would help? When I captured the OS I did not include the option "Automatically build mass storage driver list" would this have helped?

Every storage controller needs to have a driver in the image, even the built-in ones... but since sccm can do offline onjection of storage, as long as the drivers is in a package, sccm will add it to the offline image during deployment. If you don't check the "Automatically build mass storage driver list" you get 0 (zero) drivers in the image, and you will get a 0x0000007B unless you create a driver package with the storage controller. I recommend adding at least a subset of the most common drivers inside the image to keep the number of packages down in sccm... / Johan

Thank you Johan for your response. Lets say I have 3 common master storage drivers but I am not sure what hardware needs what. If I mark "automatically build mass storage driver list" while capturing the OS how do I include those drivers. Once captured when I deploy the capture OS how will SCCM know which driver to include if I do not specify a package, does it work similar to auto detect plug n play drivers? Hope that makes sense ;) Right now I have a Lenovo t510 laptop and I changed the BIOS to compatibility mode but it still will not boot when I deploy a image captured from a Lenovo desktop. So Michael mentioned to include his HAL script which I did and it still gives the 7B error when I deploy that same image with the HAL script. What is odd is both the desktop, and laptop are running the same multicore HAL right down to the version but the laptop blue screens. Its almost like a never ending circle of confusion if you know what I mean. I cant imagine im the only one facing these crazy problems, maybe because I am using the horror story Lenovo's? Thanks for sticking with me, -Logan

0x000000/B BSOD is always storage drivers missing in XP... If you include the drivers in sysprep.inf when building the reference image, you don't need to add it during deployment. Lenovo's are not better/worse than any other hardware... If you want it simpler from a storage driver point of view, deploy Windows 7 instead of Windows XP / Johan

Thank you all for the replies I resolved the problem. So I do not need to worry about storage drivers I switched the Bios to Compatibility mode, and made certain that I deployed via a driver package instead of a Auto Install Task sequence of drivers. I feel the auto install does not always download the correct drivers and this is why I kept receiving a blue screen even when not deploying mass boot drivers. I feel that Michael's HAL script also helped greatly. I now receive no errors and the correct drivers are installed. I do find that Lenovo support website does not always provide the best drivers I feel the manufacturer is sometimes better. Thanks all for the support!

Thank you all for the replies I resolved the problem. So I do not need to worry about storage drivers I switched the Bios to Compatibility mode, and made certain that I deployed via a driver package instead of a Auto Install Task sequence of drivers. I feel the auto install does not always download the correct drivers and this is why I kept receiving a blue screen even when not deploying mass boot drivers. I feel that Michael's HAL script also helped greatly. I now receive no errors and the correct drivers are installed. I do find that Lenovo support website does not always provide the best drivers I feel the manufacturer is sometimes better. Thanks all for the support!