Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The DFS Replication Management Pack shows alerts for cluster network names that are in the �healthy� status on a Windows Server 2008 R2 failover cluster


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use the Distributed File System (DFS) Replication Management Pack in the File Services Management Pack for System Center Operations Manager 2007 to monitor the health of the DFS Replication service on a Windows Server 2008 R2 failover cluster.
  • You change the ownership of a cluster network name and the ownership of the DFS Replication resources from one cluster node to another cluster node.
  • You notice that some alerts appear in the Replication Service Alerts window for a cluster network name that is in the "unhealthy" status.
  • System Center Operations Manager 2007 changes the cluster network name from the "unhealthy" status to the "healthy" status.
In this scenario, you notice that the alerts still exist in the Replication Service Alerts window.

↑ Back to the top


Cause

This issue occurs because the DFS Replication service does not receive any notification when the replicated folder resources are moved between cluster nodes.

↑ Back to the top


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 the problem described in this article. 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: 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, your computer must be running Windows Server 2008 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Dfsrclus.dll6.1.7600.20621213,50419-Jan-201010:26x64

↑ Back to the top


Workaround

Workaround for Windows Server 2008 R2

If the state of the cluster network name is healthy, you can manually close the alerts in the Replication Service Alerts window.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about the DFS Replication service, visit the following Microsoft Developer Network (MSDN) Web site: For more information about the DFS functions, visit the following MSDN Web site: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_a33b637f77dad277159ca06027d78c13_31bf3856ad364e35_6.1.7600.20621_none_6e80b45b5cf4aabc.manifest
File versionNot applicable
File size711
Date (UTC)20-Jan-2010
Time (UTC)03:13
PlatformNot applicable
File nameAmd64_microsoft-windows-dfsr-cluster-server_31bf3856ad364e35_6.1.7600.20621_none_ca902b445d4ed845.manifest
File versionNot applicable
File size2,757
Date (UTC)19-Jan-2010
Time (UTC)13:40
PlatformNot applicable

↑ Back to the top


Keywords: KB979564, kbautohotfix, kbsurveynew, kbfix, kbHotfixServer, kbqfe, kbexpertiseadvanced, kbclustering

↑ Back to the top

Article Info
Article ID : 979564
Revision : 3
Created on : 9/11/2010
Published on : 9/11/2010
Exists online : False
Views : 282