Troubleshooting

Problem: Multicast during an SCCM 2012 R2 SP1 (1511 release) Task Sequence fails with error “Failed to get MCS key (Code 0x80004005)”. This error is found in the smsts.log log file on the (Windows 10 Enterprise x64 1511) client machine. SMSTS.log file contents CLibSMSMessageWinHttpTransport::Send: URL: SCCM01.CORP.DOMAIN.COM:443 CCM_POST /SMS_MCS_AltAuth/.sms_mcs?op=keyinfo ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290) In SSL, but with no client cert ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290) `Request was successful. ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,2054) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)reply has no message header marker ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,10358) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)oMcsRequest.GetMCSKey(mcsKeyInfoResponse), HRESULT=80004005 (e:\nts_sccm_release\sms\server\mcs\consumer\mcsisapiclient.cpp,429) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)Failed to get MCS key (Code 0x80004005) ApplyOperatingSystem 15-4-2016 9:02:57 656 (0x0290)ClientRequestToMCS::DoRequest failed. error = (0x80004005). ...

During an Operating System Deployment in SCCM 2012 R2, new notebook models crashed after installing the driver package. I couldn’t see the BSOD code because I wasn’t able to boot the computer in safe mode, but after taking some pictures with my phone of the BSOD screen, I found out that the error code was 0x0000007e. The next step: how are you going to troubleshoot 160 drivers that you deployed to those models with your new driver package? ...