SCCM 2012 - SMSPXE Error

I write this to help all you technical warriors out there who get shitty advice from the Microsoft Forums and other profound idiots about the 0x80092002 error in SCCM - usually to do with PXE booting but can manifest in other ways around DP -> MP communications.

The tricky one about this error is that it happens even if you are only using HTTP communication and not HTTPS/TLS. So to get an error about certificates is somewhat confusing.

What the uneducated masses of the internet will tell you is to re-install the PXE role over an over. This will do nothing.

Then they will tell you to re-install your management point and effectively re-build your entire infrastructure. This will work, but only because it is the nuclear option and will run the step that actually makes a difference as a matter of course.

So, here it is folks. If you have these kinds of errors in your logs:

PXE::MP_InitializeTransport failed; 0x80092002 SMSPXE 22/03/2017 2:45:58 PM 4144 (0x1030)

PXE::MP_ReportStatus failed; 0x80092002 SMSPXE 22/03/2017 2:45:58 PM 4144 (0x1030)

PXE::CPolicyProvider::InitializeMPConnection failed; 0x80092002 SMSPXE 22/03/2017 2:45:58 PM 4144 (0x1030)

All you need to do is re-generate your distribution point certificates in the ConfigMgr console.

To do this, go to your Distribution Point properties, and on the general tab, just change the date by a day.

This will fire off a job and in a few minutes a new cert will be created and you will be right to go.

Remember, the error is generated by the Windows crypto libraries - it's not an SCCM specific error. In this case, error 0x80092002 means CRYPT_E_BAD_ENCODE (https://msdn.microsoft.com/en-us/library/windows/desktop/dd542646(v=vs.85).aspx) which makes for an easy and obvious place to start searching.

Remember kids, if you don't understand how Windows actually works, wildly clicking around won't help - nor will posting dumb and incorrect solutions on the Internet.