The pool managing the instance is not available or the location monitoring object cannot be found - discovery progress

Navigate to C:\Program Files\Microsoft System Center 2016\Operations Manager\Server

Open (as administrator) ConfigService.config

Edit the following lines, removing the \INSTANCENAME values so that only the SQL server value is shown.

     <Category Name="Cmdb">

        <Setting Name="ServerName" Value="jimmy\jimmy" />

        <Setting Name="DatabaseName" Value="OperationsManager" />

      <Category Name="ConfigStore">

        <Setting Name="ServerName" Value="jimmy\jimmy"  />

        <Setting Name="DatabaseName" Value="OperationsManager" />

To

     <Category Name="Cmdb">

        <Setting Name="ServerName" Value="jimmy" />

        <Setting Name="DatabaseName" Value="OperationsManager" />

      <Category Name="ConfigStore">

        <Setting Name="ServerName" Value="jimmy" />

        <Setting Name="DatabaseName" Value="OperationsManager" />

                   

Restart System Center Management Configuration and System Center Data Access Service.

Issue with SCOM agent in forest trust domain(0x80090311)

If you see these events 20057 with code (0x80090311), that is mean (trust is corrupted) and agents can not authenticate to MS.

The most common reason is Firewall issue.
(TCP/UDP 88 port (Kerberos) and TCP/UDP 389 port (LDAP)) should be open from Agent to Management Server DCs.

How to Use the Ping Command to Ping IPv4 or IPv6

Here’s a useful tidbit relating to ping on Windows: If you specify -4 or -6 after the IP address or hostname, you can ping either IPv4 or IPv6, respectively. For example:

To ping using IPv4:

  ping somehostname.com -4

To ping using IPv6:

  ping somehostname.com -6

Unable to install updates on server 2016 with error code : 0x800706d9

Cause

Firewall service 

Resolution

Service disabled set to automatic and the updates started installing 

Total CPU Utilization Percentage" is monitor not working as expected

Cause
======

CPU % and queue length are not above the threshold as per the properties of monitor

Resolution
=========

This is working as per the design.

We have the default monitor name : Total CPU Utilization Percentage.

We are dealing with two conditions here

1) Threshold CPU that is 95 % by default with number of samples collected is 3

2) Queue length which is 15 by default   

High CPU/High Memory in WSUS - Windows update will not download updates - stuck at 0% downloading

A WSUS update is now available that includes improvements for update metadata processing. This update should be applied to all WSUS servers in your environment.
Windows Server 2016 (KB4039396)
Windows Server 2012 R2 (KB4039871)
Windows Server 2012 (KB4039873)
WSUS 3.0 SP2 (KB4039929)

If you still occasionally experience thread abort exceptions, you can increase ASP.NET’s default timeout.
Increase the ASP.NET timeout

• Make a copy of \Program Files\Update Services\WebServices\ClientWebService\Web.Config.
• Open \Program Files\Update Services\WebServices\ClientWebService\Web.Config.
• Find the element “<httpRunTime”. It will look like this (in an unmodified web.config):

<httpRuntime maxRequestLength="4096" />

• Modify httpRunTime by adding an executionTimeout attribute:

<httpRuntime maxRequestLength="4096" executionTimeout="3600" />

• Save the web.config to a different location and copy the modified one into the directory.
• From an elevated command prompt, run IISReset to restart IIS

How to increase the timeout for Migration Jobs in System Center 2012 Virtual Machine Manager

To increase the timeout between jobs, follow the steps below:

1. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings

2. Create a new DWORD value

3. Set the name to be LiveMigrationQueueTimeoutSecs

4. Set the value to be 00000708 HEX. This will set the Timeout to 30 minutes and is a good place to start. 

5. Restart the VMM service