Update rollup for Microsoft Monitoring Agent (KB 3165492)

Issues that are fixed in this update rollup

• Agent multi-homing
  
  The MMA agent now lets you send data from one server to multiple log analytics workspaces. Various teams in an organization can collect data from the same managed device. A maximum of four workspaces per agent is now supported, and both the 32-bit and 64-bit versions of the agent are supported.
  
  
• Reduced noise in the event log for transient communication errors
  
  Events in the Operations Manager log that are related to communications to Azure Log Analytics (OMS) have been improved to reduce noise.
  
  
• Improved error information during setup if the Agent clock is wrong
  
  When you connect to a Log Analytics workspace when you use Agent setup, a specific error message is now returned if the workspace key cannot be validated because of an incorrect server time.
  
  
• Removed automatically generated certificates from the default certificate store to prevent application compatibility errors
  
  Client certificates that are generated by the MMA agent are now created in a "Microsoft Monitoring Agent" certificate store instead of the default computer store. This prevents application compatibility issues with other applications on the server from trying to use MMA-owned certificates.
  
  
• Bookmarks for events for multi-homed agents are not honored on restart
  
  Fixed an issue that occurs if the agent has multiple management groups configured. After a restart only, the bookmarks for events from the first management group are honored. However, from the other management groups, events logged while the agent is stopped are skipped.
  
  
• The agent could take two minutes to start after a system restart
  
  Fixes an issue where the agent could take two minutes to start after a system restart .
  
  
• Improved performance of reading security audit logs
  
  Improves the reading performance of security audit events by disabling unused Object ID lookups.
  
  
• Renewal of certificate causes one-hour data stop
  
  Fixes an issue that occurs after renewal of the certificate that's used to authenticate to OMS. In this situation, data may not be sent for up to one hour.
  
  
• Certificate pinning
  
  In addition to the standard trust checks, an improved check that the TLS (such as HTTPS) certificates presented by OMS are issued only by the certification authority used by Microsoft services.
  

Breaking changes

As part of the change to support multiple workspaces, the agent scripting APIs related to OMS on the IManagementServiceConfiguration interface were removed and replaced with APIs that support multiple workspaces.

How to obtain and install this update rollup

Download information

Update packages for Microsoft Monitoring Agent are available from Microsoft Update or by manual download.

Microsoft Update

To obtain and install an update package from Microsoft Update, follow these steps on a computer that has an Operational Manager component installed:

1. Click Start and then click Control Panel.
2. In Control Panel, double-click Windows Update.
3. In the Windows Update window, click Check Online for updates from Microsoft Update.
4. Click Important updates are available.
5. Select the Update Rollup package and then click OK.
6. Click Install updates to install the update package.

Manual download of the update packages

To manually download the update package, go to the Microsoft Update Catalog, and search for "Microsoft Monitoring Agent." Available updates will appear in the search results. For example, this update package is listed as follows: