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

What .net framework error is it? Click on details an provide details.

It doesn't appear to give a specific error

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.ConfigurationManagement.AdminConsole.SiteSystems.ManagementPointConnectionsControl.InitializePageControl()
   at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnInitialize()
   at Microsoft.ConfigurationManagement.AdminConsole.SmsPropertyPage.OnLoad(EventArgs e)
   at System.Windows.Forms.UserControl.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.ControlCollection.Add(Control value)
   at System.Windows.Forms.TabControl.ControlCollection.Add(Control value)
   at System.Windows.Forms.TabControl.TabPageCollection.Add(TabPage value)
   at Microsoft.EnterpriseManagement.ConsoleFramework.SheetFramework.AddTabs()
   at Microsoft.EnterpriseManagement.ConsoleFramework.SheetFramework.OnLoad(EventArgs e)
   at Microsoft.ConfigurationManagement.AdminConsole.DialogFramework.Forms.SmsPropertySheet.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************

Followed by lots of entries of the loaded dll's and finished off with

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Also, if I hit continue to let me go into to the "incorrect" properties, while I can change the options, I can't save them at all. "Apply" is greyed out.

Hello,

I can run the command successfully, so the problem may related to UI. First test if you can change settings via powershell command:

Set-CMManagementPoint

http://technet.microsoft.com/en-us/library/jj870921(v=sc.20).aspx

Then check if there is any valuable information in SmsAdminUI.log.

I'm able to reproduce the issue and I believe I've determined the root cause. I will get a bug filed on this internally so we can have it fixed in the next release of the PowerShell cmdlets.

In the short term, here's a workaround you can use:

$mp = get-cmmanagementpoint -SiteSystemServerName yourmanagementpointfqdn
$props = $mp.EmbeddedProperties
$ep = $mp.ConnectionManager.CreateEmbeddedObjectInstance("SMS_EmbeddedProperty")
$ep.PropertyName = "Authentication type"
$props.Remove("Authentication Type")
$props.Add("Authentication type", $ep)
$mp.EmbeddedProperties = $props
$mp.Put()

I also wanted to note that this should have no functional effect on the MP, it's only an issue with how it's presented by the UI.

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

Just checking in again... that "fix" script doesn't seem to do anything for me that I can see.

Hi Guys, this is also an issue for me, any word on a resolution?

Jeff

It's still an issue for me. I'm just going to manually re-install the MP to resolve this as I haven't seen any updates from Adam. Perhaps he's on leave.

the workaround is now officially stated in R2 CU4, but it's also not working for me.

Any news on that?

-Roland

We'll be installing CU4 in the next few days, but I've already manually re-installed the problem MP's so it's unlikely I'll be testing for this issue again any time soon.

If someone tests and confirms it is resolved in CU4 then I'll mark that as answered.

I think that issue may be in CU3 also, removing the MP and adding it with the cmdlet may show the same behavior.

Can you check that?

I noticed something else:

The difference between cmdlet and console are actually two properties.

one is updated with the workaround. the other is related to the Facing config. With the console there is one with value 1, with the cmdlet they are both 0, which must be wrong:

                            PropertyName = "MPInternetFacing";
                            Value = 0;
                            Value1 = "";
                            Value2 = "";
                        },
                        instance of SMS_EmbeddedProperty
                        {
                            PropertyName = "MPIntranetFacing";
                            Value = 0;
                            Value1 = "";
                            Value2 = "";

So, I've used set-cmmana... to set intranet to 1

Now, everything is exactly the same, compared to GUI output, except 1 (expected?) serialized number and it's still not working.

I'm just using the minimum parameters -sitecode and -SiteSystemServerName (everything is local)

should I use others also, because it doesn't let me add only "-ClientConnectionType intranet", throws an error.

-Roland

I think that issue may be in CU3 also,

Did you mean CU4?

no, meant CU3.

the CU4 article says something like not fixed yet, which let me assume is was there before also and not that the issue was introduced with CU4.

If you're now on CU3 you could then try it I meant

I'm not sure I understand what you are saying. As per my original post, we were already running CU3 when I found this issue.

alright, you confirm it's an issue with CU3 and CU4.

And it seems the workaround mentioned in CU4 (officially) isn't working.

The cmdlet is still broken and unusable, creating the issue in the console.

True?

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

It is mentioned as workaround. Weird if it doesn't work for both CUs or even all of them.

Was hoping for an answer from Adam also, but his blog is also not really active.

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 2 hours 23 minutes ago

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, but manually installing it via the GUI doesn't resolve the problem of creation via powershell.

I had hoped Adam would have reappeared with an update on this.

I will be installing SP1 soon on our DEV environment, so maybe I'll see if I can giveit another try.

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.

So did you Test this yet? I'm cleaning up old posts.

Testing this in my DEV environment with R2 SP1 CU1 seems to have resolved the issue. I don't get the error or the console crash anymore.

I'll be implementing R2SP1 into prod sometime in the next month or so and will check it again then, but this looks like it has been resolved now.

• Edited by Scott Williams - IP1 5 hours 0 minutes ago
• Marked as answer by Scott Williams - IP1 5 hours 0 minutes ago