Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all articles
Browse latest Browse all 9126

SCCM 2012 R2 CU2 - OSD Surface Pro 4 - Drivers missing after Imaging

$
0
0

Having an issue with getting the Surface Pro 4 to install all the drivers during the imaging process.  I have imported all the drivers into the Database and setup the Task Sequence to Auto Apply Drivers for the system using:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%Surface Pro 4%"

After imaging, all but 7 drivers get installed?

Intel High Definition Audio

Intel High Definition DSP

SurfaceCoverIntegration{4E781CFC-87EE-459B-A319-9B0531EB7485}

SurfaceCoverIntegration{5E9A8CDC-14AB-4609-A017-68BCE594AB68}

and 4 unknown devices.....

SMTSLOG shows it's evaluating to be true and does in fact install most of the drivers.  Just not the above. 

Query = SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%Surface Pro 4%" TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Expand a string: root\cimv2 TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Expand a string: SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%Surface Pro 4%" TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
The WMI condition expression is evaluated to be TRUE TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
The OR expression is evaluated to be TRUE TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
The AND expression is evaluated to be TRUE TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
The condition for the action (Microsoft Surface Pro 4) is evaluated to be true TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Expand a string: osddriverclient.exe /auto /bestmatch:%OSDAutoApplyDriverBestMatch% /unsigned:%OSDAllowUnsignedDriver% TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Expand a string:  TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Command line for extension .exe is "%1" %* TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Set command line: osddriverclient.exe /auto /bestmatch:%OSDAutoApplyDriverBestMatch% /unsigned:%OSDAllowUnsignedDriver% TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Start executing the command line: osddriverclient.exe /auto /bestmatch:%OSDAutoApplyDriverBestMatch% /unsigned:%OSDAllowUnsignedDriver% TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
!--------------------------------------------------------------------------------------------! TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Expand a string: WinPE TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
Executing command line: osddriverclient.exe /auto /bestmatch:%OSDAutoApplyDriverBestMatch% /unsigned:%OSDAllowUnsignedDriver% TSManager 1/28/2016 7:58:02 AM 1936 (0x0790)
============================[ OSDDriverClient.exe ]============================ OSDDriverClient 1/28/2016 7:58:03 AM 1020 (0x03FC)
Command line: "osddriverclient.exe" /auto /bestmatch:false /unsigned:true OSDDriverClient 1/28/2016 7:58:03 AM 1020 (0x03FC)
Driver path is C:\_SMSTaskSequence\drivers OSDDriverClient 1/28/2016 7:58:03 AM 1020 (0x03FC)
Driver-signing policy cannot be configured on this operating system. An administrator must always authorize the installation of unsigned drivers or a driver from a publisher that is not yet trusted. OSDDriverClient 1/28/2016 7:58:03 AM 1020 (0x03FC)

Any ideas?  Or places to look?


Viewing all articles
Browse latest Browse all 9126

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>