Applies to: Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

Topic Last Modified: 2015-03-09

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

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

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.

To run the Set-AvailabilityConfig cmdlet, the account you use must be delegated the following:

  • Exchange Organization Administrator role

For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.


Parameter Required Type Description




To specify the fully qualified domain name (FQDN) of the domain controller that retrieves data from the Active Directory directory service, include the DomainController parameter in the command.




The Instance parameter enables you to pass an entire object to the command to be processed. It is mainly used in scripts where an entire object must be passed to the command.




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




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




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




The WhatIf parameter instructs the command to simulate the actions that it would take on the object. By using the WhatIf parameter, 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 parameter.


Error Description


Exceptions Description

The first example of the Set-AvailabilityConfig command is useful with trusted cross-forest availability service. If the remote forest is trusted, and 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 ActiveSync request from the remote forest.

The second example of the Set-AvailabilityConfig command is useful if the remote forest is not trusted. When you are prompted, type the user name and password. 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 does not have an Exchange mailbox.

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

Community Additions