The following known issues and limitations are applicable to Microsoft® System Center Operations Manager 2007.
The The SDK was unable to synchronize of monitoring object instance with its cached monitoring class information. warning might be displayed when you launch the Operations Manager Console, after the Hardware Management Pack is uninstalled.
You can ignore this warning that is drawing your attention to the fact that a management pack was uninstalled when the Operations Manager was not online.
Workaround: To avoid the warning, launch the Operations Manager Console from the command line with the /ClearCache command line option after uninstalling the Hardware Management Pack (or any management pack). See the documentation for Microsoft System Center Operations Manager 2007 to determine the command line method for starting the Operations Manager.
Invalid Column Name …
This error occurs only when uninstalling the Hardware Management Pack when the Operations Manager Console is online and the cursor focus is on one of the views that was uninstalled. Other errors, such as: Collection was modified; enumeration operation may not execute might also be displayed after the uninstall.
All alerts and events from the Hardware Management Pack depend on the Microsoft Health Service on the managed system to communicate the alert or event back to the Operations Manager Server. If the network connection between the Operations Manager Server and the managed system is broken, or if the managed system stays offline, no alerts or events are communicated to the Operations Manager Server. When the network connection resumes, the cached alerts and events begin to flow to the Operations Manager Server.
When this situation occurs, you might see older alerts and events in the cache as the backlog of alerts and events is communicated and the cache is cleared.
Once a managed system is added to the Operations Manager Server scope, up to three or four minutes might pass before the system and component health states begin to populate correctly in the Operations Manager Console.
Workaround: You can perform manual refreshes periodically to display the discovered components more quickly.
Data in the health state views might disappear if you scroll left and scroll right often because of many columns in the view.
Workaround: A manual refresh causes the data to be displayed again.
In the Monitoring pane dashboard are separate views for the "IBM® System x™ and BladeCenter® x86 systems" state view and the "IBM Systems Hardware Components" state view. You cannot adjust the height of these two views or of any dashboard view.
This is a known Microsoft System Center Operations Manager 2007 limitation without a workaround.
The Path property for some object classes can be empty. All systems in the root Computers view have an empty Path property value, but do have a non-empty Path name property. All objects coming directly from the Windows® Computers view also have an empty Path value unless the Hardware Management Pack explicitly overrides it.
This is a known Microsoft System Center Operations Manager 2007 limitation without a workaround.
Client-side, script-based, in-band management packs like the IBM Hardware Management Pack, V2.0 and the Microsoft Operations Manager Agent require disk space on the managed system. If the disk space runs out on the managed system, the scripts in the Hardware Management Pack cannot launch and cannot communicate health data and alerts to the Operations Manager Server, until disk space is available.
The disk drive of concern is the drive with the %TEMP% folder of the Local System Account, which is the user account that the Operations Manager Health Service Modules run under. This %TEMP% folder almost always is the system drive where Windows is installed.
Microsoft does not recommend an amount of disk space that should be reserved, but the amount of disk space in the %TEMP% drive is controlled by the per-user TEMP environment variable.
When this situation occurs, the event log of the Operations Manager Agent on the managed system might have entries that are similar to the entries in the following examples.
Event Type: Warning Event Source: Health Service Modules Event Category: None Event ID: 10363 Date: 04/20/08 Time: 17:24:04 User: N/A Computer: A-X3650-RAID Description: Module was unable to enumerate the WMI data. Error: 0x80041032 Details: Call cancelled One or more workflows were affected by this. Workflow name: many Instance name: many Instance ID: many Management group: ValX64 For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Health Service Modules
Event Category: None
Event ID: 9100
Date: 04/20/08
Time: 17:25:33
User: N/A
Computer: A-X3650-RAID
Description:
An error occurred on line 105 while executing script
'MOM Backward Compatibility Service State Monitoring Script'
Source: Microsoft VBScript runtime error
Description: ActiveX component can't create object: 'GetObject'
One or more workflows were affected by this.
Workflow name: System.Mom.BackwardCompatibility.ServiceStateMonitoring
Instance name: a-x3650-raid.Lab54.local
Instance ID: {EE77E6E4-5DC5-F316-A0CA-502E4CBFCB97}
Management group: Adamgrp1
For more information, see Help and Support Center
at http://go.microsoft.com/fwlink/events.asp.
This is a known Microsoft System Center Operations Manager 2007 limitation.
Workaround: Create free space on the %TEMP% drive for the Local System Account.
The Microsoft Operations Manager Console provides sticky views, which are remembered from session to session. Such views are remembered even if you delete the Hardware Management Pack and import it back.
This is a known Microsoft System Center Operations Manager 2007 limitation without a workaround.
Remove the Default Management Pack first before removing the Management Pack because of dependency. You cannot delete the Management Pack without removing the dependent management packs.
These messages mean that there are one or more overrides of the rules or monitors in the Hardware Management Pack. The overrides were saved in the Default Management Pack, or in the management pack that is listed in the message.
This behavior is normal for Microsoft System Center Operations Manager 2007.
You can save overrides in a custom management pack and delete the overrides or import the overrides, if necessary. Using a custom management pack in this way can make such tasks less cumbersome.
This is a known Microsoft System Center Operations Manager 2007 limitation.
Workaround: You can delete the management pack that you created to store the overrides of the rules or monitors to prevent dependency messages when you attempt to delete the Hardware Management Pack.
Microsoft System Center Operations Manager 2007 does not support Microsoft Windows Server 2008 at this time.
After using Health Explorer to reset the health states, the most current data can take two minutes or more to roll up to the top-most state views and reflect the true health state.
Workaround: Performing a manual refresh of the information by pressing F5 can speed up the display of the current information.
When you right-click a blank space between the last system line and the horizontal scroll bar, the Data and Status information is no longer displayed.
This is a known Microsoft System Center Operations Manager 2007 limitation.
Workaround: Pressing F5 refreshes the display of the information.
If you recently uninstalled, wait approximately three minutes for the settings to get propagated to the Operations Manager database before you reinstall.
If you do not wait for the uninstall to register, reinstalling can result in managed clients that are not listed in the Operations Manager Console.
This is a known Microsoft System Center Operations Manager 2007 limitation without a workaround.