Error while querying SCOM Gateway Server registry key

While looking at the screenshot you’ve sent us on the registry key with the problem, I could see a possible problem with the structure of your ‘Server Management Groups’ registry hive in:

 

 

@"SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Server Management Groups"

 

 

What you have there is:

 

 

\Server Management Groups

 

-----\QpayCorporate

 

----------\Send Priorities

 

-----\Send Priorities*

 

 

Apparently you have a ‘Send Priorites’ management group registry hive showing up at the same level with ‘QpayCorporate’ (I’ve noted it Send Priorities*). I don’t think this would be a valid registry key under the ‘Server Management Group’ hive. I checked all of the SCOM management groups in my test environment and I can’t find it directly under ‘Server Management Groups’. Is it possible that this registry hive got imported / created unintentionally here?

 

 

The problem is that, with the current F5 MP (v2.1.5.440) when we query the sub-keys under the ‘Server Management Groups’ registry hive, there’s no guarantee that we picked up the first entry, which is ‘QpayCorporate’ and where we would expect the IsGateway registry entry to show up. As a matter of fact the IsGateway should show up under each [valid] management group key, contained

 

under ‘Server Management Groups’. This being said, you have two options for directly working around this issue with your current version of the F5 MP:

 

 

1. Create a bogus IsGateway [DWORD] registry entry under the ‘Send Priorities’ registry key (the one at same level with QpayCorporate), and set the value to 0 (zero).

 

2. Temporarily remove the \Send Priorities registry hive (the one at same level with QpayCorporate) and run the setup.

 

 

Our upcoming release of the F5 MP will gracefully handle such scenarios.

 

 

Let me know if the workaround suggested is acceptable for you and if it’s

 

working.

 

 

Thank you.

 

Julian