2013
01.28

Microsoft has released a number of fixes for when a third-party storage resource is configured in a Windows Server 2012-based failover cluster, certain features do not work.

KB2795997 UI is displayed incorrectly when you right-click a third-party disk resource in the Available Storage area in Windows Server 2012

Assume that you configure a third-party disk resource in a Windows Server 2012-based failover cluster. In this situation, the following issues occur:

  • When you right-click the resource in the Available Storage area, an empty dialog box appears.
  • When you left-click and then right-click the resource in the Available Storage area, the options in the right-hand pane are not displayed. For example, the Bring Online, Bring Offline, and Properties options are not displayed.

This issue occurs because the failover cluster filters out the third-party storage resources, and the third-party storage resources are categorized as Other Resources.

To resolve these issues, install the hotfix together with the hotfixes that are described in Microsoft Knowledge Base (KB) article 2795993 and 2796000

KB2796000 You cannot create a cluster file share on a third-party disk resource in Windows Server 2012

Consider the following scenario:

  • You create a Windows Server 2012-based failover cluster by using third-party disk resources.
  • You configure a File Server service resource in the Failover Cluster Management snap-in.
  • You try to add a cluster file share in the File Server service resource.

In this scenario, the following issues occur:

  • You cannot create the cluster file share by using the Add File Share shortcut menu.
    Note If the Add File Share shortcut menu does not start, install the hotfix that is described in Microsoft Knowledge Base (KB) article 2795993 to resolve this issue.
  • When you try to create the cluster file share by using File Explorer, a Server Message Block (SMB) share is created instead of a cluster file share on the volume. For example, assume that you try to create a cluster file share that is named " ContosoShare" by using File Explorer on a drive named "ThirdPartyDisk" by using the following configuration:
    Cluster Name: ContosoCluster
    Cluster File server resource: \ContosoFileShare
    Thirdparty storage resource that \ContosoFileShare depends on: ThirdPartyDisk
    Server/Node Name: ContosoClusterNode1
    Share Name: ContosoShare
    In this situation, the file share is accessed through the "\ContosoClusterNode1ContosoShare" path instead of the "\ContosoFileShareContosoShare" path.
  • You cannot create the cluster file share by using the NetShare API or a Windows PowerShell command. Additionally, you receive an error message that resembles the following:

    System error 87 – The parameter is incorrect

This issue occurs because the Windows Server 2012-based failover cluster does not correctly determine the third-party disk to be a cluster disk.

To resolve these issues, install the hotfix together with the hotfixes that are described in Microsoft Knowledge Base (KB) article 2795997 and 2795993.

KB2795993 New Share Wizard does not start when you try to create a cluster file share on a third-party disk resource in Windows 8 or Windows Server 2012

Consider the following scenario:

  • You create a Windows Server 2012-based failover cluster by using third-party disk resources.
  • You configure a File Server service resource in the Failover Cluster Management snap-in.
  • You try to add a cluster file share to the File Server service resource by using the Add File Share shortcut menu or theActions pane. 

In this scenario, the following issues occur:

  • The New Share Wizard does not start from either the shortcut menu or the Actions pane.
  • You cannot create the cluster file share by using a Windows PowerShell command, the NetShare API, or File Explorer. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:

    2796000 You cannot create a cluster file share on a third-party disk resource in Windows Server 2012

This issue occurs because the Failover Cluster Management snap-in in Windows Server 2012 assumes an incorrect order of the resources in the File Server role.

To resolve these issues, install the hotfix on a Windows Server 2012-based cluster node or on a Windows 8-based computer that has the Remote Server Administration Tools for Windows 8 installed. Additionally, install the hotfixes that are described in KB KB 2795997 and 2796000 to resolve all the related issues

No Comment.

Add Your Comment

Get Adobe Flash player