Creating multiple File Server resources in one group may not work correctly in a Windows Server 2012 Failover Cluster
Assume you create multiple File Server resources which belong to the same cluster group in a Windows Server 2012 Failover Clustering. If more than one File Server resource is dependent to the same client access point (CAP), the File Server resources interfere with each other and some file shares are not unexpectedly available from SMB clients.
More specifically, file shares that can be seen from SMB clients are always dependent to the last File Server resource brought online. Therefore, some file shares may disappear due to this behavior.
- Issue which is descried above does not happens if File Server resources are dependent to each individual CAP.
- Creating multiple File Server resources in the same cluster group in Windows Server 2008 or in Windows Server 2008 R2 works correctly.
Because of a design change in Windows Server 2012, only one File Server resource can exist in each cluster group. Thus, you should not put multiple File Server resources into the same CAP when you create file shares. This differs from Windows Server 2008 and Windows Server 2008 R2, in which a File Server resource is created for each disk when a file share is added to a disk resource.
Article ID: 2993295 - Last Review: 01/29/2016 17:55:00 - Revision: 5.0
Windows Server 2012 Datacenter, Windows Server 2012 Standard, Windows Server 2012 Foundation, Windows Server 2012 Essentials
- kbexpertiseadvanced kbsurveynew kbprb KB2993295