How to set Free/Busy permissions in Exchange Management Shell

This article describes how to add, change, and remove Free/Busy permissions

You can view or set Free/Busy permissions through the Exchange Management Shell. Use the following table to match Microsoft Outlook permissions with the access permissions that Microsoft Exchange Server uses.

Requested Outlook permissions Access rights
Free/Busy time AvailabilityOnly
Free/Busy time, subject, location LimitedDetails
Reviewer Reviewer
Nonediting Author NonEditingAuthor
Author Author
Publishing Author PublishingAuthor
Editor Editor
Publishing Editor PublishingEditor
Owner Owner

How to view Free/Busy permissions

To view current Free/Busy permissions, run the following cmdlet:

Note The <PrimarySMTP> placeholder represents the mailbox for which you want to view permissions.

For example, the cmdlet resembles the following:

How to add Free/Busy permissions

To add Free/Busy permissions, run the following cmdlet:

Notes

  • The <PrimarySMTP> placeholder represents the mailbox for which you want to change permissions.
  • The <UserSMTP> placeholder represents the user who is granted Free/Busy permissions.
  • The <AccessRights> placeholder represents the user permissions.
  • If you want to make the Free/Busy time viewable for nonspecific users, the AccessRights setting for the default user should be AvailabilityOnly or higher.

For example, the following cmdlet grants otheruser@contoso.com permission to view the calendar for user@contoso.com:

 

How to remove Free/Busy permissions

To remove Free/Busy permissions, run the following cmdlet:

Notes

  • The <PrimarySMTP> placeholder represents the mailbox for which you want to change permissions.
  • The <UserSMTP> placeholder represents the user who is granted Free/Busy permissions.

For example, the following cmdlet revokes permission for otheruser@contoso.com to view the calendar for user@contoso.com:

SMTP certificate renewal and EDGE subscription

1. Import new certificate
To import certificate to local certification store run:

2. Connect pending request to certificate
If step 1 failed to connect certificates together inside certification store run:

3. Enable new Exchange certificate for SMTP service
Before certificate can be used, it must have been enabled for particular services.

Result:

4. Restart transport service and AD LDS service
At this moment e-mail stop to flow to this EDGE server, because AD LDS is using new certificate and Edge is subscribed via old one.

5. Create subscription file (XML) on Edge server ans copy it to HUB server
We don´t need to create connectors for EDGE Subscription, since those are already created. EDGE must be subscribed to AD site within 24 hours after creation of subscription file.

Result:

6. Subscribe EDGE server on HUB by subscription file (XML).
We need to re-create trusted connection between Edge server and HUB servers. Subscription needs to be re-created, because AD LDS needs to use new certificate instead of old one. It is enough to subscribe each EDGE server once per subscription.

7. Restart EDGE server
Just to be sure all settings are applied before tests.

8. Test Edge Subscription
If the test is not successful you receive error.

Successful result:

9. Test mailflow

10. To start Edge synchronisation manually

Result:

TechNet Link: http://technet.microsoft.com/en-us/library/bb310755(v=exchg.80).aspx

 

 

 

Test post with Powershell code inside

This is test line of Powershell code inside a WordPress post

This is next line