I'm an IT professional with over fourteen years of experience and since 2000 I've been working with Microsoft Infrastructure. I'm post-graduated in Computer Network and Telecommunications and Microsoft Certified Professional (MCP, MCSA Security, MCSE Security, MCTS, MCITP, MCT and MVP). I work as Technical Consultant mainly involved in Microsoft Security and System Center Configuration Manager solutions
I was awared MVP status by Microsoft in 2010 for System Centre Configuration Manager
Hi All,installing a sccm client today and got the following errors on the ccmsetup.log
o [CCMSETUP] AsyncCallback(): ----------------------------------------------------------------- o [CCMSETUP] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered o [CCMSETUP] : dwStatusInformationLength is 4 o [CCMSETUP] : *lpvStatusInformation is 0x9 o [CCMSETUP] : WINHTTP_CALLBACK_STATUS_FLAG_CERT_REV_FAILED is set o [CCMSETUP] : WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set o [CCMSETUP] AsyncCallback(): ----------------------------------------------------------------- o Failed to send HTTP request. (Error at WinHttpSendRequest: 12175) o DownloadFileByWinHTTP encountered an unrecoverable error. o Sending Fallback Status Point message, STATEID='308'. o State message with TopicType 800 and TopicId {F29C31A1-173D-4DAC-88C4-D3C51F936655} has been sent to the FSP At this point, as good sccm admin as I am, used the trace32 error lookup and found that 12175 means: "A security error occurred"As this message is really good, searched over the internet and found the the MSDN have a more usefull message at http://msdn.microsoft.com/en-us/library/aa383770(VS.85).aspx One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server. To determine what type of error was encountered, check for a WINHTTP_CALLBACK_STATUS_SECURE_FAILURE notification in a status callback function. For more information, see WINHTTP_STATUS_CALLBACK.At this point, i'm pretty sure that there is a problem with SSL as I'm installing a native mode client (I haven't seen this issue in a mixed mode). As it wasn't clear yet, I asked help from network/firewall guys and found that the client was in a NAT network...as this is not supported (http://technet.microsoft.com/en-us/library/dd547071.aspx, see network adapter), we changed to be a routed network and voilà, client installed :)