Export (0) Print
Expand All

Set-AvailabilityConfig

Applies to: Exchange Server 2010

Topic Last Modified: 2011-03-19

Use the Set-AvailabilityConfig cmdlet to set the access level for free/busy information.


Set-AvailabilityConfig [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-OrgWideAccount <SecurityPrincipalIdParameter>] [-PerUserAccount <SecurityPrincipalIdParameter>] [-WhatIf [<SwitchParameter>]]

Parameter Required Type Description

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.

OrgWideAccount

Optional

Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter

The OrgWideAccount parameter specifies an account or security group that has permission to issue proxy Availability service requests on an organization-wide basis.

PerUserAccount

Optional

Microsoft.Exchange.Configuration.Tasks.SecurityPrincipalIdParameter

The PerUserAccount parameter specifies an account or security group that has permission to issue proxy Availability service requests on a per-user basis.

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.

The Set-AvailabilityConfig cmdlet defines two accounts or security groups: a per-user free/busy proxy account or group, and an organization-wide free/busy proxy account or group. These accounts and groups are trusted by all availability services in the current organization for availability proxy requests.

For cross-forest availability services to retrieve free/busy information in the current forest, they must be using one of the specified accounts, belong to one of the specified security groups, or have a user name and password for one of the specified accounts or security groups.

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 "Availability configuration settings" entry in the Client Access Permissions topic.

Error Description

Exceptions Description

This example is useful with a trusted cross-forest Availability service. If the remote forest is trusted, and a per-user free/busy proxy account or group in the remote forest is configured to use the service account, the configuration is added to the current forest to authorize the Microsoft ActiveSync request from the remote forest.

Set-AvailabilityConfig -PerUserAccount <domain name of servers group in remote forest>

This example is useful if the remote forest isn't trusted. Because this account is used for a cross-forest free/busy proxy account or group, minimize security vulnerabilities by using the credentials of a user who doesn't have an Exchange mailbox. When you're prompted, type the user name and password.

Set-AvailabilityConfig -OrgWideAccount <ExampleCredentials>
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft