Drive Injection not working > Deployment Forum Community Forums

Subject: Drive Injection not working

You are not authorized to post a reply.

Author

Messages

Posts:5

04/18/2008 8:24 AM
I am pulling my hair out with driver injection not working on ZTI builds, I am using SMS 2003 and MDT 2008, I can create my lab build no problem, drivers inject, everything works perfectly. I then capture the WIM using the OSD capture CD created in SMS, I then create a OSD package in SMS using the WIM, and create a Installation CD from within SMS (I have updated PE on the SMS server to use the source from the MDT server) Boot from the Installtion CD, and all is good, I get the menu with the one OSD build, install it and all works fine, except the driver injection, for some reason it does not work. I think I am doing something fundermentally wrong I have created a SMS package with all my drivers and the XML files, I have update CS.INI with ResourceRoot=%SMSDP%\SMSPKGE$\NH100146, I have updated my Bootstrap.ini with the OS package ID and program name. In advanced properties on the SMS program I have only got two custom actions, one in the validate phase that just runs ZeroTouchInstallation.vbs and one in the post install ZTIDrivers.wsf. I have added all the files from \\XXBDD01\Distribution$\Scripts. Can any one point me in the right direction here. Thanks MK

C Barrett

Posts:19

04/21/2008 2:39 PM
Have you updated your SMS Distribution points after you made the changes to CD.ini?

C Barrett

Posts:19

Posts:5

04/22/2008 4:24 AM
Thanks Carl, my CustomSettings.ini looks like this on the SMS DP [Settings] Priority=Default Properties=MyCustomProperty [Default] ResourceRoot=%SMSDP%\SMSPKGE$\NH100147 OSInstall=Y UserDataLocation=NETWORK [SMS] SQLServer=NHSMS01 Database=SMS_NH1 Table=v_Program Parameters=PackageID,ProgramName SQLShare=SMSClient Do I need to specify somewhere the MDT server within the SMS package ?

C Barrett

Posts:19

04/22/2008 5:01 PM
I'll check this out 2moro when I can look at my CS.ini - in the meantime just double check you have the correct SMS package specified in your "ResourceRoot" as this is where I cocked up during my OSD testing! :-)

C Barrett

Posts:19

04/23/2008 2:27 PM
Your CS.ini looks OK (when I compare it to mine at least) the only change I made was to specify my SMS servername rather than use "%SMSDP%" The only other thing to check is the content of your "NH100147" package - recommend you take a look in here just to make sure you have the "control" directory and the "out-of-box drivers" directory Finally try this video from Richard Smith which covers everything needed to set up ZTI for SMS 2003...if you haven't already seen it... http://www.deploymentforum.com/Portals/3/media/bdd.zti/config.wmv HTH

Posts:5

04/24/2008 4:35 AM
I have hard code the name of the local SMS server into CS.INI and still the same, I have taken a look at the video you gave me the link for, yes have seen that before, but thanks anyway. Can you tell me, on your advanced tab within the SMS Program, what have you got for each phase, and what files have you added for each phase ? Thanks MK

C Barrett

Posts:19

04/29/2008 6:46 AM
sorry for the delay... [u[Validation Command = ZeroTouchInstallation.vbs Files = All files found in your \\%distributionserver%\%OSD_Deploymentpoint%\%OSD_Build_Name%" directory (make sure you select "Files of all types" when searching for files to add...) State Capture Command = ZeroTouchInstallation.vbs PreInstall Command = ZeroTouchInstallation.vbs PostInstall Command = ZeroTouchInstallation.vbs (I also have a HAL Swap action but this is non-standard) State Restore Command = ZeroTouchInstallation.vbs Hope this helps

Posts:5

05/06/2008 9:23 AM
Hi Carl Thanks for that, currently I have \\MDTServer\Distribution$\scripts (entire contents) added in on the Advanced tab in SMS, is that not right ?? the ZeroTouchInstallation.vbs is kicking up the exit code 2147500037, I have currently only got it specified at the PostInstall phase Cheers Mark

bpostiau

Posts:7

05/06/2008 8:28 PM
hi this error means that "the specified network resource or device is no longer available" brgds bruno

Posts:5

05/07/2008 4:16 AM
Can someone please post a working CS.ini and Bootstrap.ini from a working config. Thanks Mark

C Barrett

Posts:19

05/08/2008 5:18 PM
Hello Mark, This part looks incorrect: \\MDTServer\Distribution$\scripts (which I only just noticed IS in your first post - sorry!) You should have created an SMS OSD Deployment point, the default share name for this is "ZTI$" in both BDD 2007 and MDT - have you created this DP? If not do this and then make your OSD Build available for your OSD DP Return to SMS and on the advanced tab select all the files found in your OSD build from the OSD DP....so the path will be something like \\XXBDD01\ZTI$\OSDBuild1 Check the other phases are set up to use "ZeroTouchInstallation.vbs" (as in the other post) and hopefully you should be on your way. I'll try and remember to post my CS.ini and Bootstrap 2moro also

You are not authorized to post a reply.

Forums > Deployment Solutions > MDT 2008 > Drive Injection not working