"Move-SmbWitnessClient" PowerShell command fails in Windows Server 2012

Symptoms

Important The hotfix that corresponds to KB 2848727 has been included with the hotfix KB 2848344, which contains all fixes that were previously included in KB 2848727.

Consider the following scenario:
  • Assume that you have a Windows Server 2012-based cluster node.
  • You request a Server Message Block (SMB) client to move the associated SMB connection from the cluster node to a specified cluster node by running the following PowerShell command:
    Move-SmbWitnessClient 
  • The SMB client is connected to the cluster node through a different server name (for example, NetBIOS name or Domain Name System host name).
In this scenario, the command fails.

Cause

This issue occurs because the system recognizes multiple registrations with the same name. Therefore, an error is returned when the system receives the move request.

Note The SMB Witness cmdlets stores two entries under the same name when an SMB client uses different names to connect to an SMB share.

Resolution

This hotfix is also available at Microsoft Update Catalog

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 website: 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 be running Windows Server 2012.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

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


Status

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

More Information

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
Properties

Article ID: 2848727 - Last Review: Jun 13, 2013 - Revision: 1

Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Foundation, Windows Server 2012 Foundation, Windows Server 2012 Foundation, Windows Server 2012 Foundation, Windows Server 2012 Standard, Windows Server 2012 Standard, Windows Server 2012 Standard, Windows Server 2012 Standard

Feedback