Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2012 drivergroup drivers copied but not loading during deployment

Unanswered MDT 2012 drivergroup drivers copied but not loading during deployment

  • Tuesday, July 03, 2012 3:13 PM
     
     
    Sign In to Vote
    0

    Upgraded from MDT 2010. My old imported task sequences are working great. I created a new base image with 2012, loaded it into my production share, created a task sequence with Drivergroup001 but for some reason it will not load the drivers on any machine. I looked at the log file and the drivergroup001 is being set, PnPEnum.exe is executed and MDT is copying the correct drivers to c:\drivers (I can see them on the computer), but it is not loading them into the OS. I seems to be missing PnP/ injection step. 

    DriverGroup001 Task Sequence Variable is set in the preinstall phase

    Since I am using drivergroups I set inject drivers to nothing in preinstall phase

    Post install phase has the default inject driver task: cscript.exe "%SCRIPTROOT%\ZTIdrivers.wsf"

    In the unattend.xml I have the driver path set to:

    <settings pass="offlineServicing">

            <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DriverPaths>
                    <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                        <Path>\Drivers</Path>
                    </PathAndCredentials>
                </DriverPaths>
            </component>

    </settings>

    Any ideas why drivers will not load?

     

All Replies

  • Thursday, July 05, 2012 1:59 PM
     
     
    Sign In to Vote
    0

    Hi,

    Can you please verify in your Deployment Share:

    • Did you add your drivers into out-of-box drivers and regenerated boot image using Update Deployment Share? When you regenerate,your out-of-box drivers will be injected into your boot image.
    • Did you set the correct selection profile in your Task Sequence? cross check whether the selection profile contains your driver.

    Gud Luck

    Cheers

    Hari Rama K

     
  • Thursday, July 05, 2012 2:42 PM
     
     
    Sign In to Vote
    0

    Yes and yes

    I am able to boot off the boot disk fine, and the windows image does install on the system but does not install the drivers that are copied by MDT to the C:\Drivers folder. Doing more research I found this  in the CBS_unattend.log

     DISM   DISM Driver Manager: PID=372 ENTER InstallDriversOffline ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 Parameter Offline Windows Directory Path: 'C:\Windows' ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 Parameter Offline system drive on reboot: 'C:' ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 Offline Image has 'PROCESSOR_ARCHITECTURE_INTEL' ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 User has Administrator privileges. ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 Offline SOFTWARE hive located at: C:\Windows\system32\config\SOFTWARE ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 Loaded hive key name {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/SOFTWARE ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 Could not open key for driver path. Err = 0x00000002
     ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 Did not find driver path settings in offline hive. Exiting driver installer. Err=0x00000002 ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info                  DISM   DISM Driver Manager: PID=372 RETURN InstallDriversOffline (0) ( HRESULT = 0x0 ) - DriversCallback
    2012-07-03 14:36:50, Info           

    Looking at the registry of this is image, there does not seem to be a key telling the system to look drivers in C:\drivers

    I am not sure why this is not being set

     
  • Friday, July 06, 2012 2:30 PM
     
     
    Sign In to Vote
    0

    Hi Pete,

    I have few questions.

    1. How did you import your drivers into MDT image?
    2. Did you try creating a new TS and check?
    3. What are the file types of your drivers and what drivers you are looking at?
    4. finally, Did you try installaing these drivers manually?

    Cheers

    Hari Rama K


    • Edited by Hari Rama Friday, July 06, 2012 2:39 PM Misconception
    •  
     
  • Friday, July 06, 2012 3:00 PM
     
     
    Sign In to Vote
    0

    Hi,

    1)I have a drivergroup001 variable in the TS.

    2)Yes created a new task seqeunce. drivers are still copied the system into c:\drivers but are not installed

    3)These are normal drivers, IE network, usb etc...

    4) yes the drivers copied to the c:\drivers folder are the correct drivers and install file when I tell device manager to load them.

    The issue is for what ever reason the DISM does not know where to look for the drivers:

    DISM Driver Manager: PID=372 Loaded hive key name {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/system32/config/SOFTWARE ( HRESULT = 0x0 )

    Driver Manager: PID=372 Could not open key for driver path.

    It can not get this info from the registry. I looked for that key in the registery and it does not exisit.

     
  • Monday, July 09, 2012 5:34 AM
     
     
    Sign In to Vote
    0

    Hi Pete,

    Thanks for your reply..

    • Please check in ZTIDrivers.log whether the driver got detected by MDT.
    • Check DISM.log and setupact.log to see it the driver was injected.
    • Check Setupapi.dev.log to see if the driver was installed by setup

    also refer:

    Scenario3:

    http://www.deployvista.com/Default.aspx?tabid=78&EntryID=132

    Cheers

    Hari Rama K

     
  • Monday, July 09, 2012 7:42 AM
     
     
    Sign In to Vote
    0

    Hi,

    Could you please Provide here the TS.xml of this Task sequence?

    and one other thing, if you try to install Windows Server 2012\ Windows 8 RP - you will probably need to install MDT 2012 Update 1 Beta 1 from connect.

    Download
    MDT 2012 Update 1 Beta 1 now!

    אם תשובתי סייע בפתרון לשאלה, אנא הצבע כמועיל, תודה. Best Regards, Ori Husyt - אורי הוסיט

     
  • Monday, December 10, 2012 10:40 PM
     
     
    Sign In to Vote
    0

    This is continuing to happen with MDT 2012 update 1. when i upgraded to MDT 2012 update 1 (from 2012) and ADK,  drivers will no longer load on my vista task sequences. (win 7/8 work fine) I recreated and re-imported my custom vista image and recreated the task sequences and still no luck. C:\drivers have the correct drivers for the system but Vista OS does not load them.

     
  • Wednesday, December 12, 2012 9:35 AM
     
     
    Sign In to Vote
    0

    Did you get any help on this, or solve the issue?

    I have the same thing in my deployment. Had is all working a few days ago....then suddenly it doesnt anymore.... So I must have changed something.
    I know I added another driver subdirectory, for another machine. But that shouldn't cause any issues?

    In the logs now, I can see that the driver is found, copied to "C:\Drivers\System" and then nothing more.

    Found a driver for Device: {e2befe40-f253-484f-83db-73afc3fb2980} from \\RYDSMDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_F7BF8FB3F46E873DEA122075AE3433A8865FCA99\PantSMB.inf ZTIDrivers 2012-12-11 16:37:59 0 (0x0000)
    Validating connection to \\RYDSMDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_F7BF8FB3F46E873DEA122075AE3433A8865FCA99 ZTIDrivers 2012-12-11 16:37:59 0 (0x0000)
    Already connected to server RYDSMDT as that is where this script is running from. ZTIDrivers 2012-12-11 16:37:59 0 (0x0000)
    Copying drivers from "\\RYDSMDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_F7BF8FB3F46E873DEA122075AE3433A8865FCA99" to "C:\Drivers\System\2008s4el_9.1.0.1012_F7BF8FB3F46E873DEA122075AE3433A8865FCA99" ZTIDrivers 2012-12-11 16:37:59 0 (0x0000)
    About to run command: cmd.exe /c xcopy /seihycd "\\RYDSMDT\DeploymentShare$\Out-of-box Drivers\System\2008s4el_9.1.0.1012_F7BF8FB3F46E873DEA122075AE3433A8865FCA99" "C:\Drivers\System\2008s4el_9.1.0.1012_F7BF8FB3F46E873DEA122075AE3433A8865FCA99" 1> NUL 2>NUL ZTIDrivers 2012-12-11 16:37:59 0 (0x0000)
    Command has been started (process ID 1704) ZTIDrivers 2012-12-11 16:37:59 0 (0x0000)
    Return code from command = 0 ZTIDrivers 2012-12-11 16:38:00 0 (0x0000)

    Any idea??

    BR

    Micke Eskilander

     
  • Wednesday, December 12, 2012 2:12 PM
     
     
    Sign In to Vote
    0
    Micke is this a vista task sequence? If so there is confirmed bug by Microsoft tech, they are opening a ticket with the mdt team. If this is win 7/8 I'm not seeing any issue with drivers not loading. Check the dism.log file also CBS_unattend.log and setup.api.offlineservicing.log Should give you a better idea what's going on with the drivers
     
  • Wednesday, December 12, 2012 2:17 PM
     
     
    Sign In to Vote
    0

    OK.

    Its a Windows 7 installation.
    Sadly it's been working earlier, and somehow now it's not anymore.
    I have all the log-files, but Im not sure what to make of them.

    Will check them again.

    Thanks

     
  • Wednesday, December 19, 2012 10:11 AM
     
     
    Sign In to Vote
    0
    In my case, I had placed the driver injection to far down the task sequence.
    After the Windows installation.
    So drivers where copied to the C:\Drivers - folder, but since its made AFTER the Windows installation, no actions are made with them.

    When placing then further up the task sequence, in the "pre-install" section, the drivers are added correctly :)

    So my case is solved. :)
     
  • Wednesday, December 19, 2012 2:27 PM
     
     
    Sign In to Vote
    0
    in my vista task sequence (well all my task sequences) my driver group is set in pre-install phase. thats how it knows what drivers to download to the c:\drivers folder. MS is still working on this for me. They belive the ADK is the reason that it is not working correcly with Vista
     
  • Wednesday, January 09, 2013 7:57 AM
     
     
    Sign In to Vote
    0

    @PeteBC is there a link where the bug is described? Or are you directly in contact with MS?

    I'm having the same issue with our Vista pc's, so I'm very interested in solutions or workarounds.

     
  • Wednesday, January 09, 2013 4:13 PM
     
     
    Sign In to Vote
    0

    Im in direct contact with them. Right now they are saying the solution its to uninstall ADK, reinstall WAIK and recreate your boot disks.

    When I asked about deploying windows 8 with waik (every thing Ive read about windows 8 deployment has said you needed ADK installed) they ran a test deploying windows 8 with WAIK and they said it worked. Right now im in a holding pattern. They said they have talked to the MDT team and they might come out with a ADK update to fix the issue with vista but they are not 100% sure.

    We are not seeing many people imaging with Vista in our area now so im just telling them when they get the MDT error message to go to device manager, select the network card, install the driver from C:\drivers, and tell MDT to retry.


    • Edited by PeteBC Wednesday, January 09, 2013 4:14 PM
    •  
     
  • Tuesday, February 12, 2013 12:54 PM
     
     
    Sign In to Vote
    0

    Any news on this issue?

    Thanks

    Marc Philips

     
  • Monday, March 11, 2013 12:08 PM
     
     
    Sign In to Vote
    0
    Micke is this a vista task sequence? If so there is confirmed bug by Microsoft tech, they are opening a ticket with the mdt team. If this is win 7/8 I'm not seeing any issue with drivers not loading. Check the dism.log file also CBS_unattend.log and setup.api.offlineservicing.log Should give you a better idea what's going on with the drivers

    Did you find a workaround for this issue. I have the same problem with the "apply driver package" action in a vista 32 Bit sequence. Do you have a bug id or a source?

    thanks