Microsoft has unveiled a new update rollup 8.0.11030.0 for the Microsoft Monitoring Agent (MMA) that has fixed issues in the previous version of MMA. The fixes in this version includes below.
- Improved logging for HTTP connection issues
- Fix for high CPU utilization when you’re reading a Windows event that has an invalid message description
- Support for Azure US Government cloud
How to get update rollup version 8.0.11030.0 for Microsoft Monitoring Agent (KB3206063)?
This package is available as a manual download in the Microsoft Update Catalog. You can search for Microsoft Monitoring Agent and list down the available updates will appear in the search results.
Microsoft has published a new Hotfix 3208888 for those who are running SCVMM 2016 Update Rollup 1. This includes a fix for the issue where when you use VMM to live migrate a VM from one host that’s running one version of Windows Server 2016 to another host that’s running a different version of Windows Server 2016, the placement page assigns a zero rating to the target host.(i.e Datacenter edition to Standard edition). This issue happens only when you try to live migrate between two version of Windows Server 2016 but not when you are trying a live migration between hosts that are running 2012 R2 and 2016.
This leads to block the live migration with below error message:
Unable to migrate or clone the virtual machine VM_name because the version of virtualization software on the host does not match the version of virtual machine’s virtualization software on source version_number. To be migrated or cloned, the virtual machine must be stopped and should not contain any saved state.
Note the this is applicable only to those who are running SCVMM 2016 Update Rollup 1.
- Download the KB package from here.
- Use an elevated Command Prompt to install the KB manually.
msiexec.exe /update kb3208888_vmmserver_amd64.msp
In Operations Manager sometimes you may need to revert back to an older version of a Management Pack for a particular workload. The Operations Manager UI allows to delete and re-import MPs from the “Installed Management Packs” screen. The problem happenes when there are multiple and multi-level dependencies on the MP that you are trying to delete.
However now there is an enhanced version of a script available at TechNet (developed by MSFT employee Christopher Crammond) that will help you to revert Management Packs with a single command.
Using the Script
- Open the Operations Manager Command Shell prompt as an Administrator.
- Download the script to remove a management pack with dependencies from here.
- Execute the script as below.
.\RecursiveRemove.ps1 <ID or System Name of the MP>
- For an example if you want to remove the SQL 2014 Disocvery MP run the script as below.
How to get the the ID or System Name of an MP?
- Selecting the MP that you want to delete in the Installed Management Packs view by clicking Properties in the Actions pane.
- Copy the content in the “ID :” text box in the General tab.
If you have recently upgraded your datacentre infrastructure to Windows Server 2016 (or your client device to Windows 10) you can benefit from the latest Hyper-V features available on your virtual machines by upgrading their configuration version. Before you upgrade to the latest VM version make sure;
- Your Hyper-V host are running latest version of Windows or Windows Server and you have upgraded the cluster functional level.
- You are not going to move back the VMs to a Hyper-V host that is running a previous version of Windows or Windows Server.
The process is fairly simple and involves only four steps. First check the current VM configuration version.
- Run Windows PowerShell as an administrator.
- Run the Get-VM cmdlet as below and check the versions of Hyper-V VMs. Alternatively the configuration version can be obtained by selecting the virtual machine and looking at the Summary tab in Hyper-V Manager.
Get-VM * | Format-Table Name, Version
- Shutdown the VM.
- Select Action > Upgrade Configuration Version. If you don’t see this option for any VM that means that it’s already at the highest configuration version supported by that particular Hyper-V host.
If you prefer PowerShell you can run the below command to upgrade the configuration version.