Kevin’s blog

Links to other SCCM SEE blogs

KevinMSFT — Mon, 10 Jul 2017 21:48:12 GMT

SCCM topics OSD Frank Rojas & Wilhelm Kocher https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/ DRS/SQL/SCCM DB + other Umair Khan - https://blogs.technet.microsoft.com/umairkhan/ Senthilkumar https://blogs.technet.microsoft.com/senthilkumar/ SUS/WSUS Meghan Stewart & others - https://blogs.technet.microsoft.com/sus/ The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance ConfigMgr Support Team blog: https://blogs.technet.com/configurationmgr/

Sys Ctr Config Mgr 1610 | ADK 1703 | Windows 7 OSD with NVME SSD HDD - failing to apply drivers randomly

KevinMSFT — Wed, 28 Jun 2017 04:08:45 GMT

ISSUE

When deploying Windows 7 OSD - drivers are randomly not applying . Some workstations fails at application of different drivers (USB/video/NIC)

smsts.log
Current OS version is 10.0.15063.0
..
OS version is 6.1 ( OS system file version found to be 6.1.7601.23572 )
..
Executing command line: "X:\windows\system32\dism.exe" /image:"C:" /windir:"Windows" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"
Process completed with exit code 2147500037
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,548)
Dism failed with return code -2147467259
AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,658)
Failed to add driver to driver store. Code 0x80004005
InstallDriver( pDriver->getContent()->getContentId(), sSource, 0 ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,622)


dism.log
Failed to load offline schema.dat hive from '\\?\C:\Windows\system32\smi\store\Machine\schema.dat' into registry key '{abc123-ab12-1234-ab12-abc12345678}C:/Windows/system32/smi/store/Machine/schema.dat'. [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
Failed to load SMI schema hive [HRESULT = 0x80070020 - ERROR_SHARING_VIOLATION]
Unloading offline registry hive: {abc123-ab12-1234-ab12-abc12345678}C:/Windows/System32/config/SOFTWARE
Failed to unload offline registry: {abc123-ab12-1234-ab12-abc12345678}C:/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
...
DISM Package Manager: PID=1812 Failed initializing the session - CDISMPackageManager::RefreshInstanceAndLock(hr:0x80070020)
DISM Package Manager: PID=1812 Failed doing internal initialization - CDISMPackageManager::Initialize(hr:0x80070020)
DISM Provider Store: PID=1812 Failed to call Initialize method on IDismServicingProvider Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80070020)
DISM Provider Store: PID=1812 Failed to Load the provider: C:\_SMSTaskSequence\PkgMgrTemp\abc123-ab12-1234-ab12-abc12345678\CbsProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80070020)

RESOLUTION

3 Workarounds can be found on the System Center blog by Frank Rojas In my customer's case, he used workaround 2 and was pleased with the result. Workaround 2 does not use the Apply Driver Package at all. Instead it uses the Download Package Content task to first download the Driver Package to a specified directory and then using more or less the same command line from Workaround 1, it installs the drivers. This workaround also resolves the problem by only having to initiate one registry load/unload during the DISM driver injection process. Since the Download Package Content task is only available with ConfigMgr Current Branch, this workaround cannot be used with older versions of ConfigMgr (ConfigMgr 2012 SP2/R2 SP1 or ConfigMgr 2007). https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2016/12/28/apply-driver-package-task-fails-when-the-adk-is-upgrade-to-adk-10-1607/ ~Kevin Lee Support Escalation Engineer | Microsoft System Center Configuration Manager Disclaimer: This posting is provided “AS IS” with no warranties and confers no rights.

Win 10 1607 OSD upgrade hangs with "Starting Driver Inventory" in setupact.log

KevinMSFT — Wed, 28 Jun 2017 03:07:47 GMT

Recently resolved a case with a Windows 7 - 10 IPU issue that I wrote a help document internally with the help of Frank Rojas but has now been posted publicly (https://support.microsoft.com/en-us/help/4020149/updates-fix-in-place-upgrade-to-windows-10-version-1607-problem) Additional details about it can be found below.

ISSUE

When upgrading Windows 7 to 10 via SCCM with the integrated Operating System Upgrade task sequence using the Windows 10 1607 Enterprise media. We are continuously running into the error of 0xC1900208 which is flagged as a compatibility error on the workstation. However, using the same exact media loaded onto a thumb drive or network share, I receive no compatibility errors. SMSTS.log shows these entries: 02-16-2017 10:04:55.970 OSDUpgradeWindows 4940 (0x134c) Windows Setup failed with hexadecimal exit code 0xC1900208 (decimal 3247440392). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online. 02-16-2017 10:04:55.970 OSDUpgradeWindows 4940 (0x134c) Failing this task sequence step NOTICE THAT setupact.log stops abruptly at: 02-27-2017 13:14:23.000 CONX Windows::Compat::Appraiser::WicaApplicationInventory::GetInventory (263): Starting Application Inventory. 02-27-2017 13:14:23.000 CONX Windows::Compat::Appraiser::DriverInventory::GetInventory (204): Starting Driver Inventory.

CAUSE

Windows 10 1607 known issue

RESOLUTION/WORKAROUND

Apply compatibility update for upgrading to Windows 10 Version 1607: January 10, 2017 or later https://support.microsoft.com/en-us/help/3211309/compatibility-update-for-upgrading-to-windows-10-version-1607-january-10,-2017 The hotfix description is a bit generic and unfortunately does not describe the issues it corrects, including this issue. Also this hotfix is implemented a bit different than your standard hotfix. Please take the following steps to apply the hotfix: 1) Download the hotfix from https://www.catalog.update.microsoft.com/Search.aspx?q=3211309 2) After downloading the CAB file, extract its contents. 3) Determine the source directory of your Windows 10 1607 installation files. You can find this in the properties of the Upgrade Operating System Package 4) After determining the source directory, copy the contents of the extracted CAB file into the Source folder of the Windows 10 1607 installation files. Click yes to overwrite any existing files 5) Update the DPs for the Upgrade Operating System Package 6) Once the DPs have been updated, retry the deployments and see if the issue is corrected

MORE INFORMATION:

NOTE: KB 3211309 has been superseded twice by KB4013420 on March 14, 2017 which was later superseded by KB4016654 on April 11, 2017 https://support.microsoft.com/en-us/help/4013420/compatibility-update-for-upgrading-to-windows-10-version-1607-and-windows-server-2016-march-14-2017 https://support.microsoft.com/en-us/help/4016654/compatibilityupdateforupgradingtowindows10version1607andwindowsserver2016april11,2017 ~Kevin Lee Support Escalation Engineer | Microsoft System Center Configuration Manager Disclaimer: This posting is provided “AS IS” with no warranties and confers no rights.