Configure Resource Mailbox to AutoAccept in Exchange 2007

To configure a resource mailbox to automatically accept an appointment in Exchange 2007, you must use the Exchange management shell.

If there is already an appointment that overlaps at all with the appointment you are trying to schedule, you will get back a ‘Declined’ receipt from the resource mailbox.

Assuming you already have the mailbox created, and it is called “ResourceMailboxName”, here is the command you should run:

Set-MailboxCalendarSettings ResourceMailboxName -AutomateProcessing:AutoAccept

See these pages for more info on resource mailboxes:

Grant access to resource mailbox in Exchange 2007

To grant access to a resource mailbox, you must use the Exchange management shell.

Assuming you already have the mailbox created, and it is called “ResourceMailboxName”, here is the command you should run:

Add-MailboxPermission -AccessRights FullAccess -Identity ResourceMailboxName -User Username

If you need to grant a different level of permission, use a different option with the ‘AccessRights’ switch.  The other options are:

  • ChangePermission
  • ChangeOwner
  • DeleteItem
  • ExternalAccount
  • ReadPermission
  • SendAs

See these pages for more information on resource mailboxes:

Free/Busy info not available outside the network

If you are having problems with free/busy information in Outlook, it is most likely due to misconfiguration of the Exchange 2007 Autodiscover service.

The Autodiscover service provides info to the Availability service, such as the addresses (internal and external) that Outlook 2007 clients should use to connect to Exchange.  More info here.

I would recommend that you read this post at the Microsoft Exchange Team blog and the referenced whitepaper at the top.

Most likely, you do not have the internal/external addresses configured correctly in Exchange.  Double-check these.  In addition, with Outlook open, you can hold the ctrl key and right-click on the Outlook icon in your system tray to get the “Test Email Autoconfiguration” option.  Run this to see how Outlook is trying to connect to your Exchange server.  You may notice that Outlook first tries to connect to “”, then to “”.  These are the default addresses that Outlook tries.  You may need to create a CNAME for “” which points to your Exchange proxy address.  That is the address that you have in the Exchange proxy connection settings in Outlook, and is likely the same as your OWA address.

Once you have the Autodiscover/Availability services configured correctly, you will likely find that your free/busy info problems have been resolved.

Setting Client Permissions on Exchange 2007 Public Folders

By ‘public folder’, I mean any of the objects you see in your folder list in Outlook underneath “All Public Folders”.  It can be a calendar, contact list, task list, among others.

The best, easiest way to manage permissions on public folders in Exchange is through Outlook.  However, getting it set up so you can do that is not the most intuitive process.

To be able to set permissions on a public folder, you must be the owner of it.  Even if you are a domain/enterprise/schema admin, if you don’t own the public folder, you will not be able to modify the permissions of the folder via Outlook.  You must give your account ownership of the public folder first.  The way to do that is through the Exchange Management Shell.

Here is the command you will need to run:

Add-PublicFolderClientPermission -Identity <PublicFolder> -User “Username” -AccessRights <Right>

And for example, let’s say you have a calendar called “Company Calendar” directly under ‘All Public Folders’, and you want to give ownership of it to John Doe (username ‘jdoe’).  The command would be:

Add-PublicFolderClientPermission -Identity “\Company Calendar” -User “jdoe” -AccessRights Owner

and if, underneath All Public Folders, the company calendar is in another folder called Calendars, you would run the following instead:

Add-PublicFolderClientPermission -Identity “\Calendars\Company Calendar” -User “jdoe” -AccessRights Owner

There are other permissions you can set besides ‘Owner’, such as ‘Publishing Editor’, etc., with this command.  However, if your goal is to be able to manage the PF permissions from Outlook, just give ownership with this command then go to Outlook to set the remaining permissions.

Here is an article on Technet for more information on configuring public folder permissions:

Supporting Exchange 2007 on Windows Server 2008 R2

While it was previously announced that Exchange 2007 would not be supported on Windows Server 2008 R2, that decision has been reversed and support for this combination will be forthcoming.

According to this post, at the Microsoft Exchange Team Blog:

We always talk about listening to customers and sometimes this is written off by many as ‘marketing speak’.  In fact, we do take feedback seriously and no input is more important to our engineering processes than your voice.

Earlier this year we made a decision in one direction, and due to the feedback we have received on this blog and elsewhere, we have reconsidered.  In the coming calendar year we will issue an update for Exchange 2007 enabling full support of Windows Server 2008 R2.  We heard from many customers that this was important for streamlining their operations and reducing administrative challenges, so we have changed course and will add R2 support.  We are still working through the specifics and will let you know once we have more to share on the timing of this update.

So, keep the feedback coming.  We are listening.

Kevin Allison
GM Exchange Customer Experience

Posted via email from Aaron Johnstone