Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2012-11-19
Use the Remove-RoleAssignmentPolicy cmdlet to remove an existing management role assignment policy from a server running Microsoft Exchange Server 2010.
Syntax
Remove-RoleAssignmentPolicy -Identity
<MailboxPolicyIdParameter> [-Confirm
[<SwitchParameter>]] [-DomainController <Fqdn>]
[-WhatIf [<SwitchParameter>]]
|
Detailed Description
The assignment policy you want to remove can't be assigned to any mailboxes or management roles. Also, if you want to remove the default assignment policy, it must be the last assignment policy. Do the following before you attempt to remove an assignment policy:
- Use the Set-Mailbox cmdlet to change the assignment
policy for any mailbox that's assigned the assignment policy you
want to remove.
- If the assignment policy is the default assignment policy, use
the Set-RoleAssignmentPolicy cmdlet to select a new default
assignment policy. You don't need to do this if you're removing the
last assignment policy.
- Use the Remove-ManagementRoleAssignment cmdlet to remove
any management role assignments assigned to the policy.
For more information about assignment policies, see Understanding Management Role Assignment Policies.
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 "Assignment policies" entry in the Role Management Permissions topic.
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Identity |
Required |
Microsoft.Exchange.Configuration.Tasks.MailboxPolicyIdParameter |
The Identity parameter specifies the assignment policy to remove. If the assignment policy name has 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. |
|
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. |
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 assignment policy called "End User Policy". First, find all of the mailboxes assigned the assignment policy.
 Copy Code |
|
|---|---|
Get-Mailbox | Where {$_.RoleAssignmentPolicy -Eq "End User Policy"}
|
|
Next, use the list you gathered to assign each mailbox a new assignment policy. You may want to assign all the mailboxes the same new assignment policy, such as Seattle End User Policy.
| Copy Code |
|
|---|---|
Get-Mailbox | Where {$_.RoleAssignmentPolicy -Eq "End User Policy"} | Set-Mailbox -RoleAssignmentPolicy "Seattle End User Policy"
|
|
Then, remove all the management role assignments assigned to the assignment policy.
| Copy Code |
|
|---|---|
Get-ManagementRoleAssignment -RoleAssignee "End User Policy" | Remove-ManagementRoleAssignment |
|
Finally, remove the assignment policy.
| Copy Code |
|
|---|---|
Remove-RoleAssignmentPolicy "End User Policy" |
|
For more information about the Where cmdlet and pipelining, see Working with Command Output and Pipelining.