Option 3: Move to Windows Vista and never worry about mass storage drivers again. (Sorry, couldn't resist.)
Yes, your understanding sounds right to me.
-Michael
I am trying to figure out Mass Storage in deploying Windows XP using SCCM OSD with MDT. I am moving from SMS 200 BDD 2007 to SCCM 2007 R2 with MDT.
From what I can tell, I have two options for Mass Storage Drivers.
I can either do it the old (SMS 2003) way, place the drivers in the captured image using a modified MassStorageDrivers section in Sysprep.inf
Or
I can do it the new way which is to have a MassStorage Driver package that I apply during the deployment stage rather than the capture stage.
The cons to the first option is that a new capture is required any time I want to add a new storage driver.
The cons of the second option is that I need to know the model name or have some way to otherwise identify every single computer that needs out of box drivers and make a filtered "Apply Driver Package" for every one of the models of computers that requires an F6 type driver.
I think option two sounds like a lot more work, but more organized. Also, new or unknown models are unlikely to work without intervention on the OSD team. With option one, it takes a whole new chipset to be release before a change is needed.
So my question is, do I understand the situation correctly?
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/
==============
Missed an email? Check out the list archive:
http://myitforum.com/cs2/blogs/smslist/