none
Task sequence stops after "Setup Windows and Configuration Manager" with SCCM 1906 RRS feed

  • Question

  • Hi,

    i have upgraded to SCCM CB 1906 and installed quite afew Systems but it suddenly stopped working when the Certificate wasn´t valid anymore, so i fixed it at the "default Website", WSUS and within SCCM i selected the appropriate Certificate.

    Then i started OSD, the OS is deploying fine, till it reaches the Configuration MAnager Client.It is beeing installed but afterwards it shows a black screen for some time and then goes to the login screen.

    SMSTS Log shows:

    C:\windows\ccm\logs\smsts.log

    CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: SCCM.some.domain:443  CCM_POST /ccm_system_AltAuth/request	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    SSL, using authenticator in request.	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    In SSL, but with no client cert.	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Request was successful.	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set a global environment variable _SMSTSLastActionRetCode=0	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set a global environment variable _SMSTSLastActionName=Setup Windows and Configuration Manager	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set a global environment variable _SMSTSLastActionSucceeded=true	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Expand a string: %_SMSTSMDataPath%\Logs	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Clear local default environment	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    The action (Setup Windows and Configuration Manager) requested a retry	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Reboot to local harddisk	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    _OSDGinaIsConfigured variable set to TRUE	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    _SMSTSServiceStartType variable set to 	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Created volatile registry entry for pending reboot initiated by this task sequence	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Command line for extension .exe is "%1" %*	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set command line: "bcdedit.exe"	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Executing command line: "bcdedit.exe" with options (0, 0)	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Process completed with exit code 0	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Calling RebootSystem()	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    TSUEFIDrive: 	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    OSD type of task sequence. Ignore the service window setting	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Updated security on object S:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Updated security on object C:\_SMSTaskSequence.	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set a global environment variable _SMSTSNextInstructionPointer=42	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set a Task Sequence execution environment variable _SMSTSNextInstructionPointer=42	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set a global environment variable _SMSTSInstructionStackString=41	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Set a Task Sequence execution environment variable _SMSTSInstructionStackString=41	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Save the current environment block	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    Expand a string: %_SMSTSMDataPath%\Logs	TSManager	13.09.2019 19:40:14	2604 (0x0A2C)
    ==============================[ OSDSetupHook.exe ]==============================	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Logging successfully initialized to C:\_SMSTaskSequence\Logs	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Running module version 5.0.8853.1000 from location 'C:\WINDOWS\system32\OSDSETUPHOOK.EXE'	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Clients is joined to a domain.	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Command line for extension .exe is "%1" %*	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Set command line: C:\WINDOWS\system32\net.exe start W32Time	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Executing command line: C:\WINDOWS\system32\net.exe start W32Time with options (0, 0)	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Process completed with exit code 2	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Command line for extension .exe is "%1" %*	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Set command line: C:\WINDOWS\system32\w32tm.exe /resync	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Executing command line: C:\WINDOWS\system32\w32tm.exe /resync with options (0, 0)	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Process completed with exit code 2147943462	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Successfully synchronized time with AD.	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Executing task sequence	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}	OSDSetupHook	13.09.2019 19:46:13	1596 (0x063C)
    Reading logging settings from Task Sequence environment to set Task Sequence logging.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Setting LogEnabled to 1	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Setting LogMaxSize to 5242880	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Setting LogMaxHistory to 3	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Setting LogLevel to 0	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Setting LogDebug to 1	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Saving existing desktop wallpaper settings.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Setting desktop wallpaper.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Configuring local administrator account	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Enabling local administrator account	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Account was already enabled	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Re-assign all drive letters...	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    bIsMBR, HRESULT=00000000 (..\diskutils.cpp,2048)	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    This program is not running on MBR disk. No need to re-assgin driver letters.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Installing SMS client	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Setting variable to indicate client installation attempted	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Clearing existing client configuration.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Cleaning existing client certificates from SMS certificate store	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Restoring SMS client identity.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    The client certificates were not found in the environment. New certificates will be generated.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Successfully restored the client identity.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Using CRL: 	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Importing certificates to root store	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Added certificate to store or replaced matching certificate in store.	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Succeeded loading resource DLL 'C:\WINDOWS\system32\_SMSOSDSetup\1033\TSRES.DLL'	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Command line for extension .exe is "%1" %*	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Set command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Register:WinPE with options (0, 0)	OSDSetupHook	13.09.2019 19:46:14	1596 (0x063C)
    ==========[ TsProgressUI started in process 3644 ]==========	TsProgressUI	13.09.2019 19:46:15	3648 (0x0E40)
    Registering COM classes	TsProgressUI	13.09.2019 19:46:15	3648 (0x0E40)
    sbModulePath = C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe	TsProgressUI	13.09.2019 19:46:15	3648 (0x0E40)
    Shutdown complete.	TsProgressUI	13.09.2019 19:46:16	3648 (0x0E40)
    Process completed with exit code 0	OSDSetupHook	13.09.2019 19:46:16	1596 (0x063C)
    Successfully registered Task Sequence Progress UI.	OSDSetupHook	13.09.2019 19:46:16	1596 (0x063C)
    Executing C:\_SMSTaskSequence\OSD\PS100003\ccmsetup.exe /useronly /source:C:\_SMSTaskSequence\OSD\PS100003 /config:MobileClient.TCF /status:848	OSDSetupHook	13.09.2019 19:46:16	1596 (0x063C)
    Command line for extension .exe is "%1" %*	OSDSetupHook	13.09.2019 19:46:16	1596 (0x063C)
    Set command line: "C:\_SMSTaskSequence\OSD\PS100003\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PS100003 /config:MobileClient.TCF /status:848	OSDSetupHook	13.09.2019 19:46:16	1596 (0x063C)
    Executing command line: "C:\_SMSTaskSequence\OSD\PS100003\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PS100003 /config:MobileClient.TCF /status:848 with options (0, 0)	OSDSetupHook	13.09.2019 19:46:16	1596 (0x063C)
    Process completed with exit code 0	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Install succeeded. Blocking other instances of ccmsetup.	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Creating ccmsetup mutex.	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Installed Client	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Backing up current global client logging settings that are read from registry	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Overwrote client global logging setting in registry with OSD logging settings.	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Start to cleanup Task Sequence policy	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Task Sequence Manager deleted 0 instances	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Task Sequence Policy cleanup done	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    End Task Sequence policy cleanup	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Setting variable to indicate a client installation was done	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Registering the task sequence with the execution manager in the newly installed operating system.	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Active request handle is empty, registering with new active request handle. This is expected if the Task Sequence was started from a media/PXE.	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    Saving the new active request handle for the task sequence: {348D1A1A-324C-473A-8456-FD65AE8490DC}	OSDSetupHook	13.09.2019 19:48:31	1596 (0x063C)
    CoCreateInstance succeeded	OSDSetupHook	13.09.2019 19:48:33	1596 (0x063C)
    Succesfully registered the task sequence with the execution manager	OSDSetupHook	13.09.2019 19:48:50	1596 (0x063C)
    Command line for extension .exe is "%1" %*	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Set command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Executing command line: "C:\WINDOWS\system32\_SMSOSDSetup\TsProgressUI.exe" /Unregister with options (0, 0)	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    ==========[ TsProgressUI started in process 5040 ]==========	TsProgressUI	13.09.2019 19:48:51	5044 (0x13B4)
    Unregistering COM classes	TsProgressUI	13.09.2019 19:48:51	5044 (0x13B4)
    Shutdown complete.	TsProgressUI	13.09.2019 19:48:51	5044 (0x13B4)
    Process completed with exit code 0	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Successfully unregistered Task Sequence Progress UI.	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Moving logs to SMS client directory	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    LOGGING: Resetting log path.	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Successfully moved logs to SMS client log directory: C:\WINDOWS\CCM\Logs\SMSTSLog	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Executing task sequence manager bootstrap	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Get install directory for SMS client	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Update reboot count	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Launch C:\WINDOWS\CCM\TSMBootstrap.exe /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:1	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Command line for extension .exe is "%1" %*	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Set command line: "C:\WINDOWS\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:1	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Executing command line: "C:\WINDOWS\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:1 with options (1, 1)	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    ==============================[ TSMBootStrap.exe ]==============================	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Command line: "C:\WINDOWS\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:1	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Current OS version is 10.0.14393.0	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Logging successfully initialized.	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Resuming Task Sequence in Full OS	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Starting tsmbootstrap.exe version 5.0.8853.1000 from location 'C:\WINDOWS\CCM\TSMBootstrap.exe'	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    TS environment is not initialized	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Failed to set TS logging read from TS environment	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    We are going in OOBE and potentially need to set the authenticator in SSL	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    setting the authenticator	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Pass DP auth token and super peer token(if available) to the client framework in provisioning mode	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    setting the DP auth token 	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Failed to set DP auth token in registry	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Failed to resume task sequence (0x800703E6).	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Error to resume task seqauence.	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Exiting with return code 0x800703E6	TSMBootstrap	13.09.2019 19:48:51	5064 (0x13C8)
    Process completed with exit code 2147943398	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Task sequence completed 0x800703E6	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Restoring original desktop wallpaper.	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Resume SCCM Client.	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    CCMExec service startup type is set to enabled	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Modifying CCMExec Service to auto start.	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    CCMExec Service started	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Waiting for CcmExec service to be fully operational	OSDSetupHook	13.09.2019 19:48:51	1596 (0x063C)
    Failed to verify existence of file 'C:\WINDOWS\system32\0409\TSRES.DLL', error = 2	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    Trying base path for resource file	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    Failed to verify existence of file 'C:\WINDOWS\system32\TSRES.DLL', error = 2	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    Failed to find resource file 'TSRES.DLL'	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    0, HRESULT=80070002 (..\util.cpp,823)	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    FindResourceFile( pszBasePath, pszDllName, sDllPath, uLangID, bTryBasePathWithNoLanguage ), HRESULT=80070002 (..\util.cpp,957)	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    Failed to load resource file TSRES.DLL. 
    The operation completed successfully. (Error: 00000000; Source: Windows)	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    TS::Utility::LoadResourceDLL(sBasePath, phResourceModule, bUseEnvironment), HRESULT=80070002 (..\resourceutils.cpp,85)	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    Failed to create an instance of COM progress UI object. Error code 0x80040154	OSDSetupHook	13.09.2019 19:48:52	1596 (0x063C)
    CcmExec service is up 

    * Updated Bootimages

    * Created new TaskSequence & deployed it

    * redeployed the old task sequence.

    Currently i´m stuck.

    OS is 2016 Standard + August 2019 CU

    ADK Version 1903




    Saturday, September 14, 2019 11:04 AM

Answers

  • Finally solved it. But I didn´t find it in any logs, more or less checked everything.
    Funny thing is if you´d take the Client-Cert used for OSD and import it to ie and test https://<ServerName.FQND>/sms_mp/.sms_aut?mplist
    it works. no issues. nothing...

    Somehow the certificate template was set to 4096bits, but sccm only allows 2048 bits...

    https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements

    Tuesday, September 17, 2019 8:37 PM

All replies

  • Hi,

    0x800703E6 usually caused by corrupted registry keys, corrupted or missing DLL files, obsolete drivers, Windows update errors, missing or corrupted system files, or by viruses, Trojans or other destructive programs.

    Does this error only happened on this machine?

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, September 16, 2019 8:40 AM
  • Hi,

    i have 4 systems with which i can test, all diffrent models. i recreated the driver-package from scratch since i had an error after redistributing(they weren´t distributed anymore)

    tried it afterwards. will investigate a bit more tomorrow.

    the wim wasn´t modified, it worked fine since CU 2019-08

    Monday, September 16, 2019 2:57 PM
  • What type of wim are you using is it a captured image or a standard wim file being used in a Hybrid Task Sequence?
    But see how far you get on some other machine tests and we can look at the logs.

    Website: www.walshamsolutions.com Technical Blog: https://www.walshamsolutions.com/technical-blog Personal Blog: https://www.walshamsolutions.com/personal-blog Twitter: Dwalshampro

    Monday, September 16, 2019 3:07 PM
  • I have extracted Index 2+4 from 2016 iso and serviced them to the 2019-08 CU, The WIM should´t be an issue. as it worked for a few weeks

    The only thing i can say for sure, the Certificate of the SCCM was renewed and after the cert was replaced in "default Website", WSUS and within the SCCM console the issue appeared.

    The Cert is from an internal CA 4096 bit, Server and Client Auth.

    The 4 Systems are of diffrent hardwaretypes and all have the same issue.


    Monday, September 16, 2019 3:53 PM
  • Finally solved it. But I didn´t find it in any logs, more or less checked everything.
    Funny thing is if you´d take the Client-Cert used for OSD and import it to ie and test https://<ServerName.FQND>/sms_mp/.sms_aut?mplist
    it works. no issues. nothing...

    Somehow the certificate template was set to 4096bits, but sccm only allows 2048 bits...

    https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements

    Tuesday, September 17, 2019 8:37 PM
  • We're experiencing the same issue, albeit only with Windows 7 x86 Task Sequences (Build & Capture, Deployment), that were working fine prior to the SCCM 1906 upgrade.

    Same error in the logs also, will post them tomorrow, as am at home at the moment.

    Tried a base WIM from an unaltered Win 7 x86 DVD, a fully offline serviced WIM (2019-09) and the previous OS deployment WIM that was working prior to the SCCM 1906 upgrade.

    We've also tried both Boot Images 5.00.8790.1025 / 5.00.8692.1008.

    Other Task Sequences are working fine and to date we've tried the following:

    Win Server 2016, Win 7 x64, Win 10 1903 x64, Win 10 1803 x64

    Have also tried repairing Config Manager after install during the Task Sequence, placing reboots, pauses, etc... Sometimes it continues through our Task Sequence a bit further and then after a reboot further down the line, stops and just goes to the login screen.

    Our ADK, WinPE etc are also fully up to date. ADK/WINPE 10.1.18362.1

    As we're in the middle of a Win 10 migration it's not too big an issue, although we have a couple of applications that do not function on Win 10, or 64-bit architecture and the supplier is either no longer in business, or they cannot provide an upgrade, but it is still concerning.


    • Edited by CPR_ Tuesday, September 17, 2019 9:10 PM Formatting
    Tuesday, September 17, 2019 9:06 PM
  • Did you find any solution around this?

    We are facing the exact same issue after upgrading to SCCM 1906.

    Friday, September 20, 2019 10:48 AM
  • If all Images are affected check for cert issues Nevertheless check smsts.log on c:\_tasksequences C:\windows\ccm\logs
    Friday, September 20, 2019 11:10 AM
  • Error code 0x800703E6.

    As mentioned above in the post:

    

    Friday, September 20, 2019 3:05 PM
  • Maybe check your boundaries.
    Friday, September 20, 2019 4:08 PM
  • If you redistributed drivers check is they are really available
    Friday, September 20, 2019 4:17 PM
  • Boundaries are configured well. As I said, Issue is only when we are using SCCM 1906 SCCM client. As soon as we replace it with SCCM 1902 client, there is no issue at all,
    Monday, September 23, 2019 8:53 AM
  • Drivers are there.
    Monday, September 23, 2019 8:53 AM
  • Can you Post an smsts.log I would suggest replacing Domain and servernames. Currently i‘m on holiday, so i have only a mobile to read. But it definetly works with 1902. Did you update the bootimages?
    Monday, September 23, 2019 9:09 AM
  • Boundaries are configured well. As I said, Issue is only when we are using SCCM 1906 SCCM client. As soon as we replace it with SCCM 1902 client, there is no issue at all,

    I'm experiencing exactly the same issue.

    When I'm using the 1906 SCCM client in the task sequence on Windows 7 (x86) machines, the task sequence stops after "Setup Windows and ConfigMgr"

    All works fine with the 1902 client...

    Also, on Windows 10 machines, I don't have a problem with the 1906 SCCM client.

    Monday, September 23, 2019 9:25 AM
  • Ok Since its only win7 i guess you have Not integrated sha-2 Patch. https://support.microsoft.com/de-de/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus Its Necessary for sccm 1906 https://support.microsoft.com/de-de/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus
    Monday, September 23, 2019 9:31 AM
  • https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1906
    Monday, September 23, 2019 9:33 AM
  • SHA-2 related patches are already injected to the WIM. Also latest September month patches are also part of the WIM:

    Monday, September 23, 2019 10:37 AM
  • Have you tried accessing https://<ServerName.FQND>/sms_mp/.sms_aut?mplist. Or http://<ServerName.FQND>/sms_mp/.sms_aut?mplist Depending on your settings When using https add Client cert to Browser
    Monday, September 23, 2019 4:32 PM
  • Did you find a solution?
    Sunday, September 29, 2019 7:01 AM
  • The only solution for me, was to use an older SCCM Configuration Manager client package.

    Still looking for a solution where I can just use the latest package (which works for Windows 10)

    Monday, September 30, 2019 6:27 AM
  • That's the only workaround we are using as well. We have to use old SCCM client to make it work with Win7 32 Bit.

    Tuesday, October 1, 2019 9:34 AM