August 01
Microsoft Operations Manager 2005 Service Pack 1 ready for download!
Finally! The Microsoft Operations Manager 2005 Service Pack 1 is ready for
download. I was waiting for this Service Pack a long time and now it's finally ready. Hopefully this solves the issues I've had with the XIAN network manager from
Jalasoft.
MOM 2005 Service Pack 1 includes:
- Broader OS and database support including Windows Server 2003 SP1 and SQL
2000 SP4 which enables customers to leverage the latest Windows Server
System software.
- Support for x64 platforms which allows MOM 2005 to run on and monitor the
latest high performance hardware.
- License usage alerting which enables customers to receive alerts when
product usage exceeds their configured threshold of licensed OMLs.
Many customer-requested enhancements to better support enterprise scenarios:
- Support for disjoint namespaces with mutual authentication
- Support for NETBIOS names containing dot
- Improve robustness of heart beating and MCF
MOM 2005 SP1 Fixes
| Knowledge Base Number |
Title |
| 883925 |
The W3wp.exe process causes 100% CPU utilization on Management Servers in MOM 2005. |
| 885416 |
MOM 2005 agent logs an "existing connection was forcibly closed by the remote host" event. |
| 885839 |
The MOM 2005 Administrator Console crashes if you try to expand the the "Exchange 2000" rule group node in the Microsoft Operations Manager (MOM) 2005 Administrator console. |
| 885841 |
When you import a Management Pack in Microsoft Operations Manager MOM 2005, you may lose information that is contained in other Management Packs that reside in the same rule group. |
| 887180 |
A MOM 2000 SP1 hotfix (830595) introduces an unacceptable memory leak on Windows Server 2003 DCAM. |
| 888304 |
You receive a "Column 'IdComputer' does not belong to table" error message or a "Column 'IdTargetClass' does not belong to table" error message when you change regional and language options from English to Turkish on a computer that is running MOM 2005. |
| 889017 |
You receive an exception error when the MCF tries to insert alerts in MOM 2005, or event ID 10042 is written to the Application log when you use the MMPC. |
| 889071 |
Microsoft Operations Manager 2005 agent alerts are not processed when the Ignore Missing Heartbeats option is enabled. |
| 889187 |
MOM 2005 does not support NetBIOS domain names containing a period (.). The computer group is blank on any MOM agent (include the MOM server), and the attributes discovery seems not working. |
| 890948 |
"Generic failure" error message when you run a custom script that uses the UpdateContactTime method of the MSFT_Computer WMI class in Microsoft Operations Manager 2005. |
| 891200 |
The Operator Console State view shows a critical computer that has no alerts |
| 891641 |
The GetParentRuleGroup method does not return the correct rule group objects in Microsoft Operations Manager 2005. |
| 891709 |
The Microsoft Operations Manager Web console stops responding if the user belongs to many Active Directory user groups. |
| 892096 |
In a multiple tier deployment that uses MOM and HP Openview, the regional update to the alert occurs before the HP Openview reads the alert. As a result, the resolution state is overwritten and the alert is not forwarded. |
| 892140 |
Alerts that are in an inactive state on a source Microsoft Operations Manager 2005 Management Server appear as active on the destination Management Server. |
| 892307 |
The Application Log Provider may unexpectedly quit, and event 25257 is logged when the provider parses an IIS log file that contains Asian characters in MOM 2005. |
| 894319 |
In multiple tier environment there are missing alerts on the destination management group because alerts are erroneously suppressed into other alerts on the management group. |
| 894464 |
Provide version of the SetActionAccount utility that will allow you to supply the password via command-line instead of prompting during the installation. |
| 895142 |
In Microsoft Operations Manager (MOM) 2005, when you put a MOM agent in maintenance mode, responses may not immediately stop running on the Management Server. Additionally, when you remove an agent from maintenance mode, responses may not immediately start running on the Management Server. |
| 895195 |
You receive an "Access is denied" error message when you use the Install Agent Wizard in Microsoft Operations Manager 2005. |
| 895324 |
The Operator Console fails and displays the "MOM.UI.OPSCONSOLE.EXE.EXE - Common language runtime debugging services Application has generated an exception that cannot be handled" application exception message. |
| 895951 |
You receive an "UnauthorizedAccessException" error message when the MOM-to-MOM Product Connector tries to forward alert and discovery information in Microsoft Operations Manager 2005. |
| 896861 |
You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6. |
| 896989 |
You receive a "0x800706be" error message when you try to view the Computer Groups container in the MOM 2005 Administrator Console. |
| 898466 |
The override rule is not functioning dependably. |
| 898921 |
Issues that you may experience after you install MOM 2005 on a computer that is running Windows Server 2003 with SP1. |
| Fixed |
Visual indicators in the Alerts view do not accurately reflect a computer's state when it is in maintenance mode. |
| Fixed |
MOM licensing information is provided in MOM Reporting, but there is no way for customers to monitor license compliance. This service pack enables you to record the number of licenses acquired by providing this number during setup or by editing the Licenses global setting. The MOM Management Pack has a rule that warns when there is a possible non-compliance issue with licenses. See also: Table 3. |
MOM 2005 SP1 Management Pack Issues and Fixes
| Management Pack |
Title |
Description |
| Microsoft Business Security Analyzer (MBSA) |
The English version of MBSA is installed on non-English builds of Windows |
Prior to MOM 2005 SP1, the MBSASetupFile parameter of the "MBSA Install and Run" script incorrectly listed “MBSASetup-en.msi” as its value. This caused the installation of the English version of MBSA on non-English builds of Windows. The value for the parameter has been corrected, and the appropriate language version of MBSA will be installed on non-English builds of Windows. |
| Microsoft Operations Manager 2005 (MOM 2005) |
The "MOM Database State Monitoring" and "MOM Agent Service Discovery" scripts might generate script errors |
In some environments, the "MOM Agent Service Discovery" script might generate an error on line 14 and the "MOM Database State Monitoring" might generate an error on line 1252. Both of these script errors are fixed in this service pack. |
|
New authentication and MOM to MOM Product Connector related rules added to MOM 2005 SP |
Two rules have been added to enable the detection of mutual authentication problems that affect Operations Manager Server and/or Agent communications. The new rules include "MOM Management Server mutual authentication problems", "MOM Management Server mutual authentication problems", "MMPC error forwarding a new invalid alert", and "MMPC error forwarding an invalid alert update". |
|
An alert might occur when computer discovery takes longer than 5 minutes |
The alert “A script hung or exceeded its specified timeout” might incorrectly occur when computer discovery takes longer than five minutes. The rule has been updated for MOM 2005 SP1 to prevent an alert when this condition exists. |
|
There is no way to monitor MOM licensing compliance other than MOM Reporting |
A new rule compares the number of managed computers against the value in the Licenses global setting. An alert is generated if there is a potential licensing non-compliance issue. |
| Microsoft SQL Server 2000 |
The rule “A SQL job failed to complete successfully” doesn’t work on French versions of SQL Server 2000 |
The criteria for the rule “A SQL job failed to complete successfully” is incorrect and fails to generate alerts when a job failure occurs on a French version of SQL Server 2000. The criteria for the rule has been fixed in this service pack. |
|
The threshold for the SQL Server 2000 Space Analysis script is ignored |
The “SQL Server 2000 Space Analysis” script that is used by the “SQL Server Space Analysis” rule incorrectly ignores the value set for “TempLogErrorLevel” script parameter. The script is fixed, and MOM 2005 SP1 can use the script parameter correctly. |
|
The "Disk Read and Write Latency" view doesn’t list any counters |
The criteria for the "Disk Read and Write Latency" view is incorrect, and as a result. none of the PhysicalDisk Counter instances are displayed. The view criteria is fixed in this service pack. |
|
Some reports fail when run on systems with non-US English regional settings |
The "User Connections by Day" and "User Connections by Peak Hour" reports fail when run on a computer configured with non-US English regional settings. These reports are fixed and will run on systems that are running supported regional settings configurations for MOM 2005 SP1. |
| Microsoft Windows Server Base OS |
The Operating System Storage Configuration might fail when attempting to sort columns |
The Operating System Storage Configuration might fail when attempting to sort by the “Volume Name”, “Drive Free Space GB”, or “Drive Size GB” columns. The report is fixed in this service pack, and sorting by these columns works correctly. |
|
Used and Free space columns are missing from the Operating System Storage Configuration report |
The “Used Space (GB)” and “Free Space (GB)” columns are missing in the Operating System Storage Configuration report. These columns have been added to the report for MOM 2005 SP1. |
|
After installing MOM SP1 on two servers within Virtual PC I got this error on both's machines.
I'll look into this tomorrow! I'm going to bed now ;-)
Tools 
Help
