I’ve seen this error around a few times over the last while but have never really paid too much attention to it:

It seems it only occurs in the management console if you have IE9 installed on your Exchange 2010 SP1 server. Previously the recommendation was to uninstall IE9 or just live with it. I recently installed Update Rollup 5 for Exchange 2010 SP1 in my lab environment and it seems to have fixed this error.

Obviously I would recommend thorough testing before deploying any updates in production, but I thought it would be worth mentioning that it does seem to fix this error as well.

I’ve been having a problem with remote mailbox moves to Office 365. The move completes successfully and everything works ok, but it always generates the following error:

“Could not load type 'Microsoft.Exchange.MailboxReplicationService.RequestPriority'…”

I’ve seen this mentioned a few times on the Office 365 community forums and some of my colleagues are also seeing this. The good news is that after installing Update Rollup 5 for Exchange 2010 SP1 this error no longer appears.

Earlier today the Exchange team announced the release of Update Rollup 5 for Exchange Server 2010 Service Pack 1. Update Rollup 5 for Exchange Server 2010 SP1 resolves the issues that are described in the following Microsoft Knowledge Base articles:

• 2275156 - The inline contents disposition is removed when you send a "Content-Disposition: inline" email message by using EWS in an Exchange Server 2010 environment
• 2499044 - You cannot save attachments in an email message by using OWA if the subject line contains special characters in an Exchange Server 2010 environment
• 2509306 - Journal reports are expired or lost when the Microsoft Exchange Transport service is restarted in an Exchange Server 2010 environment
• 2514766 - A RBAC role assignee can unexpectedly run the Add-ADPermission command on an Exchange Server 2010 server that is outside the role assignment scope
• 2529715 - Slow network or replication issues after you change the number of virus scanning API threads in Microsoft Exchange Server 2010
• 2536704 - Mailbox users who are migrated by using ILM 2007 cannot use the Options menu in OWA in an Exchange Server 2010 environment
• 2537094 - French translation errors occur when you edit a response to a meeting request by using OWA in an Exchange Server 2010 SP1 environment
• 2554604 - A RBAC role assignee can unexpectedly manage certificates that are outside the role assignment scope in an Exchange Server 2010 environment
• 2555800 - You cannot use the GetItem operation in EWS to retrieve properties of an email message in an Exchange Server 2010 environment
• 2555850 - You cannot delete a mailbox folder that starts with a special character in its name by using Outlook in an Exchange Server 2010 environment
• 2556096 - The columns in the .csv logging file are not lined up correctly when you perform a discovery search on a mailbox in an Exchange Server 2010 environment
• 2556107 - The columns in the .csv logging file are not lined up correctly when you perform a discovery search on a mailbox in an Exchange Server 2010 environment
• 2556133 - A device that uses Exchange ActiveSync cannot access mailboxes in an Exchange Server 2010 environment
• 2556156 - Extra.exe crashes when it performs RPC activity checks against an Exchange Server 2010 server
• 2556352 - "ChangeKey is required for this operation" error message in Outlook for Mac 2011 in an Exchange Server 2010 environment
• 2556407 - Certain client-only message rules do not take effect on email messages that are saved as drafts in an Exchange Server 2010 environment
• 2559926 - "There are no items to show in this view." error message when you try to view a folder by using Outlook in an Exchange Server 2010 environment
• 2572958 - The "Test-OutlookConnectivity -Protocol HTTP" command fails with an HTTP 401 error in an Exchange Server 2010 environment

For more information, click here

To Download, click here

Have you ever had to figure out what version of Exchange a build number is referring to or vice versa? There is a very handy TechNet article that lists every build number and release date since Exchange 4.0.837 (Exchange Server 4.0 Standard Edition, June 11 1996)

Bhargav Shukla also has a great script that can be used to find Exchange 2007 and Exchange 2010 build numbers in your environment.

It’s almost time to head to the Gold Coast for Tech-Ed 2011. I will be tweeting and blogging from the conference as usual. I will also be speaking this year so if you are attending, be sure to come over and say hi.

Microsoft’s Toby Knight and I will be presenting session EXL311 entitled “Microsoft Exchange and Microsoft Office 365: From Simple Migration to a Hybrid Environment”. Whether you’re looking to migrate all of your mailboxes to the cloud or planning to run a hybrid environment, this is the session for you. We will cover how and when to take advantage of the Simple Exchange Migration which supports migrating existing Exchange on-premise customers who want to move all of their mailboxes to the cloud with full data fidelity. You will also learn how rolling out an Exchange 2010 server in your current Exchange environment prepares you for seamless integration with Exchange Online. Whether you are piloting a few users or moving a large part of your workforce to the cloud, we give you the technical details on Exchange-to-cloud integration that you need to be successful.

The session is currently scheduled for Wed, 31 Aug at 5 PM. See you there!

During the month of June I was fortunate enough to attend the Microsoft Certified Master rotation at Microsoft in Redmond, Washington.

I am delighted to announce that after a very long month of waiting for the results of the final “qual lab”, I passed and have earned the Microsoft Certified Master | Exchange Server 2010 certification.

The MCM program differentiates itself through expert-led training. The curriculum is
developed in conjunction with Microsoft product engineering teams and delivered by industry-renowned instructors and practiced experts within their fields of discipline. Instructors use their numerous years of experience to ensure that students receive authoritative information on the successes and challenges of applying course concepts to real-world customer situations. I knew it would be challenging, but when day 1 ended up being 17 hours long we all knew we would be in for more than we could have ever imagined.

In order to successfully pass and be able to call yourself an MCM you need to get through 3 very difficult theory exams and then face the beast, otherwise known as the “qual lab”. Without going into it in too much detail, it is a very intense 3 weeks. How intense? read Bojan Nenadic’s Blog

I have to say thanks to all my rock star instructors and classmates.. I am humbled and truly grateful to have shared this experience with you all.

With the recent launch of Office365 I was very excited at the thought of moving my existing BPOS account to a new Office365 tenant. I signed up, removed my “cgoosen.com” domain from my BPOS account and went through the process of adding it to Office365. I thought the whole process was going really well until I tested it by sending myself an email from another external account. I immediately received a “550 5.4.1 Relay Access Denied” error which seemed a little strange. After some research on the Office365 Community forums I realised that this seems to be a common issue with people moving a domain from BPOS to Office365.

I ended up calling Microsoft Customer Support and after some trial and error here is how I fixed it.

The first thing you need to do is use PowerShell to connect to your Office365 tenant, make sure you have the correct versions of Windows PowerShell and Windows Remote Management (WinRM) installed and configured on your computer. If you are running Windows 7 or Windows Server 2008 R2, you don't have to install anything. If you are running anything else, see the link at the bottom of the post. By default, PowerShell’s execution policy is set to “Restricted” that means that scripts won’t run so before we try to connect, we need to change that. Open PowerShell and execute the following cmdlets:

Get-ExecutionPolicy – verify that it is set to “Restricted”

Lets change it to “RemoteSigned”. PowerShell will now run any scripts that you write yourself and scripts downloaded from the Internet only if those scripts have been signed by a trusted publisher:

Set-ExecutionPolicy RemoteSigned

Now we are ready to connect to our Office365 tenant. Execute the following cmdlets:

$LiveCred = Get-Credential

Enter your Office365 admin credentials in the dialog

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

Import-PSSession $Session

Once connected you, execute the following cmdlets:

Set-AcceptedDomain -Identity "yourdomain.com" -OutboundOnly $True

Set-AcceptedDomain -Identity "yourdomain.com" -OutboundOnly $False

You may need to allow around 40mins for replication, after that you should be able to receive mail again without the “550 5.4.1 Relay Access Denied” error.

If you are using running anything other than Windows 7 or Windows Server 2008 R2, see this link for information on Install and Configure Windows PowerShell.

For more information about connecting to Office365 via PowerShell, click here.

One of my favourite tools is the Exchange Server Deployment Assistant. The Deployment Assistant asks you some questions about your particular Exchange environment and, based on your answers, it provides a checklist with instructions that are designed to help you deploy Exchange 2010 quickly and easily. Each step has a huge amount of valuable information to guide you through your deployment.

The Exchange Team recently announced that they have updated the Deployment Assistant to include a rich coexistence scenario for organizations interested in maintaining some users on-premises with Exchange 2010 and some users hosted in the cloud by Microsoft Office 365 for enterprises. This information is only available in English at this time and requires Exchange Server 2010 Service Pack 1 (SP1).

The Exchange Server Deployment Assistant can be found here.

The Exchange Team are looking to learn a bit more about your public folder topologies and usage scenarios. They have created an anonymous survey that asks about things like usage scenarios, folder management habits or thought process around public folder data organization.

If you have 15 minutes to spare, I’m sure they will appreciate it! The survey can be found here.

I recently posted about an issue with Exchange 2007 SP3 RU3 that could result in database corruption. The Exchange Servicing team has fixed the reported issue with RU3 and is making new version of RU3 available to customers, version 08.03.159.002, (KB2530488). They strongly advise that all customers install this newly released version of Microsoft Exchange Server 2007 SP3 Update Rollup 3 and to discard any prior version of RU3 (KB2492691) which they may have.

Update Rollup 3 Installation Guidance:

Customers with RU3 already installed within your Exchange environment

It is not necessary for you to uninstall the existing RU3 within your environment. The new RU3 package can be installed over the top of the existing package installed on your servers.

Customers with previous SP3 RU’s installed within your Exchange environment

You can simply install the new version of the RU3 package.

General RU Installation Guidance:

Note for deployments that leverage Forefront Security for Exchange: For those of you running Forefront Security for Exchange perform these important steps from the command line in the Forefront directory before and after this rollup's installation. Without these steps, Exchange services for Information Store and Transport will not start back up. You will need to disable Forefront via "fscutility /disable" before installing the patch and then re-enable after the patch by running "fscutility /enable" to start it up again post installation.