Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2012-11-19
Use the Remove-ManagementRole cmdlet to remove custom management roles that you don't need anymore.
Syntax
Remove-ManagementRole -Identity <RoleIdParameter>
[-Confirm [<SwitchParameter>]] [-DomainController
<Fqdn>] [-Force <SwitchParameter>] [-Recurse
<SwitchParameter>] [-UnScopedTopLevel
<SwitchParameter>] [-WhatIf [<SwitchParameter>]]
|
Detailed Description
You need to remove all the management role assignments from a role before you delete it. If the role is the parent of child roles, the child roles must be removed before you remove the parent role, or you must use the Recurse parameter when you remove the parent role. You can only remove custom roles. Built-in roles, such as the Mail Recipients role, can't be removed. For more information about how to remove a custom role, see Remove a Role.
You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the "Management roles" entry in the Role Management Permissions topic.
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
|
Identity |
Required |
Microsoft.Exchange.Configuration.Tasks.RoleIdParameter |
The Identity parameter specifies the custom role to remove. If the name of the role contains spaces, enclose the name in quotation marks ("). |
||
|
Confirm |
Optional |
System.Management.Automation.SwitchParameter |
The Confirm switch can be used to suppress the
confirmation prompt that appears by default when this cmdlet is
run. To suppress the confirmation prompt, use the syntax
|
||
|
DomainController |
Optional |
Microsoft.Exchange.Data.Fqdn |
The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory. |
||
|
Force |
Optional |
System.Management.Automation.SwitchParameter |
This parameter is available for multi-tenant deployments. It isn't available for on-premises deployments. For more information about multi-tenant deployments, see Multi-Tenant Support. The Force switch specifies whether to suppress warning or confirmation messages. This switch can be used when the task is run programmatically and prompting for administrative input is inappropriate. If the Force switch isn't provided in the command, you're prompted for administrative input. You don't have to specify a value with this parameter. |
||
|
Recurse |
Optional |
System.Management.Automation.SwitchParameter |
The Recurse parameter removes all child roles of the role specified with the Identity parameter and then removes the specified role.
|
||
|
UnScopedTopLevel |
Optional |
System.Management.Automation.SwitchParameter |
The UnScopedTopLevel switch specifies that the role you're trying to remove is an unscoped top-level role. You must use this switch if you want to remove an unscoped top-level role. |
||
|
WhatIf |
Optional |
System.Management.Automation.SwitchParameter |
The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch. |
Caution:Input Types
To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.
Return Types
To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.
Examples
EXAMPLE 1
This example removes the single role ExampleRole1.
 Copy Code |
|
|---|---|
Remove-ManagementRole ExampleRole1 |
|
EXAMPLE 2
This example runs the Remove-ManagementRole cmdlet with the WhatIf switch. The WhatIf switch lets the command run as if it were going to perform the action you specified but doesn't commit any changes. Instead, it displays the results of what would have happened, so you can verify that the actions are correct.
| Copy Code |
|
|---|---|
Remove-ManagementRole ExampleRole2 -Recurse -WhatIf |
|
If the results are as expected, the following command
can be used to remove the ExampleRole2 parent role and
all its child roles.
| Copy Code |
|
|---|---|
Remove-ManagementRole ExampleRole2 -Recurse |
|
EXAMPLE 3
This example uses the Get-ManagementRole cmdlet to get a list of roles that contain the string "Example" in the role name and then pipes the list to the Remove-ManagementRole cmdlet. The Remove-ManagementRole cmdlet, because the WhatIf switch is specified, displays the roles that would have been removed but doesn't commit any changes. If the results are as expected, the command can be run again without the WhatIf switch to remove the roles.
| Copy Code |
|
|---|---|
Get-ManagementRole *Example* | Remove-ManagementRole -WhatIf |
|
EXAMPLE 4
This example removes the In-house scripts unscoped top-level management role. Because this is an unscoped top-level role, the UnScopedTopLevel switch must be used.
| Copy Code |
|
|---|---|
Remove-ManagementRole "In-house scripts" -UnScopedTopLevel |
|
For more information about unscoped top-level management roles, see Understanding Management Roles.