Driver Packages Imported with DCDP Not Installing Correctly

Question

I manually created an image and captured it using the SCCM Capture CD from 'Create Task Sequence Media'. The image is already imported into SCCM, and I can deploy the image. However, the drivers are not installing properly from the CABs I imported.

I installed DCDP on SCCM R2 SP2. I was able to successfully import the CABs as driver packages. However, after configuring and editing the task sequence per the posted whitepaper (Operating System Deployment on Dell Enterprise Client Systems using Microsoft System Center Configuration Manager 2007), several drivers are not properly installed after logging into the Desktop for the first time. This problem happened with a Latitude E6320 and Optiplex 390 using their respective drivers. I am not currently using Combo CABs at this point. I've noticed the USH, video, and NIC drivers are not being installed.

The sequence is as follows:

Restart in Windows PE (boot image assigned)
Connect to Network Folder (necessary for access to a DISKPART script)
Run Command Line (processes the DISKPART script I created)
Apply Data Image 1 (second partition specified, as Dell diags exist on the first partition)
Apply Operating System (Image 2 applied to the third partition - includes Unattend.xml)
Apply Windows Settings
Apply Network Settings (currently configured to join the domain, which is not working)
Apply Driver Package (appropriate driver package selected with 'Do unattended installation of unsigned drivers' checked and the WMI query Option enabled)

Please note the conditions used for the Optiplex 390:
select * from Win32_ComputerSystem where Manufacturer like 'Dell%' AND Model like '390%'

To complete the task sequence, these items follow:

Setup windows and ConfigMgr
Install Updates

Any help would be greatly appreciated to correct this.

Thanks!

Lunatek · Answer

I ended up removing the WMI query from the Options tab. This corrected the problem I was having on both models. FYI

DELL-Warren B · Answer

Removing the WMI query essentially invalidates the reason for having driver specific packages and increases the time to build your systems because all driver packages are applied to all systems. You should re-instate the query and verify that the query was working correctly to address the issue.

Lunatek · Answer

'Removing the WMI query essentially invalidates the reason for having driver specific packages and increases the time to build your systems because all driver packages are applied to all systems. You should re-instate the query and verify that the query was working correctly to address the issue.' The tests responded with a result of 0. I need the correct syntax for each model's WQL query to implement this properly. Are they posted anywhere on this site? So far, I've been successful deploying individual driver cabs without it. I have a task sequence configured to apply a driver package to a Latitude E6320 using the model-specific cab.

Lunatek · Answer

'The tests responded with a result of 0. I need the correct syntax for each model's WQL query to implement this properly. Are they posted anywhere on this site? So far, I've been successful deploying individual driver cabs without it. I have a task sequence configured to apply a driver package to a Latitude E6320 using the model-specific cab.' I tried the following, which did not work (the drivers fail to install properly if I include this from the posted white paper): select * from Win32_ComputerSystem where Model like 'E6320%' I tried it with 'Latitude E6320%', as well. That also failed.

Systems Management General

Driver Packages Imported with DCDP Not Installing Correctly

Was this post helpful?