Friday, January 09, 2009
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Community   »   Forums  
Member Login
StandardLiveID


Register
Forgot Password ?

Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Forums > Deployment Solutions > MDT 2008
Subject: MDT 2008 and injecting MassStorageDrivers
Prev Next
You are not authorized to post a reply.

AuthorMessages
Old_ChicagoUser is Offline

Posts:26

Send Message
05/13/2008 1:24 PM  
Does MDT 2008 inject drivers into an image that has already been syspreped?  Has anyone tried this yet?

O.C.

FarmerPeteUser is Offline

Posts:168

Send Message
05/14/2008 8:33 AM  
With Windows XP the answer is no. I'm not sure about Vista. Both will inject non massstorage drivers, but XP doesn't like them so much after the fact.
KonradUser is Offline

Posts:67

Send Message
05/18/2008 5:59 PM  
I believe that MDT 2008 introduced this for XP with the new task sequence step "Inject Storage Drivers for XP and 2003". This runs the command line:
cscript.exe "%SCRIPTROOT%\ZTIStorageDriversSysprep.wsf"


If you migrate your task sequence from MDT 4, then you won't have this step and you'll have to add it yourself under "Preinstall", just after "Inject Drivers". If you create a new task sequence under MDT 2008 it puts this step in for you.

There is also a corresponding step for task sequences that use a scripted build which run the command line:
cscript.exe "%SCRIPTROOT%\ZTIStorageDrivers.wsf"


Mind you, I only just went to use this step for the first time last week using a VMWare ESX client (which uses SCSI) and it only almost worked for me, but I haven't had much of a chance to investigate it yet.

Old_ChicagoUser is Offline

Posts:26

Send Message
05/20/2008 8:15 AM  
I think there is more to it then just adding this step into the Task Sequence.  I didn't build my custom image from MDT.  I did all the manual work myself, then used ImageX to capture the WIM.  Since MDT updates Sysprep, I imagine I am going to have to rebuild my image completely using MDT. 
DietmarUser is Offline

Posts:70

Send Message
05/23/2008 3:33 AM  
The only solution for integrating mass storage drivers into Windows XP is to recreate the image. The other solution is to use Vista.

To integrate the drivers into LTI use this: http://www.deployvista.com/Blog/tabid/70/EntryID/18/language/en-US/Default.aspx
To integrate the drivers into ZTI use this: http://blogs.technet.com/benhunter/archive/2007/07/12/bdd-2007-integrating-mass-storage-drivers-into-your-xp-image.aspx

Both works fine for us. Thanks to the authors!
Old_ChicagoUser is Offline

Posts:26

Send Message
05/29/2008 10:48 AM  
With MDT 2008, you have the capability of injecting mass storage drivers into your image.  I'm not looking for the manual way to do this.  I'm trying to get away from this, actually.

 

Cheers,

 

OC


DietmarUser is Offline

Posts:70

Send Message
05/30/2008 4:18 AM  

With Windows XP there is no way to inject mass storage device drivers after sysprep.
I really tried all ways before I created a new master image. At least I did create a new master image and injected the drivers with the sysprep.inf file. This woks really fine and I think it´s simple. You have to create the sysprep.inf only one time for future use.

 

You are not authorized to post a reply.
Forums > Deployment Solutions > MDT 2008 > MDT 2008 and injecting MassStorageDrivers



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.
Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt