Microsoft a publié un article sur son blog de support à propos d’un problème pouvant survenir lors du déploiement de système d’exploitation. Le démarrage PXE échoue si le Management Point est mode HTTPS alors que le point de distribution est en mode HTTP.
Vous pouvez observer les informations suivantes dans le fichier smspxe.log :
ProcessMessage: Context:0015B270 dTime:0 SMSPXE
!sTempString.empty(), HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\string.cpp,1023) SMSPXE
MAC=<MAC_Address> SMBIOS GUID=<SMBIOS_GUID> > DHCP Discover received. SMSPXE
Set enterpirse certificate in transport SMSPXE
Set media certificate in transport SMSPXE
Set authenticator in transport SMSPXE
CLibSMSMessageWinHttpTransport::Send: URL: <ConfigMgr_MP_Server>:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATION SMSPXE
In SSL, but with no client cert SMSPXE
Request was succesful. SMSPXE
Set authenticator in transport SMSPXE
Setting message signatures. SMSPXE
Setting the authenticator. SMSPXE
CLibSMSMessageWinHttpTransport::Send: URL: <ConfigMgr_MP_Server>:443 CCM_POST /ccm_system_AltAuth/request SMSPXE
In SSL, but with no client cert SMSPXE
Request was succesful. SMSPXE
pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1967) SMSPXE
reply has no message header marker SMSPXE
DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,6202) SMSPXE
SMSClientLookup.RequestLookup(smbiosGUID, macAddress, dwItemKey, bUnknown), HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\smspxe\database.cpp,221) SMSPXE
PXE::DB_LookupDevice failed; 0x80004005 SMSPXE
Set enterpirse certificate in transport SMSPXE
Set media certificate in transport SMSPXE
Set authenticator in transport SMSPXE
CLibSMSMessageWinHttpTransport::Send: URL: <ConfigMgr_MP_Server>:443 GET /SMS_MP_AltAuth/.sms_aut?MPKEYINFORMATION SMSPXE
In SSL, but with no client cert SMSPXE
Request was succesful. SMSPXE
Set authenticator in transport SMSPXE
Sending StatusMessage SMSPXE
Setting message signatures. SMSPXE
Setting the authenticator. SMSPXE
CLibSMSMessageWinHttpTransport::Send: URL: <ConfigMgr_MP_Server>:443 CCM_POST /ccm_system_AltAuth/request SMSPXE
In SSL, but with no client cert SMSPXE
Request was succesful. SMSPXE
pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1967) SMSPXE
reply has no message header marker SMSPXE
DoRequest (sReply, false), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,4045) SMSPXE
Failed to send status message (80004005) SMSPXE
smStatusMessage.Send(), HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\smspxe\database.cpp,444) SMSPXE
Failed to send the status message SMSPXE
PXE::DB_ReportStatus failed; 0x80004005 SMSPXE
GetOrCreateDeviceFromPacket(pRequest, deviceInfo, 1, 1), HRESULT=80004005 (e:\nts_sccm_release\sms\server\pxe\smspxe\pxehandler.cpp,1475) SMSPXE
PXE Provider failed to process message.
Unspecified error (Error: 80004005; Source: Windows) SMSPXE
Rejecting PXE request SMSPXE
Ce problème survient si un certificat auto-signé est utilisé dans les propriétés du point de distribution. Durant le démarrage PXE, les clients utilise ce certificat pour dialoguer avec le Management Point et le Distribution Point. Si le Management Point est en mode HTTPs, le client a besoin d’un certificat PKI pour parler au Management Point.
Pour résoudre le problème, vous devez spécifier un certificat de votre PKI au lieu d’un certificat auto-signé.
