I'm running a test lab with SCCM R3 SP2 and OSD (no MTD2010). For last month I learn a lot of Operating System Deployment, but still there is missknowledge about Drivers issue. I'm not sure what is the best way to install drivers during Task Sequence and I have a problem with Mass Storage Driver. I'm deploying Windows XP SP3 and I after first OS restart I get 0x0000007B. I have one old desktop and one old laptop, both with IDE hard drive. I noticed, that when using Driver Package, Mass Storage Drivers is always required, is that right? Where I can find those for old models? Is there any generic drivers? Both computers use Intel chipsets. Another problem is, that during Task Sequence the installed computer won't join domain. Still, network connectivity exists if I use F8 and go to command line. Should Win PE 3.0 support all common network cards? And what is differense between unattended and sysprep? How I should those? Most important is to define regional settings, language and keyboard layout for installed computers. Sorry again for n00b questons. I can't find any decent information about these issues.

Here is error from log about applying driver package - Failed to run the last action: Apply Driver Package. Execution of task sequence failed. The hash value is not correct. (Error: 80091007; Source: Windows) I've updated DP's for a few times and checked out the log that it was succsessful.

Another problem is, that during Task Sequence the installed computer won't join domain. Still, network connectivity exists if I use F8 and go to command line. Should Win PE 3.0 support all common network cards? Windows PE 3.0 is a light version of Windows 7. You need to use Windows 7 drivers for your Windows PE boot image. So the answer is no. Windows PE 3.0 does not have the all drivers you'll need... This guide wil help you import drivers in Windows PE: http://www.ronnipedersen.com/2009/04/importing-network-drivers-into-the-windows-pe-boot-image/Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

I'm running a test lab with SCCM R3 SP2 and OSD (no MTD2010). I'm deploying Windows XP SP3 1. Start using MDT... No need to reinvent the wheel again... MDT will get you started MUCH faster... 2. Do you really want that? I mean... You’re playing in a test lab, trying to learn deployment and Windows XP is close to be "End of Life"... Start playing with Windows 7. It's a lot easier. Even if you really want to do Windows XP deployments, start with Windows 7, and learn the basics on an OS that was built with deployment in mind :o)Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

Thank you Ronni, I'll look that up. The reason of holding with Windows XP is that my job is unfortunately very much XP related and I want to know "how this all began".. meaning OSD :) ..and I also have old hardware that does not fully support 7 because of lack of drivers. Before reading last post, I add 2 collection of Mass Storage Drivers to SCCM driver database: http://driverpacks.net/driverpacks/windows/xp/x86/mass-storage/10.11 http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=321957&prodSeriesId=4095872&swItem=ob-81362-1&prodNameId=4095873&swEnvOID=1093&swLang=13&taskId=135&mode=4&idx=3 I used auto apply drivers and unattend non-signed drivers included. Still, model HP Compaq nc6220 gives me the BSOD 0x0000007B. Any ideas? Is there any chance to make it working, or should I just capture reference machine of this model with drivers included?

Using the "Auto Apply Drivers" step will not allow you to inject mass storage drivers... Check out this post. That should get you started: http://usjensen.wordpress.com/2008/12/08/how-i-handle-boot-critical-drivers-mass-storage-drivers-for-windows-xp-in-configmgr-os-deployment/ Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

Thanks. Now I need to know only to things: - how come laptop with IDE (ATA) hard drive needs Mass Storage Driver (isn't all mass storage drivers are for SATA?) - what mass storage driver is required for HP Compat nc6220? HP Driver download site does not provide any.

I think this is the driver you''ll need: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=17882&lang=engRonni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

We are getting close, but not done yet :) Yes, I found 4 different drivers like Intel(R) 82801XX Ultra ATA Storage Controller which is listed in Driver Package, but when I add it to task secuence and try to choose it as mass storage, there is only only other SATA drivers available, but not Ultra ATA. This is very weird!

I've talked with one of our deployment specialist, and he told that when dealing with XP, every driver should be imported as unique, and not as a mass deployment. I should try that later.

That is also explained in this post: http://usjensen.wordpress.com/2008/12/08/how-i-handle-boot-critical-drivers-mass-storage-drivers-for-windows-xp-in-configmgr-os-deployment/Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

That is also explained in this post: http://usjensen.wordpress.com/2008/12/08/how-i-handle-boot-critical-drivers-mass-storage-drivers-for-windows-xp-in-configmgr-os-deployment/ Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen Ok, I got it. Only last question is - do I really have to play around with queries and WMI, or could it work if I just import one Ultra ATA driver at the time?

It would work, Yes. But if you don't use the filters the driver would also be installed on clients that doesnt need the driver. If thats ok with you, you should be fine... Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

It would work, Yes. But if you don't use the filters the driver would also be installed on clients that doesnt need the driver. If thats ok with you, you should be fine... Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

I know exactly what driver models my laptop require, so I believe I don't need filters, isn't that right? I only import one driver at the time to driver package. I also use 1 task sequence per model. With Windows XP, problem is this - wherever I use auto apply or package apply, drivers are imported to c:\drivers but none of them is installed. I also cannot see mass storage drivers in those 2 sections of mass storage options. Should Auto Apply Drivers work on Windows XP if only specific-model compatible drivers are imported?

I know exactly what driver models my laptop require, so I believe I don't need filters, isn't that right? I only import one driver at the time to driver package. I also use 1 task sequence per model. With Windows XP, problem is this - wherever I use auto apply or package apply, drivers are imported to c:\drivers but none of them is installed. I also cannot see mass storage drivers in those 2 sections of mass storage options. Should Auto Apply Drivers work on Windows XP if only specific-model compatible drivers are imported?

I also use 1 task sequence per model. Then you don't need to use any filters.Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

I also use 1 task sequence per model. Then you don't need to use any filters.Ronni Pedersen | Configuration Manager MVP | Blog: http://ronnipedersen.com/ | Twitter @ronnipedersen

So any ideas, why Intel and Nvidia Ultra ATA Storage controller drivers are not seen in Driver Package Mass Storage menu?

Drivers are probably not seen in Mass Storage options because they aren't included in txtsetup.oem file. And modifying it is out of my skill (..also my will and time), so I'm thinking why not import Ultra ATA drivers to Windows XP .wim image and leave everything else to task sequence driver package apply. Where I should import files?

I finally realized what my problem was - I read this article and everything is now clear... almost :) http://www.vernalex.com/guides/sysprep/mass.shtml In this site I found best explanation of mass storage devices and how to use sysprep to get around with mass drivers.