Skip to content

Posts from the ‘Exchange’ Category


Exchange 2010/2013 Co-Existence Experience

Now that Exchange 2010 SP3 and Exchange 2013 CU1 have both been released, co-existence between Exchange 2010 and Exchange 2013 can now be completed using a supported method.  Unfortunately, there are some scenario’s that can cause this migration to have a few problems.  I wanted to take a few minutes to post a few experiences I have had in this process; hopefully what we have learned will be helpful to others.

Read moreRead more


Exchange 2010 Update Rollups Fail

Update: This has been fixed in Exchange 2010 SP1 Rollup 3 (

We recently ran into an issue when trying to apply the latest rollups for Exchange 2010 SP1.  We never had this problem with the rollups on Exchange 2007.

What happens when the update fails, it rolls back, but it leaves all dependent services in a “Disabled” state (when it fails it does not reset its services back to the way they were, which is very bad).  To find out which services it changed, the easiest way is to look in the System Event Log and see which services were modified.

This issue occurs when you have the “PowerShell Execution Policy” defined in group policy.  You can find this policy in the Group Policy Management Editor under: Computer Configuration > Policies > Administrative Templates > Windows Components > Windows PowerShell > Turn on Script Execution.

The only workaround I could find is to temporarily disable your GPO that configures this policy on your Exchange server (or exclude your Exchange servers from the policy).  After the patch has completed successfully, the policy can (should) be re-applied.  Hopefully Microsoft will fix this for future rollups.


Room Mailboxes in Exchange 2007

When you setup a room account you create the account as a “room mailbox” in Exchange.  This is done in the Exchange Management Console (Recipient Configuration > Mailbox > New Mailbox…).

This creates a special AD account with special attributes.  These properties can be figured two ways.  First (recommended), through the Exchange Management Shell (powershell integration of Exchange).  Second is through OWA (this requires you granting yourself Full Mailbox Access to your regular account and then using the connect to mailbox feature in OWA to connect to the resource).  Once connected, in options, there is a resource setting page.

When managing with the Shell, you can use the “Set-MailboxCalendarSettings” cmdlet to manage resource mailboxes.  Here is a reference of the available parameters:

Here is a common example of using the command with a new resource mailbox:

Set-MailboxCalendarSettings conferenceroom100 -Automate Processing AutoAccept -DeleteSubject $False -DeleteComments $False -AllBookInPolicy $False -BookInPolicy:finance,hr

You can use the following cmdlet example to view all configured properties:

Get-MailboxCalendarSettings conferenceroom100 | fl

You can also convert existing mailboxes to room mailboxes using the following cmdlet example:

set-mailbox conferenceroom100 -Type Room

This last cmdlet example will report the current type of a mailbox, this is useful when verifying success of the above cmdlet

get-mailbox conferenceroom100 | select Name, IsResource

Once a mailbox is configured this way, you can book a resource in Exchange 2007 directly as a room.

Applies to: Exchange 2007