With Operations Manager 2007 SP1 offical RTM it is time to find what was fixed and what got broken.
The SP1 introduces a bug for the Active Directory monitoring:
DC Last Bind monitors on NON-US, at least on many of the western European regional settings, have a x1000 factor added. So if the AD Last Bind time is 0,016 sec. Ops Mgr 2007 SP1 alerts with 16 sec. DC Bind Time. This is probably because we use "," as delimiter and the US ".". If you open one of the alerts "AD Last Bind Latency...." and goes to the Product knowledge and run the inline task "Check current LDAP response time" the task returns the correct value of 0,016 sec. This worked with Ops Mgr 2007 RTM but it is broken with SP1. There will probably be a web update of the AD MP during March for this.
Dicovery of Windows 2003 CPUs are still disabled by default in SP1:
http://support.microsoft.com/kb/948097
The CPU percentage Utilization monitors are targeted to the Windows server 2003 processor class. However, there is no available Windows server 2003 processor class instance by default, due to the corresponding discovery rule: Discover Windows CPUs is disabled by default.
Resolution:
1. In Operations Manager Console, open Authoring -> Management Pack Objects -> Objects Discoveries.
2. Search for the discovery rule "Discover Windows CPUs".
3. In the properties window of this rule, go to Overrides. Set overrides on all Windows server 2003 operations system role type objects. Check override on the Parameter named "Enable".
4. Save the override setting.
5. When the "Windows server 2003 processor" is working, the CPU percentage Utilization monitors will also work.
I will continue reporting on this in the days to come..
