ConfigMgr – Dealing with Windows XP Mass Storage Drivers

Roger Zander had posted another nifty way of dealing with mass storage drivers here, basically created a task sequence section that detects the mass storage device and injects the driver.  This is an alternative method to injecting the mass storage driver from within a model specific driver package. For example having a driver package for a Lenovo T61p that includes the Intel Mass storage driver and selecting it, similar to the screenshot below:

[image unavailable]

Here is the link to Roger’s post:

http://myitforum.com/cs2/blogs/rzander/archive/2009/08/07/apply-xp-massstorage-drivers-from-sccm-osd-task-sequence.aspx

What i want to do with this post is show you how to take that information above and import it into your existing OSD TS.

1. Download and extract out the task sequence so that we have the file we will need to import.

[image unavailable]

2. Next we need to prepare ourselves for the task sequence, so lets make sure we have a Mass Storage Driver Package created and the appropriate drivers in that package.

[image unavailable]

[image unavailable]

3. Next lets import the task sequence that we downloaded previously

[image unavailable]

Browse to and import the “massstoragedrivers.xml”

[image unavailable]

You’ll first get an error message about an invalid boot image:

[image unavailable]

Then an error message about invalid packages:

[image unavailable]

Click on edit on this screen, and then we can correct the task sequence to point to the correct Mass Storage Driver Package for our site.

Once it loads you’ll have a nice TS with a bunch of errors:

[image unavailable]

Credit due where credit is due! :)

[image unavailable]

So first lets fix the VMware SCSI Controller as an example:

We first need to browse to our Mass Storage Driver Package:

[image unavailable]

Then we need to modify the values to fit the entry we are editing:

[image unavailable]

If for some reason you don’t have a signed driver, you will need to check this box:

[image unavailable]

You can see if you have a signed driver by looking at the driver properties in the console:

[image unavailable]

Now that we’ve modified the VMware SCSI Controller entry, you can see that we have one green check box now:

[image unavailable]

So we need to go through and modify the rest of them so that these TS entries are valid for our environment, I disabled a few that I don’t want to use right now, also the disabled ones are ones that are not in the standard Intel RAID/AHCI drivers.

[image unavailable]

So now we have a TS that contains valid entries for our environment, so i need to incorporate this into an existing TS of mine.

4. Integrating the Mass Storage task sequence steps in an existing OSD task sequence.

NOTE: You can also move the Mass Storage steps into your task sequence by using copy/paste, in order to do this, you need to have both task sequences’s open at the same time. This is easier than editing the XML.

Here is a basic Windows XP TS that i’ve added a “Driver Management” category to. (No MDT integration, even though i normally use MDT)

[image unavailable]

The Driver Management category is good because it gives me a place in the TS that i can find when editing it to add my new content. That’s typically how i prefer to manage my TS’s.

First lets export our TS so we can work with it. We need to export our Mass Storage Driver TS and our OSD TS.

[image unavailable]

All exported:

[image unavailable]

Next lets open up our OSD TS with notepad ++ and find the Driver Management section we created:

[image unavailable]

Also, open up the Mass Storage TS.

Now we need to copy the “steps” from the Mass Storage TS to our OSD TS.

You basically want what i’ve detailed in this screen shot (it’s a collapsed view). This is in the Mass Storage task sequence we exported.

[image unavailable]

This will give us a new group and the relevant steps. Basically the information we want to copy over into our existing task sequence.

Lets move this information over to our OSD ts, and we want to place it right below the line i’ve detailed below.

[image unavailable]

This will create a new group and steps underneath it.

[image unavailable]

After we paste this info (collasped view again) you will see that i have a new group called “MassStorage Drivers” underneath my “Driver Management” group:

[image unavailable]

Now lets save the TS, exit notepadd ++, and then we need to import the task sequence back into ConfigMgr.

Next we look at our new OSD TS and see the new “Mass Storage” steps under our “Driver Management” section in our TS.

[image unavailable]

There we go, we now have the new Mass Storage detection section in our Windows XP task sequence.

5. Time to test

6. Test again :)

This post should help you be able to configure the information Roger/Richard put together and integrate it into your existing task sequence without too much trouble. I hope this helps, and remember to test :)

-Chris