System Center Management Pack for Windows Server Operating System Version: 6.0.7323.0


 

 

 

image

 

 

  • System Requirements

    Supported Operating System

    Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

      The Windows Server Operating System Management Pack for Operations Manager is designed for the following versions of System Center Operations Manager: • System Center Operations Manager 2007 R2 • System Center Operations Manager 2012 • System Center Operations Manager 2012 SP1 • System Center Operations Manager 2012 R2
  • Install Instructions
      See MP Guide for installation and usage instructions

 

image

 

What’s inside the Management Pack Guide

 

 

Changes in Version 6.0.7323.0

· Added Storport Miniport monitor for monitoring Event ID 153 in Windows Server 2003, 2008 and 2012 platforms.

· Fixed bug: Logical Disk MB Free Space and Percentage Free Space monitor issues: Operator can set the threshold values for Error state even within Warning state default thresholds. At that, the Error state will supersede the Warning state according to the set values. Error threshold is independent of the Warning threshold.

· Fixed localization issue with root report folder in the Report Library.

· Windows Server Cluster Shared Volume Monitoring management pack is now supporting Nano Server and Windows Server 2016. Please note that Nano Server monitoring is supported by SCOM 2016 only.

· Fixed bug with duplicating Nano Server Cluster Disk and Nano Server Cluster Shared Volumes health discoveries upon MP upgrade. See Troubleshooting and Known Issues section for details.

· Fixed bug: Windows Server 2003 Computer discovery was causing repeated log events (EventID: 10000) due to improper discovery of non-2003 Windows Server computers.

· Fixed bug: Windows Server 2008 Computer discovery was causing repeated log events (EventID: 10000) due to improper discovery of non-2008 Windows Server computers.

· Fixed bug: Windows Server 2008 R2 Computer discovery was causing repeated log events (EventID: 10000) due to improper discovery of non-2008 R2 Windows Server computers.

· Fixed bug: Windows Server 2012 Computer discovery was causing repeated log events (EventID: 10000) due to improper discovery of non-2012 Windows Server computers.

· Fixed bug: Windows Server 2012 R2 Computer discovery was causing repeated log events (EventID: 10000) due to improper discovery of non-2012 R2 Windows Server computers.

· Fixed bug: [Nano Server] Cluster Seed Name discovery was causing repeated log events (EventID: 10000) due to improper discovery of non-Nano objects.

 

Supported Configurations

The System Center Management Pack for Windows Server Operating System is designed to monitor the following versions of the basic operating system:

· Windows Server 2012 R2

· Windows Server 2012

· Windows Server 2008 (including Windows Server 2008 R2)

· Windows Server 2003

 

All the management packs are supported on Operations Manager 2007 R2 and System Center 2012 and System Center 2012 R2 Operations Manager. For specific configurations regarding patches, see the table below.

Operating system being monitored

Operations Manager 2007 R2

Windows Server 2008 SP1

Install the updates for the operating system as provided in the following Knowledge Base articles:

· KB951327 (install on computers running the Operations console)

· KB952664

· KB953290

Windows Server 2008 SP2

No updates required.

Windows Server 2008 R2

Refer to the support statement in Knowledge Base article 974722 (http://go.microsoft.com/fwlink/?LinkId=161394).

Windows PowerShell 2.0 for Windows Server 2008 (http://www.microsoft.com/en-us/download/details.aspx?id=9864 )

 

Other Requirements

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.

The Windows Server Library and the Windows Server 2012 management packs rely on both RTM of System Center 2012 Operations Manager and Operations Manager 2007 R2 with the latest updates installed.

 

Security Considerations

This section provides information about using a low-privilege account with the System Center Management pack for Windows Server Operating System. It also includes information about the computer groups that are added when this management pack is installed.

Low-Privilege Environments

The Windows Operating System Management Pack uses the agent action account to perform discovery and run rules, tasks, and monitors. The agent action account can run as Local System or as a named account. When running as Local System, the agent action account has all of the rights needed to perform discovery and run rules, tasks, and monitors.

Important

A low-privilege account can be used only on computers running Windows Server 2008 or Windows Server 2003. On computers running Windows 2000 Server, the action account must be a member of the local administrator security group or Local System.

Using a low-privilege domain account requires password updating that is consistent with your password expiration policies.

Using a Low-Privilege Account

You can use a low-privilege account for the agent action account; however, a number of rules and monitors require elevated rights. On computers running Windows Server 2008 or Windows Server 2003, the low-privilege account must meet the following requirements:

· Member of the local users group

· Member of the local Performance Monitor Users group

· Granted Log On Locally rights

Three of the monitors and object discoveries in the Windows Operating System Management Pack require a high-privilege account to perform the functions:

· Mount Point Discovery

· Physical Disk Discovery

· Monitoring the Computer Browser service

In addition, the following tasks related to Windows Server 2008 require a high-privilege account:

· Top CPU Usage

· Display Active Sessions

· Display Server Statistics

These rules and monitors have been configured to use the Privileged Monitoring Account Run As Profile, which defaults to Local System, and does not require association with any Run As account and target computer. As a result, no user intervention is required for these rules and monitors that need to use a high-privilege account.

If your requirements stipulate that only a low-privilege account is to be used in your environment, use overrides to disable the three monitors and object discoveries.

 

Known Issues

Disk partitions, which correspond to mounted disks are not monitored

The “Core Windows Services Rollup” monitor for Windows Server 2008 includes services that it should not

Remote Desktop (Admin) not always accessible

The console session does not work in Windows Server 2008

Behavior for accessing the console session of Windows Server 2003 has changed

SUBST drive mappings are not supported by logical disk monitoring

Cluster disks managed by third-party software are not monitored

PowerShell in 2012 MP fails if .NET is uninstalled from Core OS agent by user

Disk Performance dashboard view is empty

Some objects may be missing in dashboard view during rediscovering upon the management pack update.

Cluster disks discovery

Offline Cluster Shared Volume is not displayed in the Operations Manager

Cluster Shared Volume State monitor does not work correctly if Cluster Shared Volume goes offline.

Performance counters of logical CPUs are no longer available upon MP upgrade.

Cluster Shared Volume objects will be re-discovered with a new key value upon the management pack upgrade.

SCOM may stop discovery of clusters and cluster groups.

Mount point discovery may work incorrectly.

“Cluster Disc – Free Space Monitor (MB)” changes its state to “Critical” when the cluster disk is offline.

Previously discovered virtual computer and its objects are displayed along with the new ones upon change of network resource name.

Nano Server cluster health discoveries may be duplicated after MP upgrade.

Cluster Shared Volume NTFS State Monitor does not switch to Critical state.

Comments (0)

Skip to main content