A common request the SCCM product group has received is to provide a way to define management point affinity for a specific set of ConfigMgr Clients in a primary site.
Starting with ConfigMgr 2012 R2 cumulative update 3 (http://support.microsoft.com/kb/2994331) there is a new way to define management point affinity for clients.
However, there are some caveats in the way management point affinity works in cumulative update 3. You can set a client to use a specific management point(s) by setting a registry value. When this registry value exist, It will cause LocationServices to bypass switching to any management point(s) during a Location Services Rotation unless it’s defined in the registry value.
The downside to this approach is if the management point(s) the client is forced to use goes down you will have an unmanaged client until the management point(s) is back online or the registry value is deleted or changed.
This method should only be used for management point(s) in a primary site. Clients in a boundary group of a secondary site will still use the secondary sites management point as a proxy management point. This can be used to set the initial management point communication for clients to register with a management point at a primary site before it starts to use a secondary site’s management point as a proxy management point.
This method is only for management point selection. This does not apply to distribution points, software update points, Fallback Status Points, or any other site system roles.
This method only works for intranet clients and intranet management points.
This method can’t be used to defeat the HTTPS preference over HTTP management point(s).
Only management point(s) in the same primary site as the client can be used.
For more information and a free consult, please contact Henson Group at http://www.thehensongroup.com or 800-980-1130