How do I configure permissions for a cluster share using Powershell on 2008?
Posted
by
Andrew J. Brehm
on Server Fault
See other posts from Server Fault
or by Andrew J. Brehm
Published on 2012-08-06T14:07:35Z
Indexed on
2012/09/04
9:40 UTC
Read the original article
Hit count: 402
I have a cluster resource of type "file share" but when I try to configure the "security" parameter I get the following error (excerpt):
Set-ClusterParameter : Parameter 'security' does not exist on the cluster object
Using cluster.exe I get a better result, namely the usual nothing when the command worked. But when I check in Failover Cluster Manager the permissions have not changed. In Server 2003 the cluster.exe method worked.
Any ideas?
Update:
Entire command and error.
PS C:\> $resource=get-clusterresource testshare
PS C:\> $resource
Name State Group ResourceType
---- ----- ----- ------------
testshare Offline Test File Share
PS C:\> $resource|set-clusterparameter security "domain\account,grant,f"
Set-ClusterParameter : Parameter 'security' does not exist on the cluster object 'testshare'. If you are trying to upda
te an existing parameter, please make sure the parameter name is specified correctly. You can check for the current par
ameters by passing the .NET object received from the appropriate Get-Cluster* cmdlet to "| Get-ClusterParameter". If yo
u are trying to update a common property on the cluster object, you should set the property directly on the .NET object
received by the appropriate Get-Cluster* cmdlet. You can check for the current common properties by passing the .NET o
bject received from the appropriate Get-Cluster* cmdlet to "| fl *". If you are trying to create a new unknown paramete
r, please use -Create with this Set-ClusterParameter cmdlet.
At line:1 char:31
+ $resource|set-clusterparameter <<<< security "domain\account,grant,f"
+ CategoryInfo : NotSpecified: (:) [Set-ClusterParameter], ClusterCmdletException
+ FullyQualifiedErrorId : Set-ClusterParameter,Microsoft.FailoverClusters.PowerShell.SetClusterParameterCommand
© Server Fault or respective owner