Creating shares under CAPs not working in Cluster 2012 R2
we have 6 node file server cluster running on windows 2012 r2. part of our migration legacy cluster, need retain old resources names. using client access points (caps) seems perfect fit this.
on 2012 r2 cluster, roles have been created using names not in use on legacy cluster (call 1 of them newrole1). storage, have created small root disks. call 1 of them newroot1. consider default cap. larger san disks mounted folders on root disk. each folder corresponds resource on legacy cluster. call 1 of these folders legacyres1.
i can create cap on 2012 cluster same name resource on legacy cluster (once delete old resource). @ point have 2 caps under role newrole1 - newroot1 , legacyres1. in failover cluster manager (fcm) can create number of shares available under newroot1 cap, when try create share under legacyres1 cap, wizard substitutes newroot1 instead, no way change it.
has encountered this? seems bug in 2012 r2 me, can't find on it.
this user error.
for else doing this: when click on "add file share", fcm asks cap want create share under. however, second screen of wizard (select server , path share) requires again select proper cap. if don't, share created under newroot1.
i've never liked wizards, less now. i'm looking powershell cmdlets perform these functions me.
Windows Server > File Services and Storage
Comments
Post a Comment