In a large site, multiple Management Points assist in load-balancing traffic from multiple clients. They are also useful so that clients continue to receive their policy after Management Point failure. Howver this feature should be regarded as load-balancing rather than true High Availability.
This Technet Library article explains the limitations well:
Planning for High Availability with Configuration Manager
You can also configure the additional Management Point to use a database replica (rather than the site database) and this further reduces the CPU processing on the site database server. This is described here:
Configure Database Replicas for Management Points
ConfigMgr 2012 Management Points are only supported on Windows Server 2008 and upwards (see Supported Configurations)
Pre-requisites
For Windows Server 2012
Prior to Windows Server 2012
Add the computer account of the Primary Site server to be Local Administrator of the new Management Point server.
Management Point Installation
Navigate to Administration > Site Configuration.
Right click "Servers and Site Systems" and choose "Create Site System Server".
Enter the server name and choose your site code.
Select "Management Point".
Choose to use either the site database or a database replica (see above).
Click Next to install the Management Point.
Close the wizard.
The new site system appears in the console.
Verify the installation using the SITECOMP.log file.
See additions in Site Status.
See additional components.
Folder structure on new MP.
New objects published to Active Directory.
Hi Gerry,
ReplyDeleteI wanted to know what are pre-requisities for adding a distribution point on a remote server. What all features and ports configuration needs to be taken care of.
Appreciate if you reply soon.
Thanks in advance
Jose
Hi Gerry,
ReplyDeleteMy environment is a standalone Primary Site with 2 Management Points: 1 is on the Primary Site Server, the other is an MP/DP that's in an untrusted forest. The cross-forest MP is to be used for Internet-based client management. The issue I have is this message that's appeared in the SMS_MP_DEVICE_MANAGER Component Status ever since I attempted to install the DMZ MP... "Site Component Manager failed to add machine account *DMZ MP Servername* to the user group SMS_SiteSystemToSiteServerConnection_MP_*sitecode*, this must be done manually."
From what I understand, it's a requirement that each MP be in the SMS_SiteSystemToSiteServerConnection_MP local Group on the site server. But I see no way of adding my MP to that group because it's in an untrusted forest. I've googled this thoroughly and all I can determine is I need to get the DMZ MP into that group, but I don't see a path to doing that. Do you have any tips?
Thanks for any help you can give me.
Have a look at this guide. It works
Deletehttp://blogs.technet.com/b/neilp/archive/2012/08/24/cross-forest-support-in-configmgr-2012-part-3-deploying-site-server-site-systems-in-an-untrusted-forest.aspx
Hi Gerry:
DeleteI have the same scenario as the user before, I followed the article you specify but the poblem persist. I have is this message that's appeared in the SMS_MP_DEVICE_MANAGER Component Status indicating I must add machine MP account to the user group SMS_SiteSystemToSiteServerConnection_MP_*sitecode* on the site server. But the MP Machine is in an untrusted Domain.