Siroj Posted September 22, 2015 Report post Posted September 22, 2015 We are running a single SCCM 2012 R2 SP1 CU1 server in out LAB environment with the following patches applied: https://support.microsoft.com/en-us/kb3091103/ https://support.microsoft.com/en-us/kb/3089193 https://support.microsoft.com/en-us/kb/3084586 We are LAB testing the Windows 10 deployment to our devices, including Surface Pro 3, Dell E5550, Dell E5530. Boot image is version WinPE 10.0.10240.16384 At this moment we are having issues with installing device drivers during deployment. Some drivers get installed without problems, but most of them won't install at all. Following is logged in smsts.log for every device that has a missing device driver: Unsuccessful in finding a suitable device driver for device 'Microsoft Storage Spaces Controller'. OSDDriverClient 22-9-2015 13:13:03 1692 (0x069C) Unsuccessful in finding a suitable device driver for device 'Microsoft Basic Display Driver'. OSDDriverClient 22-9-2015 13:12:59 1692 (0x069C) ... All drivers got installed successful in SCCM without errors, categorized and packages are created + deployed. Manually installing the drivers afterward using the same source files works without a problem and all drivers get installed perfectly so the drivers are correct. We have played around with setting "Best mached drivers" and "Limiting driver categories" for Auto Apply Drivers but to no result. The TS includes SMSTSDownloadRetryCount and SMSTSDownloadRetryDelay, without this the TS would error out. For testing we also tried Windows 7 deployment + drivers on the same server and that worked without problems and all drivers get installed. Anyone have any idea about this? Quote Share this post Link to post Share on other sites More sharing options...
Jorgen Nilsson Posted September 22, 2015 Report post Posted September 22, 2015 Hi, Haven't tried that, apply driver package always works so much better than apply driver. I would test that instead and then it should work as you tell the ConfigmGr client what drivers should be installed. /Jörgen Quote Share this post Link to post Share on other sites More sharing options...
Siroj Posted September 22, 2015 Report post Posted September 22, 2015 Alright, thanks for the feedback. I'll try it immediately and post back here... Quote Share this post Link to post Share on other sites More sharing options...
Siroj Posted September 22, 2015 Report post Posted September 22, 2015 Using the package seems to fix the problem. Just imaged a Surface Pro 3 and all drivers installed nicely! Still wondering why the Apply Driver step doesn't work for Windows 10..?.. 1 Quote Share this post Link to post Share on other sites More sharing options...
Siroj Posted September 22, 2015 Report post Posted September 22, 2015 One additional question: our Surface Pro 3 driver package includes all recent drivers and firmware. When applying the driver package in our TS, does this also automatically install all applicable firmware updates? Quote Share this post Link to post Share on other sites More sharing options...
NickolajA Posted September 22, 2015 Report post Posted September 22, 2015 I'm quite sure it doesn't, but please correct me if I'm wrong. Have a look at this post for how to deploy firmware updates: http://sunbehindtheclouds.com/2015/01/21/managing-surface-pro-drivers-and-firmware-in-the-enterprise/ Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted September 23, 2015 Report post Posted September 23, 2015 yes it should install all applicable firmware updates, you can check the versions in device manager (Firmware) and compare it against the versions in the drivers released 1 Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted September 23, 2015 Report post Posted September 23, 2015 does this also automatically install all applicable firmware updates? Also just to add depending on when your Surface was manufactured and the release\version of your driver\firmware package would depend if firmware gets updated as the surface may already be shipped with the latest firmware. You should see after the first restart when the agent gets installed that the device will display applying system updates, this is the newer firmware been applied to the older.(correct me if I am wrong) Quote Share this post Link to post Share on other sites More sharing options...
pk@ianz Posted September 22, 2017 Report post Posted September 22, 2017 Hi. I have an issue where the audio drivers are not getting installed during the deployment for Surface Pro 4. I am using MDT for deployments. Below is the ZTI drivers log. Found Device HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101 with 3rd party drivers! Count = 1 = {a0802322-6c56-4368-89f4-2e487bda60b1} {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc} ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101: {a0802322-6c56-4368-89f4-2e487bda60b1} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484\IntcDAud.inf ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484 ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) Mapping server share: \\WDS\UDSept2017$ ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) Already connected to server WDS as that is where this script is running from. ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" to "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" 1> NUL 2>NUL ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) Command has been started (process ID 2728) ZTIDrivers 23/09/2017 8:55:40 a.m. 0 (0x0000) Return code from command = 0 ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101: {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763\IntcDAud.inf ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763 ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) Mapping server share: \\WDS\UDSept2017$ ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) Already connected to server WDS as that is where this script is running from. ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" to "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" 1> NUL 2>NUL ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) Command has been started (process ID 2760) ZTIDrivers 23/09/2017 8:55:41 a.m. 0 (0x0000) Return code from command = 0 ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Found Device HDAUDIO\FUNC_01&VEN_8086&DEV_2809 with 3rd party drivers! Count = 1 = {a0802322-6c56-4368-89f4-2e487bda60b1} {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc} ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809: {a0802322-6c56-4368-89f4-2e487bda60b1} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484\IntcDAud.inf ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484 ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Mapping server share: \\WDS\UDSept2017$ ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Already connected to server WDS as that is where this script is running from. ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" to "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" 1> NUL 2>NUL ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Command has been started (process ID 2796) ZTIDrivers 23/09/2017 8:55:42 a.m. 0 (0x0000) Return code from command = 0 ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809: {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763\IntcDAud.inf ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763 ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) Mapping server share: \\WDS\UDSept2017$ ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) Already connected to server WDS as that is where this script is running from. ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" to "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" 1> NUL 2>NUL ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) Command has been started (process ID 2828) ZTIDrivers 23/09/2017 8:55:43 a.m. 0 (0x0000) Quote Share this post Link to post Share on other sites More sharing options...