Thanks @CyrAz . I deleted the registry key for Kerberos authentication and was able to install and onboard the server in SCOM. Many Thanks

Hello Roger,

Thanks for your response.

I picked one agent server which was pointing to GW2 in the console. Flushed the cache and observed the event logs. I see one error which says it is trying to connect to GW1 but failing.

When i ran the PS command the output confirmed the Primary management server was GW2

Appreciate your kind assistance here @Crystal-MSFT - I still have to work on this MP and will keep you posted on the developments. This is indeed creating a lot of noise in the event logs

Hello @Crystal-MSFT .

Appreciate your response. Below is the result.

But i do have a MP which is logging massive amounts of errors in event log. It is related Azure Managed Instance. 16000 events in the last hour
Do you suggest removing this MP ?

@CyrilAzoulay Thanks for your response.

Yes. I did read that article. My config file has setting has the following values.

<Setting Name="SnapshotSyncManagedEntityBatchSize" Value="50000" />
<Setting Name="SnapshotSyncRelationshipBatchSize" Value="50000" />
<Setting Name="SnapshotSyncTypedManagedEntityBatchSize" Value="100000" />

I was wondering if it was right for me to reduce the values as suggested ? Can i proceed ?

Hello @CyrilAzoulay ,

The issue seems to be resolved. Though i did not make changes to the above parameters, i changed the timeout seconds in all the MS config file

The configservice.config file is located at C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server
Update the file with the values highlighted below:
Snapshot Synchronization:
<Operation Name="EndSnapshot" TimeoutSeconds="1800" />
Delta Synchronization:
<OperationTimeout DefaultTimeoutSeconds="300">
<Operation Name="GetEntityChangeDeltaList" TimeoutSeconds="300"

Earlier it was

<Operation Name="EndSnapshot" TimeoutSeconds="900" />
<Operation Name="GetEntityChangeDeltaList" TimeoutSeconds="30"

@Crystal-MSFT - Yes . That is right. Agents pointing to GW1 is healthy and GW2 is grayed out. Initially all servers were reporting to GW1 and they were healthy. After changing the GW reporting server for half of them to GW2 they turned grey. All the GW and MS are healthy. I have around 500 servers that are unhealthy. Any directions on how i can administer them to clear cache ?

It was all fine till i changed the configuration using the Kevin Holman link. (Please forgive me lack of understanding)

Initially all of the servers in B domain were reporting to GW1 server and it was all healthy. Once i moved half of the agents to GW2, the ones i moved to GW2 went unhealthy.

I assumed it was an issue with the Failover and the GW2 was configured to be failed over.

I used the link to configure the failover and now all the agents are grayed out :(

Initially when i checked for the primary Gateway.GetPrimaryManagementServer().DisplayName, it returned MS1.A.COM
the $Gateway.GetFailoverManagementServers().DisplayName did not return any results. Hence configured failover.

Is my configuration right in configuring failover ? Any way i can validate ? Can i in anyway reassign the primary MS to agents ?
Please advise

only the agents. The GW are healthy

@CyrilAzoulay

Thanks @CyrilAzoulay

Appreciate you taking time to check on this.

Do we have any working test cases or any work around to configure this monitoring ? Kindly advise.

Thanks @CyrilAzoulay . Generous as always :)

Hello @GuillaumeH , Thanks for checking.
the second servers used which has error is a red hat one.

Thanks @CyrilAzoulay - Appreciate

I checked the Universal Linux Monitoring MP version and it was a previous version
Current Version - 7.5.1005.0
Latest version - 7.6.1092
i imported the latest version in the lab and found the missing override for the discovery in the latest version.

---

On a lighter note, Can i not mark more than one answer as "Accept answer" : D

Hello @CyrilAzoulay ,

qq : To exclude multiple filesystem , should i used comma ? Please refer the screenshot and kindly advise

Hello Leon,

This is not the error when i import a MP. It's even before that. I do not get an option to upload. As soon as i click yes/no from the below window , this error appears.
I have tried import the MP using Powershell and it works as expected. Also, verified .net versions installed. Last time we had an issue with running fastseal and it came to our attention that by default only .net 4.7 will be installed in the core server. I have now installed 3.5 and still the same error.

We have also excluded the server from a GPO which prevents the application to use third party browsers.

No errors in System logs
Application logs have 2 errors

No errors in Ops Manager Log related to this