Boot image x64 - error loading task sequence

[ZeZe]

Hi all

 

I just updated a SCCM server with the CU1 (for the R2 SP1). After the update, when I try to boot with a bootable media mounted, it looks all good. I click on next to view the task sequence and it fails. This was working until I patch with CU1.

 

From the SMSTS.log:

 

CryptVerifySignature (hHash, pSignature, dwSizeSignature, hKey, NULL, 0), HRESULT=80090006 (e:\nts_sccm_release\sms\framework\osdmessaging\libcrypt.cpp,642) TSMBootstrap 10.11.2015 23:53:54 1920 (0x0780)

CryptVerifySignature failed, 80090006 TSMBootstrap 10.11.2015 23:53:54 1920 (0x0780)

VerifySignedString (sAnsiCert.getBuffer(), m_sMPCertificateSignature.c_str(), szTrustedRootKey, 32780 ), HRESULT=80090006 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5387) TSMBootstrap 10.11.2015 23:53:54 1920 (0x0780)

untrusted certificate: 308202EF308201D7A00302010202103F2F58B02BD4A48046A24966EFD8A8C1300D06092A864886F70D01010B05003026311630140603550403130D4857494750565053434D303031310C300A06035504031303534D533020170D3135303631343231353530335A180F32313135303532323231353530335A3026311630140603550403130D4857494750565053434D303031310C300A06035504031303534D5330820122300D06092A864886F70D01010105000382010F003082010A02820101009D05AB2CF0FF2CF396D4421B7BB5200F28D74CED3F2165F0E8C008533ECD62630208DEDC707FEDE6B6F0664A51829BA6A412960996665BF6E9631903D17E60BA666C50EB1996E0A650B25A00AB09352A39C93ABA89C36951F88B92B01B0784179AEF6D740379323CE8B68E2D6B3EF18014EDDE4F8881958963A5EFA0DB578B1B02BCB64403786D8CB456C4BD2A0AC94CD87AD0AFC3EF786A2BF1B1338C75A323BC6427655BCBFEE503BD2FAD07DA6EAE95A5983B80C89C483315069B4BA34AB3BD8838CE6FB8CFDA0D67AC7C39EA650081470F8D81245425B7FA49C5720F6C3ABEE6969D998A326D2172E81C1F3D698450507A0B6D9E575D009F4412A07AB9610203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D01010B0500038201010066687B1227B20D12DD2F23F3C64E3D736A525898508F8A7FF936522C6885BB7271C86F1E4F491AD4B3B0C0DB35415D6E5550451509D35CFD93FFF5CA3317618BB99D05D2D39EE3E72650F2D1D6DF627469315E229A79918FD55013525771994C46402DF79B54B6F3F2A8320D3BAC2FBFCB951F54936AE1713E217CB7712440CC8097E06FE53D48988BC93F6BA75181AABC1B8409C38C27D816A1A377CFB968D15D648B902790C48C1131529951E5BA174D58DDD88B083C120D3DD221DCAC161C3B79A410DDC01154DCCA2437A346AE5EFC85398BE650762DA13F18167C0FE40C31711C7143E44D9BA233A5B245D27ED49FA313CF1BEA2A1BC684D26002D21D8C, , 0602000000A40000525341310008000001000100C781D94CA72A91BD0315C67676BA325A9C464D0AB180223BEF2E4F5AAAC426A4B7A7F5C22FB3CCB907F8C752681917679430CDBFD9427B956A6A776C3B20712C338D93A0DDF7970056C2D39569368502897CD0E267E559DBAE2788F80698AFFE20113DDF95798868EF728BC6AC7B515F34C21E94169D8EA78B0AD49FD00B5BF3F9CEC1DD9A42AFB484AC6782F35FD3892D080B4693DA560D2FC0799DE75DD07A93940C42210EF20C417AD991E4EF3AE80598C0ABCEE3963EC4897F4F69167A2585F94383B6D625BBAD988FBE9646B8235B3FD064E735A4D5D6A0E7AFF1936DBEE02F0F729B43224F165FC7EF389F09E25920281E85B03AB534B03DDF2DCC2EB1 TSMBootstrap 10.11.2015 23:53:54 1920 (0x0780)

MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80090006 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9584) TSMBootstrap 10.11.2015 23:53:54 1920 (0x0780)

Failed to get information for MP: http://SCM. 80090006. TSMBootstrap 10.11.2015 23:53:54 1920 (0x0780)

----

I have already look into the certificates and everything is "unblocked". I have created another bootable image from the task sequence media, with a long date on the certificate self-sign.

The error on the screen is this:

Any help will be very very appreciate!!

[ZeZe]

Hi to all,

 

https://social.technet.microsoft.com/Forums/en-US/c8e34057-41eb-4a8f-bf1d-979257da4fa6/untrusted-certificate-during-operating-system-deployment?forum=configmanagerosd

 

Does anyone had this issue before? Does anyone knows which values should be in these two keys?

HKLM\SOFTWARE\Microsoft\SMS\Security\[signedSerilizedKey]
HKLM\SOFTWARE\Microsoft\SMS\Security\[signedSerilizedKeyEx]

[ZeZe]

Hi evreyone!

 

Thanks for everyone support! haha

 

The solution my problem was...

 

1) removed the MP

2) reinstall MP

3) remove multicast from the DP

4) enable multicast again...

 

Here is the thing: after I finished all that, the error continue and the keys still were empty... I went to bed but before I go to sleep I went online again looking for answers. There was this case where a guy had the same issue as mine. This guy open a case on Microsoft and did what I had done already. And they wait like a few days.... and then.. puff, the problem was solved! Keys were with information needed and the OSD was running fine... so.... this morning I woke up and I check the keys and they were OK... OSD was fine too... SCCM is very slow, isn't?!?!?!?!!??!