Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2012-11-19

Use the New-ManagementScope cmdlet to create a regular or exclusive management scope.

Syntax


`New-ManagementScope -Name <String> -RecipientRestrictionFilter <String> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Exclusive <SwitchParameter>] [-Force <SwitchParameter>] [-Organization <OrganizationIdParameter>] [-RecipientRoot <OrganizationalUnitIdParameter>] [-WhatIf [<SwitchParameter>]]`


`New-ManagementScope -Name <String> -ServerRestrictionFilter <String> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Exclusive <SwitchParameter>] [-Force <SwitchParameter>] [-Organization <OrganizationIdParameter>] [-WhatIf [<SwitchParameter>]]`


`New-ManagementScope -Name <String> -ServerList <ServerIdParameter[]> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Exclusive <SwitchParameter>] [-Force <SwitchParameter>] [-Organization <OrganizationIdParameter>] [-WhatIf [<SwitchParameter>]]`


`New-ManagementScope -Name <String> -DatabaseList <DatabaseIdParameter[]> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Exclusive <SwitchParameter>] [-Force <SwitchParameter>] [-Organization <OrganizationIdParameter>] [-WhatIf [<SwitchParameter>]]`


`New-ManagementScope -Name <String> -DatabaseRestrictionFilter <String> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Exclusive <SwitchParameter>] [-Force <SwitchParameter>] [-Organization <OrganizationIdParameter>] [-WhatIf [<SwitchParameter>]]`


`New-ManagementScope -Name <String> -PartnerDelegatedTenantRestrictionFilter <String> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Organization <OrganizationIdParameter>] [-WhatIf [<SwitchParameter>]]`

Detailed Description

After you create a regular or exclusive scope, you need to associate the scope with a management role assignment. To associate a scope with a role assignment, use the New-ManagementRoleAssignment cmdlet. For more information about adding new management scopes, see Create a Regular or Exclusive Scope.

Important:
Microsoft Exchange Server 2010 Service Pack 1 (SP1) introduces database scopes. Database scopes are only enforced on servers running Exchange 2010 SP1. If a user connects to a server running the release to manufacturing (RTM) version of Exchange 2010, management role assignments associated with database scopes aren't applied. Also, database scopes aren't visible to the Get-ManagementScope cmdlet when it's run on an Exchange 2010 RTM server.

Important:

Microsoft Exchange Server 2010 Service Pack 1 (SP1) introduces database scopes. Database scopes are only enforced on servers running Exchange 2010 SP1. If a user connects to a server running the release to manufacturing (RTM) version of Exchange 2010, management role assignments associated with database scopes aren't applied. Also, database scopes aren't visible to the Get-ManagementScope cmdlet when it's run on an Exchange 2010 RTM server.

For more information about regular and exclusive scopes, see Understanding Management Role Scopes.

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 scopes" entry in the Role Management Permissions topic.

Parameters

Parameter

Required

Type

Description

DatabaseList

Required

Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter[]

The DatabaseList parameter specifies a list of databases to which the scope should be applied. Multiple databases can be specified, separated by commas. If you use the DatabaseList parameter, you can't use the DatabaseRestrictionFilter, ServerList, RecipientRestrictionFilter, RecipientRoot, or ServerRestrictionFilter parameters.

DatabaseRestrictionFilter

Required

System.String

The DatabaseRestrictionFilter parameter specifies the filter to apply to database objects. Only database objects that match the filter are included in the scope. If you use the DatabaseRestrictionFilter parameter, you can't use the RecipientRestrictionFilter, ServerRestrictionFilter, RecipientRoot, DatabaseList, or ServerList parameters. For a list of filterable database properties, see Understanding Management Role Scopes.

Name

Required

System.String

The Name parameter specifies the name of the management scope. The name can be up to 64 characters. If the name contains spaces, enclose the name in quotation marks (").

PartnerDelegatedTenantRestrictionFilter

Required

System.String

This parameter is reserved for internal Microsoft use.

RecipientRestrictionFilter

Required

System.String

The RecipientRestrictionFilter parameter specifies the filter to apply to recipient objects. Only recipient objects that match the filter are included in the scope. If you use the RecipientRestrictionFilter parameter, you can't use the DatabaseRestrictionFilter, DatabaseList, ServerList, or ServerRestrictionFilter parameters. For a list of filterable properties, see Filterable Properties for the -Filter Parameter.

ServerList

Required

Microsoft.Exchange.Configuration.Tasks.ServerIdParameter[]

The ServerList parameter specifies a list of servers to which the scope should be applied. Multiple servers can be specified, separated by commas. If you use the ServerList parameter, you can't use the RecipientRestrictionFilter, RecipientRoot, DatabaseRestrictionFilter, DatabaseList, or ServerRestrictionFilter parameters.

ServerRestrictionFilter

Required

System.String

The ServerRestrictionFilter parameter specifies the filter to apply to server objects. Only server objects that match the filter are included in the scope. If you use the ServerRestrictionFilter parameter, you can't use the RecipientRestrictionFilter, RecipientRoot, DatabaseRestrictionFilter, DatabaseList, or ServerList parameters. For a list of filterable server properties, see Understanding Management Role Scopes.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

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.

Exclusive

Optional

System.Management.Automation.SwitchParameter

The Exclusive switch specifies that the role should be an exclusive scope.

Caution:
When you create exclusive management scopes, only users or universal security groups (USG) assigned exclusive scopes that contain objects to be modified can access those objects. Users or USGs that aren't assigned an exclusive scope that contains the objects immediately lose access to those objects.

Force

Optional

System.Management.Automation.SwitchParameter

The Force switch specifies that an exclusive scope should be created without showing the warning that the exclusive scope takes effect immediately.

Organization

Optional

Microsoft.Exchange.Configuration.Tasks.OrganizationIdParameter

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 Organization parameter specifies the organization in which you'll perform this action. This parameter doesn't accept wildcard characters, and you must use the exact name of the organization.

RecipientRoot

Optional

Microsoft.Exchange.Configuration.Tasks.OrganizationalUnitIdParameter

The RecipientRoot parameter specifies the organizational unit (OU) under which the filter specified with the RecipientRestrictionFilter parameter should be applied. If you use the RecipientRoot parameter, you can't use the DatabaseRestrictionFilter, DatabaseList, ServerList, or ServerRestrictionFilter parameters.

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 creates a scope that includes only the servers HubServer1, HubServer2, and HubServer3. Users assigned roles using management role assignments that have the scope in this example can only perform against the servers included in the scope.

	Copy Code
New-ManagementScope -Name "Hub Servers 1 through 3" -ServerList HubServer1, HubServer2, HubServer3

EXAMPLE 2

This example creates the Redmond Site Scope scope and sets a server restriction filter that matches only the servers located in the "CN=Redmond,CN=Sites,CN=Configuration,DC=contoso,DC=com" Active Directory Domain Services (AD DS) site.

	Copy Code
New-ManagementScope -Name "Redmond Site Scope" -ServerRestrictionFilter {ServerSite -eq "CN=Redmond,CN=Sites,CN=Configuration,DC=contoso,DC=com"}

EXAMPLE 3

This example creates the Executive Mailboxes scope. Only mailboxes located within the Executives OU in the contoso.com domain match the recipient restriction filter.

	Copy Code
New-ManagementScope -Name "Executive Mailboxes" -RecipientRoot "contoso.com/Executives" -RecipientRestrictionFilter {RecipientType -eq "UserMailbox"}

EXAMPLE 4

This example creates the Protected Exec Users exclusive scope. Users that contain the string "VP" in their title match the recipient filter for the scope. When the exclusive scope is created, all users are immediately blocked from modifying the recipients that match the exclusive scope until the scope is associated with a management role assignment. If other role assignments are associated with other exclusive scopes that match the same recipients, those assignments can still modify the recipients.

	Copy Code
New-ManagementScope -Name "Protected Exec Users" -RecipientRestrictionFilter { Title -Like "VP" } -Exclusive

The exclusive scope is then associated with a management role assignment that assigns the Mail Recipients management role to the Executive Administrators role group. This role group contains administrators who are allowed to modify the mailboxes of high-profile executives. Only the administrators of the Executive Administrators role group can modify users with the string "VP" in their title.

	Copy Code
New-ManagementRoleAssignment -Name "Executive Administrators_Mail Recipients" -SecurityGroup "Executive Administrators" -Role "Mail Recipients" -CustomRecipientWriteScope "Protected Exec Users"

EXAMPLE 5

This example creates the Seattle Databases scope and sets a database restriction filter that matches only the databases that begin with the string "SEA".

	Copy Code
New-ManagementScope -Name "Seattle Databases" -DatabaseRestrictionFilter {Name -Like "SEA*" }