Microsoft has released the on-premises client Update Rollup 1 for Microsoft System Center Advisor. This update is dated May 22, 2012. This article describes the following information about the update:
The issues that the update resolves
How to obtain the update
The prerequisites to install the update
The System Center Advisor on-premises client version 1.1 and later versions are compatible with the Microsoft System Center 2012 Operations Manager suite. Version 1.1 and later versions add new monitoring workloads and fix several important issues.
This update introduces the following new features:
Support for System Center 2012 Operations Manager
You can use System Center Advisor on the same computer on which you are running the System Center 2012 version of the Operations Manager agent.
Analysis for Microsoft SQL Server 2012
Analysis for Microsoft SharePoint 2010 and later versions
Analysis for Microsoft Exchange Server 2010 and later versions
Additional Windows PowerShell cmdlets to support running System Center Advisor in environments that require action accounts or RunAs accounts.
For more information about System Center Advisor, go to the following Microsoft website:
The System Center Advisor agent stops collecting and uploading data for the monitored server. When this issue occurs, the System Center Operations Manager HealthService service stops responding and consumes lots of memory. Memory usage may exceed 1 gigabyte (GB). In this case, you may be unable to stop the HealthService service.
This issue occurs because a timer that checks for action account credentials is recycled incorrectly.
The System Center Operations Manager HealthService service shuts down itself after the Advisor Management Pack Update process is executed in certain scenarios.
The System Center Operations Manager HealthService service is stopped unexpectedly after Microsoft Update (MU) for System Center Advisor critical update version 1.0.2021.0 is installed.
The System Center Advisor configuration process does not register the System Center Advisor agent to the System Center Advisor cloud server.
This issue occurs because the Machine.xml file is locked.
You cannot uninstall the System Center Advisor agent.
This issue occurs because the PublicKeyToken request queues up. Therefore, the agent does not stop the System Center Operations Manager HealthService service successfully.
The removal of System Center Advisor Gateway does not clean up incoming firewall rules and URLs that are reserved by System Center Advisor.
System Center Advisor Gateway does not report its version until the Gateway service is restarted.
The following files are available for download from the Microsoft Download Center: Download the update for System Center Advisor package now. For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Note For more information about how to obtain the latest update for System Center Advisor, go to the following Microsoft website:
To apply this update, you must have a version of System Center Advisor in which the build number is 1911 or earlier installed on the computer. To download System Center Advisor, go to the following website: