-
Notifications
You must be signed in to change notification settings - Fork 107
SPShellAdmins
Parameter | Attribute | DataType | Description | Allowed Values |
---|---|---|---|---|
IsSingleInstance | Key | String | Specifies the resource is a single instance, the value must be 'Yes' | Yes |
Members | Write | StringArray[] | Exact list of accounts that will have to get Shell Admin permissions | |
MembersToInclude | Write | StringArray[] | List of all accounts that must be in the Shell Admins group | |
MembersToExclude | Write | StringArray[] | List of all accounts that are not allowed to have Shell Admin permissions | |
Databases | Write | MSFT_SPDatabasePermissions[] | Shell Admin configuration of Databases | |
AllDatabases | Write | Boolean | Specify if all databases must get the same config as the general config | |
ExcludeDatabases | Write | StringArray[] | Specify all databases that must be excluded from AllDatabases |
Parameter | Attribute | DataType | Description | Allowed Values |
---|---|---|---|---|
Name | Key | String | Name of the Database | |
Members | Write | StringArray[] | Exact list of accounts that will have to get Shell Admin permissions | |
MembersToInclude | Write | StringArray[] | List of all accounts that must be in the Shell Admins group | |
MembersToExclude | Write | StringArray[] | List of all accounts that are not allowed to have Shell Admin permissions |
Type: Distributed Requires CredSSP: No
This resource is used to manage the users with Shell Admin permissions. There are a number of approaches to how this can be implemented. The "Members" property will set a specific list of members for the group, making sure that every user/group in the list is in the group and all others that are members and who are not in this list will be removed. The "MembersToInclude" and "MembersToExclude" properties will allow you to control a specific set of users to add or remove, without changing any other members that are in the group already that may not be specified here, allowing for some manual management outside of this configuration resource. The "ContentDatabases" and "AllContentDatabases" properties will allow you to control the permissions on Content Databases.
Requirements:
- At least one of the Members, MemberToInclude or MembersToExclude properties needs to be specified.
- Do not combine the Members property with the MemberToInclude and MembersToExclude properties.
- Do not combine the ContentDatabase property with the AllContentDatabases property.
Required permissions:
The documentation of the Shell Admin cmdlets states that you need the following permissions to successfully run this resource:
"When you run this cmdlet to add a user to the SharePoint_Shell_Access role, you must have membership in the securityadmin fixed server role on the SQL Server instance, membership in the db_owner fixed database role on all affected databases, and local administrative permission on the local computer."
and
"This cmdlet is intended only to be used with a database that uses Windows authentication. There is no need to use this cmdlet for databases that use SQL authentication; in fact, doing so may result in an error message."
Notes:
- In some instances the Farm account has been configured as the owner of a SharePoint database. When that is the case, SharePoint is unable to add the Farm account as a Shell Admin. We have implemented a workaround for this issue, but it can mean some warnings are shown. The workaround for this issue is to change database owner in SQL and grant the Farm account permissions to the database directly and add the db_owner database role
This example gives admin access to the specified users for the local farm as well as all content databases in the local farm.
Configuration Example
{
param
(
[Parameter(Mandatory = $true)]
[PSCredential]
$SetupAccount
)
Import-DscResource -ModuleName SharePointDsc
node localhost
{
SPShellAdmins ShellAdmins
{
IsSingleInstance = "Yes"
Members = "CONTOSO\user1", "CONTOSO\user2"
AllDatabases = $true
}
}
}
This example gives admin access to the specified users for the local farm as well as all content databases in the local farm.
Configuration Example
{
param
(
[Parameter(Mandatory = $true)]
[PSCredential]
$SetupAccount
)
Import-DscResource -ModuleName SharePointDsc
node localhost
{
SPShellAdmins ShellAdmins
{
IsSingleInstance = "Yes"
Members = "CONTOSO\user1", "CONTOSO\user2"
Databases = @(
@(MSFT_SPDatabasePermissions {
Name = "SharePoint_Content_1"
Members = "CONTOSO\user2", "CONTOSO\user3"
})
@(MSFT_SPDatabasePermissions {
Name = "SharePoint_Content_2"
Members = "CONTOSO\user3", "CONTOSO\user4"
})
)
}
}
}
This example gives admin access to the specified users for the local farm as well as all content databases in the local farm, with the exception of database WSS_Content_Portal.
Configuration Example
{
param
(
[Parameter(Mandatory = $true)]
[PSCredential]
$SetupAccount
)
Import-DscResource -ModuleName SharePointDsc
node localhost
{
SPShellAdmins ShellAdmins
{
IsSingleInstance = "Yes"
Members = "CONTOSO\user1", "CONTOSO\user2"
AllDatabases = $true
ExcludeDatabases = "WSS_Content_Portal"
PsDscRunAsCredential = $SetupAccount
}
}
}
- Home
- Getting Started
- Pre-requisites
- Installing the module
- Exporting SharePoint Configuration
- Creating Configuration Files
- Pre-created Examples
- Creating an Azure development environment
- Understanding Resources & Syntax
- Remote PowerShell Authentication
- Contributing to SharePointDsc
- Other useful modules for SharePoint DSC configurations