OpsMgr, SCE And MOM Blog

MOM 2005 SP1 - New/Updated MP's for Windows Server 2008 release/releasing to the MP catalog

2008-08-04T22:15:44Z

With the announcement of MOM 2005 SP1 agent support on Windows Server 2008. The following MP's are in the process of release. A number a already available for download from the MP catalog, others will follow shortly (http://www.microsoft.com/technet/prodtechnol/scp/opsmgr05.aspx?SCPProdID=2)

AD Federation Services
AD Rights Management Service
Windows Server 2008 Streaming Media Services
Internet Information Service
Windows Server 2008 Network Load balancing
Windows Server 2008 Failover clustering
Windows Server 2008 Fax Server
Active Directory
Windows Server 2008Terminal Services
Network Policy Server
UNIX Interoperability
Windows Server 2008 AD Certificate Services
DHCP

MOM 2005 Service Pack 1 support on Windows Server 2008-based computers

2008-08-04T21:55:46Z

The support of MOM 2005 Service Pack 1 on Windows Server 2008-based computers is announced. The KB article publication was a little delayed in it's release (out of my control - sorry). The KB article discussing MOM 2005 SP1 Win2k8 support is released under 953140

Details:

MOM 2005 Roles Supported

The only MOM 2005 SP1 role supported on Window Server 2008 is the 32-bit Agent role.

Windows Server 2008 Roles Supported (Details to be published to the TechNet supported configurations for MOM 2005 SP1)

Operating System	Agent-Managed computer (32-bit)	Agent-Managed computer (64-bit)	Agentless Managed Computer
Windows Server 2008, Standard x86 Edition	Yes	No	Yes
Windows Server 2008, Standard x64 Edition	Yes	No	Yes
Windows Server 2008, Enterprise x86 Edition	Yes	No	Yes
Windows Server 2008, Enterprise x64 Edition	Yes	No	Yes
Windows Server 2008, Datacenter x86 Edition	Yes	No	Yes
Windows Server 2008, Datacenter x64 Edition	Yes	No	Yes
Windows Server 2008, Standard x86 Edition, Core role installed	Yes	No	Yes
Windows Server 2008, Standard x64 Edition, Core role installed	Yes	No	Yes
Windows Server 2008, Enterprise x86 Edition, Core role installed	Yes	No	Yes
Windows Server 2008, Enterprise x64 Edition, Core role installed	Yes	No	Yes
Windows Server 2008, Datacenter x86 Edition, Core role installed	Yes	No	Yes
Windows Server 2008, Datacenter x64 Edition, Core role installed	Yes	No	Yes

Yes = Supported operating system. Setup does not prevent installation.

No = Setup prevents installation or upgrade.

Hotfixes that may be required

There is one potential hotfix required if deploying an agent to a Windows Server 2008-based domain controller computer. Details can be found within http://support.microsoft.com/kb/919154 (The MOM service does not start and event 9014 is logged when you deploy a Microsoft Operations Manager 2005 agent to a domain controller that is running Windows Server 2008)

Known Issues

Issue 1: Event log Descriptions for collected Windows Server 2008 Security event logs (Source=Microsoft-Windows-Security-Auditing) for rules utilizing the Security event log provider return “Unable to find Security source Microsoft-Windows-Security-Auditing message [nnnn]” in the description.

Workaround 1: None. Event log Descriptions and any collected parameters are otherwise unaffected. Rules using the Security event log provider which may specifically use the ‘From Source’ with parameter Security criterion may need to be duplicated for Windows Server 2008-based computers or have the ‘From Source’ criterion removed to allow successful collection of security events.

Issue 2: A low privilege agent action account is unable to monitor Windows Server 2008-based event logs.

Workaround 2: In addition to the requirement specified for a low privilege action account discussed in the MOM 2005 Security Guide whitepaper, the following additional requirements must be met:

· The low privilege action account also needs to be a member of the ‘Event Log Readers’ local group on Windows Server 2008.

· The Network Service built-in account requires explicit Read privileges on the following registry key of Windows Server 2008-based computers running the MOM agent

o HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\EventLog\Security

Issue 3: Internet Information Server (IIS) log collection does not work on Windows Server 2008-based servers running IIS using the Internet Information server Web server log MOM provider.

Workaround 3: None. W3C logs within IIS7 are in UNICODE format by default and log names preceded with u_ which the MOM Web server log provider is unable to read.

KB919154 - The MOM service does not start and event 9014 is logged when you deploy a Microsoft Operations Manager 2005 agent to a domain controller that is running Windows Server 2008

2008-08-04T21:55:08Z

This KB documents an issue with installing the MOM 2005 agent on a a Windows Server 2008 domain controller and a hotfix available to correct this issue.

See http://support.microsoft.com/kb/919154

SYMPTOMS

When you deploy a Microsoft Operations Manager (MOM) 2005 agent to a computer that is running Windows Server 2008, you experience the following symptoms:

•
The MOM service does not start.

•
The following event is logged in the Application log:

Event Source: Microsoft Operations Manager
Event ID: 9014
Event Cateory: None
Event Type: Error
User: N/A
Computer: ComputerName
Description: The Microsoft Operations Manager service (MOMService.exe) terminated due to an unhandled exception. It will attempt to restart itself.

You experience this problem if the Windows Server 2008-based computer where you install the MOM agent is configured as a domain controller.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Support for running Operations Manager 2007 on hardware vitalization software

2008-07-28T18:00:59Z

Awaiting the KB article for this I wrote a while ago. This currently does NOT include Hyper-V at this time which needs to be tested prior to support statement being released. This should be within 90 days of Hyper-V final release.

Please see the description on the Manageability Team CSS blog

Windows Server 2008 Support MP's released

2008-07-28T17:55:00Z

Windows Server 2008 Application Server (6.0.6278.22)

Windows Server 2008 Base OS (6.0.6278.22)

Terminal Services (6.0.6278.22)

Exchange Server 2007 (6.0.6363.0)

Key Management Service (6.0.6278.9)

Group Policy 2003 (6.0.6278.22)

Group Policy 2008 (6.0.6278.22)

Operations manager 2007 Sp1 / Essentials 2007 SP1 support for windows server 2008 announced

2008-07-26T03:19:37Z

Windows Server 2008 support has been announced. Please see the following resources for more information

The Knowledgebase article KB953141 announces our support of OpsMgr SP1 and SCE SP1 running on Windows Server 2008

The above article discusses 4 required Windows Server 2008 hotfixes which may have to be installed depending on the OpsMgr/SCE role installed on Windows Server 2008

The above article also provide a link to a required OpsMgrSP1/SCESP1 hotfix rollup which is described in Knowledgebase article KB954049

The hotfixes referenced are all available from the Microsoft download center.

The Support Configurations details for Operations Manager 2007 SP1 have been updated to reflect supported Windows Server 2008 roles http://tnstage.dns.microsoft.com/en-us/library/bb309428.aspx

Management Pack Releases for Windows Server 2008 will take place shortly.

The hotfix provided in KB954049 can be installed on localized OpsMgrSP1/SCESP1 installations as it does not provide any localized fixes. The hotfix MSI installer is currently provided in English, localized versions will be provided in the coming weeks.

NOTES:

Please take careful consideration of the OpsMgrSP1/SCESP1 installation notes within KB954049 , particularly:

The OpsMgrSP1/SCESP1 hotfix must be applied after installation of OpsMgr/SCE on Windows Server 2008 or after in-place upgrade of the OS to Windows Server 2008 of an affected OpsMgr/SCE role. This will ensure correct performance counter registration on RMS, SCE Server, Management Server, Gateway server roles.
If User Account Control (UAC) is enabled on Windows Server 2008 when you apply the OpsMgrSP1/SCESP1 hotfix, you MUST execute SystemCenterOperationsManager2007-SP1-KB954049-X86-X64-ENU.MSI from an elevated command prompt. Failure to do so will not allow the display of the hotfix applicaton dialog once the MSI has completed installation of the staging bits on the server.
Read carefully the Known issues section of KB954049. There are a number of requirements and known issues, several still under investigation (Issues 6/7). As more information on Issues 6/7 becomes available and hotfixes developed the KB article will be updated and details provided.

FRS 2000/2003 MP for Operations Manager 2007 (Documentation Update)

2008-07-01T07:09:54Z

The documentation included with the FRS MP 6.0.5000.0000 has been updated. http://www.microsoft.com/downloads/details.aspx?FamilyID=6F5F8E56-6A35-4909-BB8F-968EE95A8F17&displaylang=en

MP Refresh – Exchange Server 2007 Management Pack for Operations Manager 2007 (6.0.6278.12)

2008-06-21T01:37:00Z

The Exchange 2007 MP has been updated and is available from : http://www.microsoft.com/downloads/details.aspx?FamilyId=1A83E112-8677-4E03-83C3-F1B7EBFC3A4B&displaylang=en&displaylang=en

This MP release has dependencies on some recent hotfixes released :Including KB950853, KB951979, KB951380

There is an MP Guide with this version:)

From the download page

Overview

The Microsoft Exchange Server 2007 management pack is designed to be used for monitoring Exchange 2007 events, collecting Exchange component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. By detecting, sending alerts, and automatically responding to critical events, this management pack helps indicate, correct, and prevent possible service outages or configuration problems, allowing you to proactively manage Exchange servers and identify issues before they become critical. The management pack monitors and provides alerts for automatic notification of events indicating service outages, performance degradation, health monitoring, and centralized management.
This Management Pack requires Operations Manager 2007 Service Pack 1.
This Management Pack requires the Operations Manager 2007 updates specified in Knowledge Base articles 950853, 951979 and 951380 (see the Management Pack Guide for details).
Release History:

10/9/2007 - Initial Release, version 6.0.5000.0
6/20/2007 - Updated Release, version 6.0.6278.12

KB951526 (Hotfix) - The Root Management Server (RMS) of System Center Operations Manager 2007 Service Pack 1 becomes unstable or unusable if a management pack is imported

2008-06-19T21:16:43Z

The following Kb has been recently published and a hotfix is available. See http://support.microsoft.com/kb/951526

SYMPTOMS

Consider the following scenario:

•You import a management pack to monitor certain network devices in a Microsoft System Center Operations Manager 2007 Service Pack 1 environment.

•You perform a network device discovery by using Simple Network Management Protocol (SNMP).

In this scenario, you may receive one or both of the following error messages:
Error message 1

Health service host process has stopped working

Error message 2

Health service Host process encountered a problem and need to close

In this scenario, the OpsMgr Health Service is still running correctly. However, the Root Management Server (RMS) becomes unhealthy or unusable. Additionally, the following event is logged in the Operations Manager log on the server on which you perform the network device discovery:

Event Type: Error
Event Source: HealthService
Event Category: Health Service
Event ID: 4000
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
A monitoring host is unresponsive or has crashed. The status code for the host
failure was 2164195371.
Problem signature:
Problem Event Name: APPCRASH
Application Name: MonitoringHost.exe
Application Version: 6.0.6278.0
Application Timestamp: 47b71437
Fault Module Name: HealthServiceRuntime.dll
Fault Module Version: 6.0.6278.0
Fault Module Timestamp: 47b71433
Exception Code: c0000005
Exception Offset: 00003d9d
OS Version: 6.0.6001.2.1.0.16.7
Locale ID: 1033

CAUSE

A defect in the SNMP networking module causes the HealthService service to become unstable or to crash. Therefore, the Root Management Server becomes unstable or unusable.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have System Center Operations Manager 2007 Service Pack 1 installed

KB951380 (Hotfix) - Some computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1

2008-06-19T21:10:27Z

The following KB has recently been published http://support.microsoft.com/kb/951380 and a hotfix is available.

SYMPTOMS

When you run a discovery operation in Microsoft System Center Operations Manager 2007 Service Pack 1, and a cluster node is discovered, some computer properties may not be collected for the cluster node. For example, the DNS host name, the security identifier (SID) and the Active Directory organizational unit of the cluster node may not be collected. Therefore, some Operations Manager workflows may not function correctly. For example, if the DNS host name is not collected in an Operations Manager 2007 environment that has the Microsoft Exchange Server 2007 Management Pack applied, the following event may be logged:

Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 10720
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health Service. This is a transient issue, the affected rule(s) will be unloaded and the Health Service will restart them when initialization is complete.

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have System Center Operations Manager 2007 Service Pack 1 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

KB949969 Some data partition tables that exceed the data retention period are not groomed from the Audit Collection Services database in Operations Manager 2007

2008-06-13T01:48:54Z

New KB http://support.microsoft.com/kb/949969/en-us and hotfix

SYMPTOMS

Consider the following scenario:

•
You use the Audit Collection Services (ACS) feature in Microsoft System Center Operations Manager 2007 to collect security events from managed computers.

•
You configure database grooming policies for the ACS database.

However, some data partition tables that exceed the data retention period are not groomed from the database as expected. Over time, the ACS database may run out of disk space.
When this problem occurs, you may discover that these partition tables have a status of 1.

CAUSE

This problem occurs for one or more of the following reasons:

•
When a partition is closing, ACS tries to calculate the last event insertion time for the partition. ACS uses the last event insertion time to determine whether the partition is still within the retention period. However, the calculation operation may time out if the partition is too large. In this situation, ACS saves an invalid time to the last event insertion time field.

•
ACS marks the partition status to 1 (This means that the partition status is "in transition") when a partition is closing. ACS sets the partition status to 2 (This means that the partition status is "closed") only after re-indexing is completed. However, the re-indexing operation may time out if the partition is too large. In this situation, the partition remains in the "in transition" status indefinitely.

RESOLUTION

Hotfix information

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Hotfix installation instructions

To apply this hotfix, follow these steps:

1.
Copy the following file from the hotfix package to a local folder or to a shared folder. Then, run this file:

SystemCenterOperationsManager2007-SP1-KB949969-X86-X64-ENU.MSI

2.
By default, this hotfix is installed into the following folder:

%ProgramFiles%\System Center 2007 Hotfix Utility\Q949969

The Q949969 folder contains the following subfolders:

•
An x86 subfolder for x86 platforms

•
An x64 subfolder for x64 platforms

Open the x86 subfolder or the x64 subfolder, as appropriate for your situation.

3.
Locate the AdtSrvDll.dll file in the following folder:

%WINDIR%\system32\Security\AdtServer

4.
Verify that the version of the AdtSrvDll.dll file is greater than or equal to version 6.0.6278.0 and less than version 6.0.6278.7. To do this, right-click the AdtSrvDll.dll file in Windows Explorer, and then click Properties. The File version field on the Version tab displays the version of the file.
Note If the file version is greater than or equal to version 6.0.6278.7, this file already contains the current hotfix. If the file version is less than version 6.0.6278.0, you cannot apply this hotfix.

5.
On the ACS Collector server, stop the Operations Manager Audit Collection Service.

6.
Copy the following files from the Q949969 folder into the AdtServer folder that you located in step 3.

•
AdtSrvdll.dll

•
DbClosePartition.sql

•
DbCreatePartition.sql

When you do this, you replace the existing files with the hotfix files.

7.
On the server that hosts the ACS database or that has a connection to the ACS database, open SQL Server Management Studio.

8.
In SQL Server Management Studio, connect to the ACS database. By default, the ACS database is named "OperationsManagerAC."

9.
In SQL Server Management Studio, open a new query, and then run the following statements:

Use OperationsManagerAC
Update dtPartition Set Status = 2 Where Status = 1

10.
Verify that you receive the following message in the result pane:

(n row(s) affected)

11.
Restart the Operations Manager Audit Collection Service that you stopped in step 5.

Post-hotfix behavior

After you apply this hotfix, ACS uses the partition close time instead of the last event insertion time to determine whether a partition exceeds the retention period. In addition, when a partition is closing, the status of the partition is set from 0 directly to 2, instead of being set to 1.

Prerequisites

To apply this hotfix, you must have the following prerequisites installed on the computer:

•
System Center Operations Manager 2007 Service Pack 1

•
ACS Collector

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

KB950853 - A memory leak occurs when you monitor Exchange Server 2007 by using the MOM 2007 agent in System Center Operations Manager 2007

2008-06-13T01:45:07Z

Sorry this is one I failed to blog which released while I was at MMS http://support.microsoft.com/kb/950853/en-us .This hotfix is strongly recommended for for those running the Exchange 2007 MP together with http://support.microsoft.com/kb/951979/en-us

SYMPTOMS

Consider the following scenario:

•You import the Microsoft Exchange Server 2007 Management Pack for Operations Manager 2007 into a management group in Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1).

•Then, you install the Operations Manager 2007 agent on an Exchange Server 2007 computer to monitor Exchange rules and processes.

In this scenario, a memory leak occurs on the Exchange Server 2007 computer.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Operations Manager 2007 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Hotfix installation information

You must apply this hotfix on all Operations Manager Management Server computers. You can apply this hotfix from Windows Explorer or at a command prompt. This hotfix package includes both 32-bit and x64 file versions. When you apply this hotfix, it will install the files versions that are appropriate to your particular installation.
The computers that are running the agent are updated automatically. However, you must approve the update in the Pending Management folder. To do this, follow these steps:

1.
On the computer that is running the management server role, click Start, point to All Programs, point to System Center Operations Manager 2007, and then click Operations Console.

2.
Select Administration view, expand Administration, expand Device Management, and then click Pending Management.

3.
In the Pending Management folder, review and approve the agent computers on which you want to apply this hotfix.

Prerequisites

You must install Operations Manager 2007 Service Pack 1 before you apply this hotfix. To download the Operations Manager 2007 Service Pack 1 Upgrade Package, visit the following Microsoft Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=EDE38D83-32D1-46FB-8B6D-78FA1DCB3E85&displaylang=en (http://www.microsoft.com/downloads/details.aspx?FamilyId=EDE38D83-32D1-46FB-8B6D-78FA1DCB3E85&displaylang=en)

Restart requirement

You do not have to restart the computer after you apply this hotfix package. However all Operations Manager services will be automatically restarted.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

New KB951979 (SP1 Hotfix): Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed

2008-06-10T20:00:10Z

The following hotfix has been released for Operations Manager 2007 SP1 containing four management pack updates. These correct a number of issues seen after SP1 upgrade. See http://support.microsoft.com/kb/951979/en-us for full details.

These management packs will not be posted on the Management pack catalog and are only available as a hotfix at this time. See the link in the KB article to request this hotfix.

Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed

SYMPTOMS

Consider the following scenario. You are using a management server that has Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1) installed. This management server also has certain management packs installed. In this scenario, the following problems occur.

Problem 1

The management server cannot collect the CSDVersion property from Windows Vista-based client computers. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 31876
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Data item returned no information for parameter '$Data/Property[@Name='CSDVersion']$'
This usually indicates that the query is incorrect.

Problem 2

The management server cannot collect operating system properties from Windows 2000 Service Pack 4-based client computers. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 10409
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Object enumeration failed Query: 'SELECT Version,Caption,BuildNumber,CSDVersion,ServicePackMajorVersion,ServicePackMinorVersion,SerialNumber,InstallDate,SystemDrive,WindowsDirectory,TotalVisibleMemorySize FROM Win32_OperatingSystem' HRESULT: 0x80041017 Details: Invalid query One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DiscoverWindowsOSProperties Instance name: InstanceName Instance ID: {Instance ID} Management group: GroupName

Problem 3

The HandleCountThreshold agent monitor does not restart the HealthService service on the Microsoft Exchange Server agent even when the HandleCountThreshold value has been exceeded. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Script
Event Category: None
Event ID: 6026
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
RestartHealthService.js : Restarting Health Service. Monitoring Host exceeded Process\Private Bytes threshold.

Problem 4

Audit Collection Services (ACS) events cannot be collected correctly. Additionally, Operations Manager displays the following error message:
An error occurred while performing a database operation. The error code was {0}

Problem 5

Incorrect warnings are raised for Performance Data Source Module when some services in the system are disabled. Additionally, Operations Manager displays the following error message:
Performance Module could not find a performance counter
Back to the top

Problem 6

Cluster discovery does not work correctly when the Virtual Server Name is a substring of the Physical Server Name.

RESOLUTION

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451)
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Hotfix installation instructions
To apply this hotfix, follow these steps:1. Copy the SystemCenterOperationsManager2007-SP1-KB951979-X86-X64-ENU.msi file from the hotfix package to a local folder or to a shared folder.
2. Run the SystemCenterOperationsManager2007-SP1-KB951979-X86-X64-ENU.msi file.
3. Locate the hotfix utility folder for the hotfix. By default, the folder has the following path:
%ProgramFiles%\System Center 2007 Hotfix Utility\Q951979
4. Import the following management packs from the hotfix utility folder:

• Microsoft.SystemCenter.2007.mp (version 6.0.6278.19)
• Microsoft.SystemCenter.ACS.Internal.mp (version 6.0.6278.19)
• Microsoft.SystemCenter.Internal.mp (version 6.0.6278.19)
• Microsoft.Mom.BackwardCompatibility.mp (version 6.0.6278.19)

Prerequisites
To apply this hotfix, you must have System Center Operations Manager 2007 SP1 installed.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.

Microsoft Dynamics CRM 4.0 Management Pack for Microsoft Operations Manager 2005 Released (04.0.0000.0000)

2008-06-06T19:25:33Z

The Microsoft Dynamics CRM 4.0 Management Pack for Microsoft Operations Manager 2005 has released http://www.microsoft.com/downloads/details.aspx?FamilyID=2e2b747d-1947-474c-91c6-246348871174&DisplayLang=en

Overview

The views, tasks, rules, and knowledge specific to Microsoft Dynamics CRM 4.0 that comprise this Management Pack provide the means for MOM users to centrally manage the server application, its component services, and the computers on which they run. The Microsoft Dynamics CRM 4.0 Management Pack also collects performance analysis and capacity planning data by tracking application performance and user load.
By managing these Microsoft Dynamics CRM components in MOM, the administrator can respond quickly to critical events and key performance indicators, and take action to prevent service outages, reduce the resolution time for alert conditions, and increase the overall availability and performance of the Microsoft Dynamics CRM system.
Feature Bullet Summary:

Monitors the availability and health of the following component services:
- Microsoft Dynamics CRM Asynchronous Processing service
- World Wide Web Publishing
- Microsoft Dynamics CRM Deletion service
- Microsoft Dynamics CRM databases
Monitors the availability and health of the following application components and functionality:
- Deletion of deleted records
- Operability of ISV plug-ins
- Web application requests processing, SOAP exceptions, and unexpected failures
Detects brute-force attacks and denial of service attacks.
Monitors the performance metrics of the following components:.
- Web application requests processing
- Database query processing
Monitors the system for configuration-related failures.

Release History

6/5/2008 - Initial Release, version 04.0.0000.0000.

Message Queuing Management Pack (MSMQ) for Operations Manager 2007 Released (6.0.6278.23)

2008-06-04T19:13:57Z

The MSMQ MP has been released http://www.microsoft.com/downloads/details.aspx?FamilyID=1d2b4398-8bc2-4a43-850c-852ebb0d983b&DisplayLang=en

Overview

Message Queuing (also known as MSMQ) is a server application that enables applications to communicate across heterogeneous networks and systems that may be temporarily offline or otherwise inaccessible. Instead of an application communicating with a service on another computer, it sends its information to Message Queuing, which sends the information to a Message Queuing service on the target computer where it is made available to the other application. Message Queuing provides guaranteed delivery, efficient routing, security, and priority based messaging.
Feature Summary
The Message Queuing Management Pack provides monitoring for the following:

MSMQ Servers
MSMQ Triggers
MSMQ Queues
Dependant Clients

Release History

6/3/2008 - Initial Release, version 6.0.6278.23. Refer to the MP guide for further details.