Hi
We have implemented a new CMG to replace one in a Pay As You Go Subscription {the new CMG is on Enterprise Subscription]
CMD setup was all completed with no errors. All appears fine in SCCM and in Azure, logs show no errors.
Both CMG's are connected to SCCM on separate MPs using separate Cloud Management Gateway Connection Points
When I limit the search to the new CMG, i can see a few devices connected and they are showing they have completed policy request, heartbeat DDR, Hardware scans and software scans.
The problem is, after a short time they return to connected to the old CMG, they do not stay connected to the new CMG. when we turn off the old CMG after a short time ALL devices then show not connected. we left this for 36 hours without change. If we turn the existing CMG back on the devices connect back to this CMG. In the client I can see on some devices the new CMG stated in the network TAB, and in the registry they either show only the old CMG or some have both listed.
Has anyone seen this before?
Thanks