Greetings,

We have an established ConfigMgr 2012 R2 CU3 environment with several Primaries and management points already active. These were all installed manually using the CM Console.

I am now trying to add additional Management Points using Powershell using the command:

Add-CMManagementPoint -enablessl -sitecode "ABC" -sitesystemservername "MPservername.domain.com" -allowdevice -clientconnectiontype internetandintranet -generatealert -verbose

• The PS completes without error, the MPSetup.log and MPControl.log indicate all is well once the setup completes
• The MP appears as a component under the Server when viewing in the console
• The IIS logs show clients communicating fine and the CM component Status monitor is all green with no errors showing in the status message
• A Get-CMManagementPoint returns fine showing all the same details as other working MP's

However if I try to view the properties of the Management Point from the console, the console will error

If I click Continue it will open the properties but they don't appear correctly. The "sitedatabase" tab is missing and the mobile device and generate alert boxes aren't selected. If I click Quit the then console crashes.

So everything appears to be working, except for being able to view the actual properties through the console.

• Edited by Scott Williams - IP1 Friday, November 28, 2014 6:06 AM

Thanks Adam,

Well that will certainly save me the effort of having to raise a support case :) As for functionality, yes I had already noticed everything appears to be working fine and that it was just a UI issue.

I tried running that work-around script on the Primary for this site and while it completed without error, it doesn't appear to have fixed anything. I still get the UI crash. Does it need some time to take effect?

Some additional info in case it's relevant: Hierarchy is a CAS with SMS Providers located on dedicated servers. Multiple Primary legs, each Primary is a site server only (no other roles) with local SMS Provider. In each Site there are multiple MP's each located on dedicated servers for the MP role.

• Edited by Scott Williams - IP1 Tuesday, December 02, 2014 12:13 AM

Yes, it is an issue with CU3. The workaround suggested by Adam did not work for me with CU3.

CU4 has just been released, but I can't test if it is fixed in CU4 at the moment. I haven't looked to see if it is mentioned as fixed or not so I don't know myself.

If you have tried with CU4 and found it is still a problem, then that leaves this as an open issue unless Adam or someone else from MSFT can suggest another fix.

• Edited by Scott Williams - IP1 Thursday, February 05, 2015 11:11 AM

Hi Guys

FYI

Installing Mp's using the cmdlet also broke client push in my environment.

Fix was to remove then readd MP using GUI.

Jeff

• Edited by Jeffery101 Tuesday, February 10, 2015 12:30 AM
• Proposed as answer by Garth JonesMVP, Moderator Saturday, June 20, 2015 2:27 PM
• Unproposed as answer by Scott Williams - IP1 Tuesday, June 23, 2015 5:24 AM

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

I haven't needed to (re)build an MP for a while now and haven't checked to see if this is fixed in SP1 or SP1-CU1. I'll test it when I'm back in the office next week and post an update.