When you stop a node in a Windows Server 2008 failover cluster, the groups that are hosted on that node may fail over to a random node instead of to the next available node

When you stop a node in a Windows Server 2008 failover cluster, the groups that are hosted on that node may fail over to a random node instead of to the next available node in the Preferred Owners list.

Note When a failover occurs, the groups should move to the next available node in their Preferred Owners list. The Preferred Owners list defines the order in which the resources in cluster groups fail over to the next node.

When you stop a node, the new owner for each of its groups is set to the lowest node identifier instead of to the next preferred owner.

Update information

The following files are available for download from the Microsoft Download Center:


Download the Update for Windows Server 2008 for Itanium-based Systems (KB950181) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=6cbf916a-dd2f-453d-9907-b9781335b7b8)

Download the Update for Windows Server 2008 x64 Edition (KB950181) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=ab52d287-ef10-4392-bc9b-71b6e153a56a)

Download the Update for Windows Server 2008 (KB950181) package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=708f10fb-ff67-4989-bcad-dfa73bb3fcf0)

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

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: 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 the Failover Clustering feature installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, x86-based versions

Windows Server 2008, Itanium-based versions

Windows Server 2008, x64-based versions

To work around this problem, before you shut down the active node, move all the groups that are currently owned by the active node to another node by using the Failover Cluster Management snap-in.

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: