Consider the following scenario:
- You create a Windows Server 2012-based failover cluster and are using third-party dynamic 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.
- 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 "\\ContosoClusterNode1\ContosoShare" path instead of the "\\ContosoFileShare\ContosoShare" 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