Technically there isn’t any real surprises within the documentation of the (updated) Windows Server OS MP.
Microsoft breaks out the MP in the same manor as some previous MPs (separate modules for varying flavors; i.e. – W2K, W2K3, W2K8).
Taking a queue from the latest Exchange 2007 MP, it is refreshing to see Microsoft not enable by default some of the Windows 2000 Server Monitoring. Thus eliminating some of the useless (IMO) monitoring for the W2K OS.
Specifically, in previous versions of the Windows Server 2000 OS MP, you had to create overrides for Logical Disk Object and Processor Monitoring within Windows 2000 Server.
Logical Disk Object is not enabled (by default) for Windows 2000 Server.
There are documented steps to enable Logical Disk Object monitoring, but note that an event will be written to the Ops Mgr Event Log if done:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 31876
Date / Time:
Data item returned no information for parameter ‘$Data/Property[@Name=’SystemDrive’]$’
This usually indicates that the query is incorrect.
Workaround: There is no workaround for this issue in this release of Ops Mgr 2007.
Objects the Windows Server Operating System Management Pack Discovers:
In version 6.0.6667.0 of the Windows Server Operating System Management Pack, the intervals for the some discoveries are changed for Windows Server 2003 and Windows Server 2008 as shown in the following table:
Also, the ability to ‘Monitor Processors‘ is not supported within Windows 2000 Server.
Or is it?
One minor gripe I do have is the clarity (or lack thereof) or verbage inside the MPs documentation…
OM2007_MP_WinSerBas (updated Win Server OS MP):
Monitoring Processors: This feature is not supported on Windows 2000 Server. (p. 16)
Monitoring Total Processor Performance: The same parameters area available in the Windows Server 2003 and Windows 2000 Server management packs. (p. 17)
It is the responsibility of the product team to create relevant and useful documentation in relation to the Product MP, but I have to question the review process of the accompanying MP documentation.
Some may say that I am knit picking – I guess that is the German in me.
But not everyone has been using every MP release (including updated MPs) from Microsoft – so some of the ‘useless chatter’ from Rules and Monitors inside MPs leave some folks frustrated and scrambling to override the noise.
Also, it is a little confusing when the naming convention inside the documentation is not the same (i.e. – Windows Server 2000 vs Windows 2000 Server). A technical reviewer will be able to understand the slight changes in OS listing(s), but a simple Find/Replace isn’t too difficult – right?
Rather than spend too much time tweaking Rules and Monitors for Windows 2000 Servers, I tend to work with Business Units to virtualize and eventually migrate to a more stable OS environment (if possible).
Another item to note:
Per the MP documentation:
“Other Requirements: The Windows Server Library, the Windows 2000 Server, and the Windows Server 2003 management packs rely on the RTM (Release to Manufacturing) version of Operations Manager 2007, but the Windows Server 2008 Management Pack requires Operations Manager 2007 Service Pack 1 (SP1) because the agent must be SP1 to run on a server running Windows Server 2008.”
If you are running a Release Candidate of Ops Mgr nor do not have W2K8 SP1 installed, you will not be able to import the Windows Server OS MP.
Microsoft’s Product Management Pack developmental lifecycle has matured, no question about that. Whether due to past experiences, Product Manager driven or the community voicing concerns when a product is released and an accompanying MP isn’t.
I look forward to future product releases and their accompanying MPs…