Remove-CMSecurityRole

Module:

ConfigurationManager Module

Remove a custom security role.

Remove-CMSecurityRole
 -InputObject <IResultObject>
 [-Force]
 [-DisableWildcardHandling]
 [-ForceWildcardHandling]
 [-WhatIf]
 [-Confirm]
 [<CommonParameters>]

Remove-CMSecurityRole
 -Id <String>
 [-Force]
 [-DisableWildcardHandling]
 [-ForceWildcardHandling]
 [-WhatIf]
 [-Confirm]
 [<CommonParameters>]

Remove-CMSecurityRole
 -Name <String>
 [-Force]
 [-DisableWildcardHandling]
 [-ForceWildcardHandling]
 [-WhatIf]
 [-Confirm]
 [<CommonParameters>]

Use this cmdlet to remove a custom security role from Configuration Manager. Specify the name or ID of a security role you want to remove or use the Get-CMSecurityRole cmdlet to get one.

You can use the Remove-CMSecurityRole cmdlet to remove old, unneeded custom security roles. You can't remove built-in security roles. Every administrative user must have at least one security role. Before you remove a security role, make sure every user has a role in addition to the one you remove.

For more information on security roles and permissions, see Fundamentals of role-based administration in Configuration Manager.

This command removes a security role named MainSecurityRole. The command uses the Force parameter, so it doesn't prompt you for confirmation.

Remove-CMSecurityRole -Name "MainSecurityRole" -Force

The first command uses the Get-CMSecurityRole cmdlet to get all security roles that start with Custom, and stores them in the $role variable.

The second command removes the first security role stored in the array. Since it doesn't specify the Force parameter, this command prompts for confirmation.

$role = Get-CMSecurityRole -Name "Custom*"
Remove-CMSecurityRole -InputObject $role[1]

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.