ConfigMgr : Post PXE/Media Boot, 0x80004005

Had a strange issue reported via our support team today, a couple of builds failing once the PXE boot password had been entered with a 0x80004005 error. The SMSts.log showed the following:

{code lang:text showtitle:false lines:false hidden:false}pNext != NULL, HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,1972)    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
reply has no message header marker    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
DoRequest (sReply, true), HRESULT=80004005 (e:\qfe\nts\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
Failed to get client identity (80004005)    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1072)    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
failed to request for client    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
Exiting TSMediaWizardControl::GetPolicy.    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303)    TSPxe    10/06/2013 11:07:00    1364 (0x0554)
Setting wizard error: An error occurred while retrieving policy for this computer (0x80004005). For more information, contact your system administrator or helpdesk operator.    TSPxe    10/06/2013 11:07:00    1272 (0x04F8){/code}

Changing the time/date in the computers BIOS resolved this error – the date and time were both incorrect.

ConfigMgr : SP1 CU3 / Windows 2012 R2 / 8.1 Support

My stance on SCCM updates, following ConigMgr 2012 SP1’s initial release, is a cautious one to say the least.

Today we completed the updgrade of our ConfigMgr 2012 SP1 envronment to CU3, facilitating the following capabilities for Windows 8.1 and Server 2012 R2:

Fully appreciate ConfigMgr 2012 R2 is now out, give it 6 weeks and we’ll no doubt deploy – however CU3 at least gets the Surface Pro 2 trial moving forwards, and gives bretahing space for authenticode issues and the like!

In our multi-site (Primary/Secondary) environment the update installed without anyhickups – backups/offline-snapshot people, just to be sure!