SCCM OSD Error Socket Connect Failed 8007274d – Recently I came across an operating system deployment issue. In one of the remote sites the SCCM OSD failed with a rare error. I say this rare because I haven’t seen this issue before. Upon checking the smsts.log file revealed socket connect failed 8007274d. With the PKI in place, the communication between clients and DP’s was secured using HTTPS. The certificate imported on distribution point was valid.
The distribution point had the PKI certificate imported. In my previous posts on PKI, I had mentioned the importance of this certificate. The certificate authenticates DP to a HTTPS-enabled management point. This is just before the distribution point sends status messages. When the Enable PXE support for clients distribution point option is selected, the certificate is sent to computers that PXE boot. Therefore using this certificate they connect to a HTTPS-enabled management point during the OSD. In the smsts log file, i found the following lines.
socket ‘connect’ failed; 8007274d. sending with winhttp failed; 80072efd
However I was curious to find out what error 8007274d translates to. So here is something that I found.
Error 8007274d = No connection could be made because the target machine actively refused it.
Error 80072efd = A connection with the server could not be established
Here are the steps to fix the SCCM OSD error socket connect failed 8007274d.
- First of all login to the distribution point server. Run the mmc command, load the Add or Remove Snap-ins dialog box, select Certificates from the list and click Add. Select Computer account and in next step ensure Local computer is selected. In the console, expand Certificates (Local Computer), and then click Personal > Certificates. Ensure the correct certificates are in place.
- Next step, launch IIS Manager > right click Default web site and click Edit Bindings. Ensure HTTPS is listed along with HTTP. Edit HTTPS and select a valid certificate. Most of all check this post for exact steps.
- Finally perform an iisreset and try the OSD.
In conclusion if the above steps did not fix your issue or if something else worked, please mention it in comments.