Snoop78 Posted September 23, 2014 Report post Posted September 23, 2014 Thank you in advance. We have quite a complexed setup of SCCM 2012 R2 and due to the complexities it has some tricky hurdles to get over. We have a centrally managed environment that we then manage external domains from, but we are not able to get a domain trust in place and limited on the ports allowed through each clients firewalls etc, due to this we are not able to put in a secondary site (which would probably fix most things) but have to go with a management point on a server within the external domain. The issue we are having which is apparently a feature is that our clients are taking a round robin approach to find a management point but as you can imagine the only management point they can actually see / communicate with is the one in their domain. Does anyone know a way we can lock the clients to only communicate with the Management Point in their domain and not to try any of the others. Current Workaround: On clients that are not finally coming good we are having to put all the management points FQDN's into the Host file but all pointing at the IP of the local domain management point. As you can imagine this is not sustainable in the long term nor desirable. If there is a way to lock the clients to only want to communicate with their local Management Point I would love to know what it is Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted September 24, 2014 Report post Posted September 24, 2014 have you looked at locationaware from rob marshall ? http://www.smsmarshall.com/Pages/LocationAware.aspx secondly, the recently released CU3 has some MP features added, http://blogs.technet.com/b/jchalfant/archive/2014/09/22/management-point-affinity-added-in-configmgr-2012-r2-cu3.aspx Quote Share this post Link to post Share on other sites More sharing options...
Snoop78 Posted September 24, 2014 Report post Posted September 24, 2014 I will check these out, thank you. I will let you know how we go resolving this. I have just looked and we are only running CU1, going to look into the CU3 and the process to update it. Quote Share this post Link to post Share on other sites More sharing options...
Snoop78 Posted October 8, 2014 Report post Posted October 8, 2014 Upgrade has been done, we are having issues with the "Configuration Manager Client Package" not getting to the Distribution Points and the Source Version in the Packages window climbing in number. Found an article with what appears to be the same symptoms http://www.windows-noob.com/forums/index.php?/topic/9410-configuration-manager-client-package-keeps-updating/ We are reluctant to go diving into the SQL Database to fix though. Once we have this resolved we will be able to start upgrading the clients and determine if the CU3 has fixed all our issues. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted October 8, 2014 Report post Posted October 8, 2014 You should be reluctant to dive into SQL to fix stuff. In that case I would advise you to do the same as the guy from that article, create a CSS call and let MS fix it. That the only supported road for a SQL edit. About your initial question, if you're looking for only specific set of client that need to be "locked" to specific MP(s), you can also look at this for a static solution: http://www.petervanderwoude.nl/post/set-the-allowed-management-points-via-a-configuration-item-in-configmgr-2012/ Quote Share this post Link to post Share on other sites More sharing options...
Snoop78 Posted October 13, 2014 Report post Posted October 13, 2014 Still waiting for the Microsoft Support call to be created. In the mean time we have created our own package for the Client push and we deployed it today to some dev servers and added the registry entry into the servers via existing SCCM GPO. So far it appears to have resolved our issues and we are progressing to a production environment with the GPO and the Client upgrade. Thanks to all that have assisted with this issue and hope this helps others with similar issues. Quote Share this post Link to post Share on other sites More sharing options...
