Add-PublicFolderAdministrativePermission

This cmdlet is available only in Exchange Server 2010. This cmdlet is available only in on-premises Exchange Server 2010. Use the Add-PublicFolderAdministrativePermission cmdlet to add administrative permissions to a public folder or a public folder hierarchy. For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).

Syntax

Add-PublicFolderAdministrativePermission
   [-Identity] <PublicFolderIdParameter>
   -AccessRights <MultiValuedProperty>
   -User <SecurityPrincipalIdParameter>
   [-Confirm]
   [-Deny]
   [-DomainController <Fqdn>]
   [-InheritanceType <None | All | Descendents | SelfAndChildren | Children>]
   [-Server <ServerIdParameter>]
   [-WhatIf]
   [<CommonParameters>]
Add-PublicFolderAdministrativePermission
   [[-Identity] <PublicFolderIdParameter>]
   [-AccessRights <MultiValuedProperty>]
   -Instance <PublicFolderAdministrativeAceObject>
   [-User <SecurityPrincipalIdParameter>]
   [-Confirm]
   [-Deny]
   [-DomainController <Fqdn>]
   [-InheritanceType <None | All | Descendents | SelfAndChildren | Children>]
   [-Server <ServerIdParameter>]
   [-WhatIf]
   [<CommonParameters>]
Add-PublicFolderAdministrativePermission
   [-Identity] <PublicFolderIdParameter>
   -Owner <SecurityPrincipalIdParameter>
   [-Confirm]
   [-DomainController <Fqdn>]
   [-Server <ServerIdParameter>]
   [-WhatIf]
   [<CommonParameters>]

Description

You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).

Examples

-------------------------- Example 1 --------------------------

Add-PublicFolderAdministrativePermission -User Chris -Identity \MyPublicFolder -AccessRights ViewInformationStore

This example grants the user Chris the ViewInformationStore permission on the public folder MyPublicFolder.

-------------------------- Example 2 --------------------------

Add-PublicFolderAdministrativePermission -User Chris -Identity \MyPublicFolder -AccessRights ViewInformationStore -Deny

This example denies the user Chris the ViewInformationStore permission.

Required Parameters

-AccessRights

The AccessRights parameter specifies the rights that are being added. Valid values include:

  • None The administrator has no rights to modify public folder attributes.

  • ModifyPublicFolderACL The administrator has the right to modify client access permissions for the specified folder.

  • ModifyPublicFolderAdminACL The administrator has the right to modify administrator permissions for the specified public folder.

  • ModifyPublicFolderDeletedItemRetention The administrator has the right to modify the Public Folder Deleted Item Retention attributes (RetainDeletedItemsFor and UseDatabaseRetentionDefaults).

  • ModifyPublicFolderExpiry The administrator has the right to modify the Public Folder Expiration attributes (AgeLimit and UseDatabaseAgeDefaults).

  • ModifyPublicFolderQuotas The administrator has the right to modify the Public Folder Quota attributes (MaxItemSize, PostQuota, PostWarningQuota, and UseDatabaseQuotaDefaults)

  • ModifyPublicFolderReplicaList The administrator has the right to modify the replica list attribute for the specified public folder (Replicas).

  • AdministerInformationStore The administrator has the right to modify all other public folder properties that aren't defined previously.

  • ViewInformationStore The administrator has the right to view public folder properties.

  • AllExtendedRights The administrator has the right to modify all public folder properties.

Type:MultiValuedProperty
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010
-Identity

The Identity parameter specifies the GUID or public folder name that represents a specific public folder. You can also include the path using the format TopLevelPublicFolder\PublicFolder.

You can omit the parameter label so that only the public folder name or GUID is supplied.

Type:PublicFolderIdParameter
Position:1
Default value:None
Accept pipeline input:True
Accept wildcard characters:False
Applies to:Exchange Server 2010
-Instance

The Instance parameter specifies whether to pass an entire object to the command to be processed. It's mainly used in scripts where an entire object must be passed to the command.

Type:PublicFolderAdministrativeAceObject
Position:Named
Default value:None
Accept pipeline input:True
Accept wildcard characters:False
Applies to:Exchange Server 2010
-Owner

The Owner parameter specifies the NT Owner access control list (ACL) on the object. Valid values are the user principal name (UPN), domain\user, or alias.

Type:SecurityPrincipalIdParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010
-User

The User parameter specifies the UPN, domain\user, or alias of the user for whom rights are being added.

Type:SecurityPrincipalIdParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010

Optional Parameters

-Confirm

The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.

  • Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.

  • Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.

Type:SwitchParameter
Aliases:cf
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010
-Deny

The Deny switch specifies whether to deny the permission specified. You don't need to specify a value with this switch.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010
-DomainController

The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.

Type:Fqdn
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010
-InheritanceType

The InheritanceType parameter specifies the type of inheritance. Valid values are:

  • None

  • All

  • Descendents

  • SelfAndChildren

  • Children

Type:None | All | Descendents | SelfAndChildren | Children
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010
-Server

The Server parameter specifies the Exchange server where you want to run this command. You can use any value that uniquely identifes the server. For example:

  • Name

  • FQDN

  • Distinguished name (DN)

  • Exchange Legacy DN

If you don't use this parameter, the command is run on the local server.

Type:ServerIdParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010
-WhatIf

The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.

Type:SwitchParameter
Aliases:wi
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Exchange Server 2010

Inputs

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types (https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.

Outputs

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types (https://go.microsoft.com/fwlink/p/?LinkId=616387). If the Output Type field is blank, the cmdlet doesn't return data.