Client can't find its Management point
Having a site configuration with several MP's, a few in untrusted forest can be a challenge. Especially combined with complex and firewall micro segmented network. We had an issues with clients, that couln't find the correct MP during OSD and application delployment. This resultet in time-out errors, causing the installation to fail. The locationservice.log showed that the agent tried the entire MP list. one by one until it finally came to one it was able to communicate with. We talked about setting a static reg key allowedMP like Annop also explains in his blog post below. https://www.anoopcnair.com/sccm-mp-rotation-issue-sup-rotation-fix/ Setting the AllowedMP will enforce an agent always to communicate with the the MP in the registry, but it will at the same time remove the flexibility build in the agent. So we decided a mixed solution. First step was to solve the timeout issue during OSD. Set allowedMP in the begining of the OSD TS Remove allowedMP at the ...