MECM Roaming Client can't talk to origin MP

Thorsten Hennig 1 Reputation point
2022-10-18T12:31:10.797+00:00

Hello there, I have a customer and we have some issues with the Config Manager Configuration. Here is the situation. We're using MECM Version 2107. We have a HQ and a few subsidiaries. In our HQ we have a CAS and a Primary site (ABC). In the subsidiaries. In each subsidiary there is a primary site. Every Site has an unique network configuration and the boundaries (network subnet) are not overlapping.
Each subsidiary hat a limited internet connection via sattelite with a VPN tunnel to the HQ. Sometime it takes some time but it works quite well so far.

The Problem:
Now there are some IT technicians in the HQ who need to be at a subsidiary for some time (3-4 weeks). The clients are not allowed to talk to the Management Point in the HQ because of the limited Internet connection. The Firewall blocks that. So the clients should load the updates and applications from the local Distribution Point and talk to the local Management Point.
But that isn't working.
In the LocationServices.log we can see that the client is trying to reach the Management Point in the HQ.
How can I make the roaming clients use the local MP?

best regards
Thorsten

Microsoft Configuration Manager
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Garth Jones 1,656 Reputation points MVP
    2022-10-18T12:50:18.753+00:00

    What you are looking for will never work. Client will NEVER change sites automatically. They will need to talk to the HQ MP and DP, as such you will need to leave those clients "as is" when they return to HQ they will update at that time.

    1 person found this answer helpful.
    0 comments No comments