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

Programmatically remove a management pack with Dependencies

Programmatically remove a management pack with Dependencies

---

When a management pack is deleted from the administration pane UI, it can become very time consuming to recursively track down and delete all dependent management packs before deleting the originally intended management pack. You can use the following script to cascade delete a management pack and all its dependencies.
To run the script, follow these steps:

1. Open the Operations Manager Command Shell prompt in Administrator mode.
2. Run the attached script from the directory where you have saved it in the disk. For example:
   
   • .\RecursiveRemove.ps1 <ID or System Name of the MP>
   • .\RecursiveRemove.ps1 Microsoft.SQLServer.2014.Discovery
   Note You can see the ID or System Name of the MP that you want to uninstall by selecting it in Installed Management Packs view. Then click Properties in the Actions Pane. Then copy the content in ID: text box in General tab.

Copy

# The sample scripts are not supported under any Microsoft standard support 
# program or service. The sample scripts are provided AS IS without warranty 
# of any kind. Microsoft further disclaims all implied warranties including, 
# without limitation, any implied warranties of merchantability or of fitness
# for a particular purpose. The entire risk arising out of the use or 
# performance of the sample scripts and documentation remains with you. In no
# event shall Microsoft, its authors, or anyone else involved in the creation,
# production, or delivery of the scripts be liable for any damages whatsoever
# (including, without limitation, damages for loss of business profits,
# business interruption, loss of business information, or other pecuniary
# loss) arising out of the use of or inability to use the sample scripts or
# documentation, even if Microsoft has been advised of the possibility of 
# such damages.
#
#
# PowerShell script to automagically remove an MP and its dependencies.
#
# Original Author :      Christopher Crammond
# Modified By   :      Chandra Bose
# Date Created   : April 24th, 2012
# Date Modified  :  Januray 18th, 2016
#
# Version  :       0.0.2
#

# Needed for SCOM SDK
$ipProperties = [System.Net.NetworkInformation.IPGlobalProperties]::GetIPGlobalProperties()
$rootMS = "{0}.{1}" -f $ipProperties.HostName, $ipProperties.DomainName


#######################################################################
#
# Helper method that will remove the list of given Management Packs.
#
function RemoveMPsHelper 
{param($mpList)
  foreach ($mp in $mpList)
  {
 $recursiveListOfManagementPacksToRemove = Get-SCOMManagementPack -Name $mp.Name -Recurse
 if ($recursiveListOfManagementPacksToRemove.Count -gt 1)
 {
  Echo "`r`n"
  Echo "Following dependent management packs has to be deleted before deleting $($mp.Name)..."

  $recursiveListOfManagementPacksToRemove | format-table name
  RemoveMPsHelper $recursiveListOfManagementPacksToRemove
 }
 else
 {
  $mpPresent = Get-ManagementPack -Name $mp.Name
        $Error.Clear()
        if ($mpPresent -eq $null)
        {
            # If the MP wasn’t found, we skip the uninstallation of it.
            Echo "    $mp has already been uninstalled"
        }
  else
  {
   Echo "    * Uninstalling $mp "
   Uninstall-ManagementPack -managementpack $mp
  }
 }
  }
}

#######################################################################
#
# Remove 'all' of the JEE MPs as well as MPs that are dependent on them.
# The remove is done by finding the base MP (Microsoft.JEE.Library) and finding
# all MPs that depend on it.  This list will be presented to the user prompting
# if the user wants to continue and removing the list of presented MPs
#
function RemoveMPs
{param($mp)

  $listOfManagementPacksToRemove = Get-SCOMManagementPack -Name $mp -Recurse
  $listOfManagementPacksToRemove | format-table name

  $title = "Uninstall Management Packs"
  $message = "Do you want to uninstall the above $($listOfManagementPacksToRemove.Count) management packs and its dependent management packs"

  $yes = New-Object System.Management.Automation.Host.ChoiceDescription "&Yes", "Uninstall selected Management Packs."
  $no = New-Object System.Management.Automation.Host.ChoiceDescription "&No", "Do not remove Management Packs."
  $options = [System.Management.Automation.Host.ChoiceDescription[]]($yes, $no)

  $result = $host.ui.PromptForChoice($title, $message, $options, 0) 

  switch ($result)
  {
        0 {RemoveMPsHelper $listOfManagementPacksToRemove}
        1 {"Exiting without removing any management packs"}
  }
}

#######################################################################
# Begin Script functionality
#
if ($args.Count -ne 1)
{
  Echo "Improper command line arguments"
  Echo ""
  Echo "Specify a command line argument to either import or export MPs"
  exit 1
}
else
{
  $firstArg = $args[0]

  add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client";
  $cwd = get-location
  set-location "OperationsManagerMonitoring::";
  $mgConnection = new-managementGroupConnection -ConnectionString:$rootMS;

  RemoveMPs $firstArg

  set-location $cwd
  remove-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client";  
}

Note
If any other imported management packs depend on the management pack you are trying to remove, the Dependent Management Packs error message displays. You must remove the dependent management packs before you can continue. For https://technet.microsoft.com/en-us/library/hh230746(v=sc.12).aspx

How to checked how many connections established

[checked how many connections established]

netstat -nao | find /i "ESTAB" /c

SCOM 2016,Unable to resolve the user xxx associated with the user role. Error code 1332

Problem

===========
Unable to resolve the user xxx associated with the user role. Error code 1332

Cause

=========
Normally – when you have a trust with a remote account domain, and you want to add users from the rote domain to SCOM, things go perfectly.

However, if the user account in the remote domain uses a different UPN name than the SAM account name – the SCOM UI block’s it.

  

Solution

===========

Use SCOM PowerShell to add these users to the role:

$Role = Get-SCOMUserRole -Name "MSFT TEST"
$Role | Set-SCOMUserRole -User ($Role.Users + "MSFT\jimmytest")