Every time when there is a new extension for windows Intune a message window pops up when starting ConfigMgr administrative console saying that new extentionsfor Windows Intune is available. Unfortunately this was not the case when I was starting my ConfigMgr administrative console. I knew there was a new Intune extension available and still there was no the message window popping up. I couldnt find any errors, either in the administrative console nor in the log files. A quick search on the Internet gave me an idea. It was probably a certificate related problem. Quick look in the MMC console and I could see there was two SC_Online_Issuing certificate under Console Root->Certificates (Local Computer)->Personal->Certificates. I compered the certificate thumbprint id for both the registry key HKLM\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR\Thumbprint and the two SC_Online_Issuing certificates. I deleted one of the SC_Online_Issuing certificate that had the same thumbprint id as the HKLM\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR\Thumbprint registry key, so that there was only one SC_Online_Issuing certificate left . Then I updated the HKLM\SOFTWARE\Microsoft\SMS\SMS_DMP_CONNECTOR\Thumbprint registry key with the thumbprint id of the SC_Online_Issuing certificate, restarted the SMS Executive service, and the popup message Windows was there again, saying thet there was a new intune extension available.
0 Comments
A few days ago I have got a call from a customer who was having a problem with OSD at two sites, each with a distribution point with the PXE Option enabled. In the \\[Distribution_ Point_Server]\SMS_DP$\SMS\Logssmspxe.log log file a lot of “Failed to copy D:\RemoteInstall\SMSTempBootFiles\P01000D8\Windows\Boot\Fonts\segmono_boot.ttf to D:\RemoteInstall\Boot\Fonts\segmono_boot.ttf” and "InstallBootFilesFor Image failed. 0x80070003" error messages could be found. The error message "The system cannot find the path specified error 0x80070003" pointed me in the right direction. The “D:\RemoteInstall\SMSTempBootFiles\P01000D8\Windows” folder was missing on the distribution point. The solution was quick and easy. The missing folder had to be copied from a working DP and after the WDS service restart the DP was up and running again. |
Author
Write something about yourself. No need to be fancy, just an overview. Archives
November 2022
Categories
All
|