I had previously mentioned that Exchange 2010 Service Pack 2 would be coming this year – and it’s here! I’m pleased to announce the availability of Exchange Server 2010 Service Pack 2 which is ready to download.

We’re delighted to continually add value to Exchange as part of our ongoing release rhythm and the enhancements in this Service Park are largely due to your feedback. SP2 includes much anticipated features such as the Hybrid Configuration Wizard, Address Book Policies, Outlook Web App Mini and Cross-Site Silent Redirection for Outlook Web App as well as customer requested fixes and rollups released prior to Service Pack 2.

As we did with SP1, Service Pack 2 is a fully slipstreamed version of Exchange with 13 server languages and 66 client languages (including English) available in a single package. There is no separate download for client and server languages; you’ll only need to download and install separate language packs if you have Unified Messaging.

Please check out the features in more detail or download SP2 and try them out yourself.

I had also announced that we would support the on-premises configuration of Exchange in a multi-tenant environment. In order to receive support, we’ll publish a follow-up blog shortly that will outline some scenarios and point to our detailed guidance. Please stay tuned.

Thanks again to our TAP participants and you, our customers for all of the great feedback that you provide us!

Kevin Allison
General Manager
Exchange Customer Experience


Not applicable

Anything on AllowCrossSiteRpcClientAccess in SP2?

It was removed from SP! even thought the option is in there.

This would be a really nice feature for a lot of my Medium sized clients.

Not applicable

With Outlook Mini and ISA 2006 how would you configure basic authentication on the /owa/oma directory when the root (/owa) uses forms based authentication?  afaik you can't set up a different policy for /owa/oma when there is already one for /owa.

FWIW, In Exchange 2003 the OMA directory was in the root of the Default Web Site and not a subdirectory of the owa (/Exchange) directory.

Not applicable

@Mike C - SP2 did not introduce any functionality with AllowCrossSiteRpcClientAccess.


Not applicable

@JohnB See

Issues That Are Fixed in Exchange 2010 SP2

Not applicable

@Sazonov ILYA: Exchange 2010 SP2 Unified Messaging Language Packs are at aka.ms/ex2010sp2umlp


Not applicable

@ Sam - there can be different auth types set in Exchange for /owa and /owa/oma but if you have ISA or TMG in front, and have one FBA/Basic listener then it won't really work as any connections to /owa/oma will get the FBA page, as the client is a browser, and it supports FBA logons. One way to provide just a basic prompt, no form, would be to create a new listener, with just Basic enabled, and then create a higher priority rule than that used for OWA, for /owa/oma/* - using that listener. Then any connections to that path use that rule. It means a different listener though.

Not applicable

@ Ilya - The SP2 UM Language Packs can be downloaded at www.microsoft.com/.../details.aspx.

Not applicable

@ Greg.  Thanks. I had already tried creating a different listener with basic auth, however when I try to save the new /owa/oma policy with this different listener, ISA 2006 won't let me save it.  It says that another listener that has the same port and similar IP addresses is being used by another policy.  I don't understand that warning.

I'll keep trying.

Not applicable


Two questions:

* Stop ForeFront Protection for Exchange services or disable with fscutility is not needed anymore with SP2?

* If using OL 2003 Online Mode clients: EnablePushNotifications regkey should be manually created?


Not applicable

after sp2, my outlook 2007 and some 2010 clients keep getting prompted for user name and password.

Not applicable

On your Issues That Are Fixed in Exchange 2010 SP2 page there are no issues fixed listed other than those already fixed in previous rollups, is that correct?

Not applicable

@fr and others who've asked: In addition to SP1 Rollups 1-6, SP2 also includes fix for view change notification issue mentioned in

KB 2579172.(KB live now)

Not applicable

@Nino Bilic

That didn't work. The SP2 installation didn't recognice the Exchange installation anymore after the first dailed try. The Repair Installation from the installation medium failed cause some services coudn't start up since the files for the service where missing. And that failed repair attempt screwd the hole thing up even more.

Since it was a testenvirement it's not that bad I just removed the hole machine.

Not applicable

Does the new update provide WebApp compatibility with the recent versions of Chrome on Linux? Thanks

Not applicable

Reading some of these post makes me wonder why anyone would try to install this service pack (other than in a Dev site) three days after it's released in any production environment. It would also be helpful if you read the documentation before trying. Common sense dictates waiting a few months unless there is some new feature in SPK2 you can't live without or need to fix problem that can't be resolved any other way. Maybe it's just me or I need another cup of coffee.

Not applicable

Is there any descriptions for a UM languages packs SP2? Release Notes? KBs? List of bug fixes? List of new features?

Not applicable

Just to be clear (I have read the Release Notes and Pre-requisites). However it has been a long time since I installed Exchange 2010 SP1

We have a single Exchange 2010 server installation (on 2008 R2 SP1), all clients Outlook 2007/2010

So, to go from

Exchange 2010 SP1 Rollup6


Exchange 2010 SP2

1. No need to remove the Rollups

2. Update AD Schema (using ‘Prepare Active Directory & Domains’ documentation)

3. Install any additional Server Roles required by SP2 (as per SP2 Release Notes)

4. The simply run the GUI setup (no need to run the DOS “Setup Mode:/Upgrade”)

Is this correct?

Not applicable

@ ILYA - The SP2 UM Language Packs include a small set of recording changes based upon issues reported by customers.  There is no new functionality, nor is there a public KB or release note for these updates.  The SP1 UM Language Packs will not work with SP2.  Upgrading to SP2 UM Language Packs requires that the SP1 version be uninstalled first.  SETUP will prompt if you don't uninstall the previous version prior to upgrading to SP2.

Not applicable

There seems to be an error in the step 4 commandlet re: ABP here at:


RecipientFilter is not legal in the context of set-mailbox or get-mailbox.  I did it using the following instead:

get-mailbox -filter '(customattribute1 -eq FAB)' | set-mailbox -addressbookpolicy "FAB_ABP"

Hope that helps someone else!


Not applicable

Something I am not clean on. Do we still need the EnablePushNotifications regkey to work around OL 2003 UDP notification once we install SP2?

Not applicable


there appears to be a wrong translation in the dutch version of OWA.


Not applicable

@JohnM, Outlook 2003 in online mode expects UDP so yes you will want to enable push notifications if you have any Outlook 2003 clients in online mode.

Not applicable

SP2 contains a translation error when using OWA in Dutch: 'Berichten' (Mail) is now called 'Globale adreslijst' (Global address list). This might cause confusion.


Not applicable

SP2 contains a translation error when using OWA in Dutch: 'Berichten' (Mail) is now called 'Globale adreslijst' (Global address list). This might cause confusion.

I am able to reproduce this: martijnwestera.blogspot.com/.../exchange-2010-sp2-owa-dutch-translation.html

Not applicable

Doenst install as CAS Role on TMG 2010 SP2 with Forefront Endpoint Protection!!

Not applicable

Doesn`t install EDGE Role on TMG 2010 SP2 with Forefront Endpoint Protection!

Sorry CAS is was wrong on TMG...

Not applicable

Thats great and Addressbook segmentation is now supported. Great work.

Not applicable

Hello there,

@ technet.microsoft.com/.../bb125224.aspx

there are false information about the objectVersion in Exchange 2010 SP2. The objectVersion value for Exchange 2010 Sp2 should be 14247 ;)

Read here: http://stephan-mey.de/?p=2140


Verifies that the schema has been updated and that the organization is up to date by checking the objectVersion property in Active Directory. The objectVersion property is in the CN=<your organization>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container. The objectVersion value for Exchange 2010 SP2 is 14221

Not applicable

After the installation of SP2 EMS is missing. I followed the steps under part 4 in this article that is for SP1:


All the psd1 files where missing so I copied them from the sp2 installation to the bin folder.

After following the instructions I can start powershell with RemoteExchange.ps1 as target and I can run cmdlets but not scripts.

Any ideas?

Not applicable

Thanks Ross for the information regarding correction of the View issue.

Is it true that there is still an issue with messages leaving the outbox for OLK2003 users?

There also remains an issue for "File --> Save All Attachments" for all OLK2003 users, will this be fixed?

Not applicable

@ Pesos - good catch, we'll fix that.

@ Gwen, Franc and Martijn, we know about that one and are fixing that too.

Not applicable

Is the EMC/IE9 issue fixed with Exchange 2010 SP2?  Or do you still have to use:


Not applicable

@tork247 - this is not a fix that Exchange can fix; it required a change in IE code. What I am saying is - Exchange Sp2 does not make a difference here. If you want to use IE9 on the server with Exchange management tools, you will need the IE fix.


EDIT: I have just received word that today's IE security update, KB 2618444 - is all that you now need. I am going to update the original blog post that talks about this issue.

Not applicable

I have 13 servers deployed with Exchange 2010 SP1 RU3 V3, and 7 out of those 13 servers have the Interim Updates.

Besides the schema change in AD, would i have to unistall the interim updates ? and also deal with the Forefront commands to install this SP2 ?

Would you guys recommed to install SP1 RU6 or go straight to SP2 ?

Thanks in advance

Not applicable

@Dar Bos: Yes, you will need to uninstall IUs on those servers before installing SP2. Note that you should double-check with your support contact that the fixes that you needed IUs for are either in SP2 or are available as a post SP2 IUs, and get those. IU removal is not tied to AD schema change but rather to our regular setup requirement (that IUs be uninstalled and server is in a "known state")

On Forefront - you do not need to run any commands, just stop Forefront services before installation. I'd suggest to go to SP2 rather than go to RU6 > SP2; fixes from RU6 are in SP2 also.

Not applicable

Thanks a lot Nino, i'll double check with Microsoft support on the IU. the IU we have deployed is KB2529939-v3-x64-en, whenever the CAS role is installed.

Not applicable

@ Dar Bos: that fix (KB2529939-v3-x64-en) does not seem to be an IU (Interim Update)... it is "Update Rollup 3-v3 for Exchange Server 2010 Service Pack 1 (KB2529939)" (www.microsoft.com/.../details.aspx) - if this is it, you do not ned to uninstall it, just install SP2. SP2 setup should tell you if there are IUs to uninstall anyway. :)

Not applicable

@ Erik -  I got the same problem on two machines in my Lab environment. No EMS after installation of SP2. Where you able to solve this?

Not applicable

We have applied SP2 to a client and are now getting reports that Droid devices can no longer Sync. We are using silent cross site redirection now as well. Can anyone else confirm that it works or not for them? All full active sync devices seem to work ok.

Not applicable

Have you noticed issues mentioned in this thread social.technet.microsoft.com/.../88ddaf28-de7a-4048-af27-4972b11a212a

EWS is no longer working ok after SP2 and that means no Mac "Mail" clients can connect anymore and OOO (Automatic Reply) is not working in Outlook 2010/2007.

All this is cause by a ASP.NET error killing the EWS application pool. Read more in the article mentioned above.

Would be nice to fix this asap.


Not applicable

@Nino - Not sure if you saw my post on Exchange 2010 SP1 RU6, but I tried stopping the Forefront Controller service to stop all of the Forefront services prior to installation of RU6, and it left Forefront unhooked into the Store process after a reboot. When I didn't stop the Forefront services and applied RU6, everything was fine after a reboot. I was able to reproduce this behavior: blogs.technet.com/.../released-update-rollup-6-for-exchange-server-2010-sp1.aspx

So I am wondering what the downside is to not stopping the Forefront services if we plan to reboot after the Service Pack/Roll Up application anyway. Also I assume the Exchange Product group tested the Forefront team's recommendation on stopping the Forefront services prior to the upgrade, so I am curious if you all saw the same issue where Forefront was unhooked from the Store process due to the service being stooped and had to be manually reconnected via the registry.

Clarification on the *need* to stop the Forefront services would be greatly appreciated.

Not applicable

ServiceControl.ps1 AuthorizationManager check failed Error Back

This error was fixed for the exchange Rollup but looks like this was not done for Service Pack Install. If you are using remotesigned or restricted execution policy in PowerShell the SP2 Upgrade will fail with error " AuthorizationManager check failed. As per our understanding this is because the Install Stops and disabled service required by PowerShell to Execute a Signed Script and since the service is disabled it cannot retrieve the current execution policy and provide with AuthorizationManager failure error.

The exchange initial rollup had the same problem and was fixed it later rollup, can't understand how they missed this for Service Pack 2

Not applicable

Echange 2010 sp 1 was working great . . . downloaded and installed sp 2 and now we cannot send nor receive . . .

Jist Marvelous . . . I wanted to stay up all night . . .

Not applicable

Okay, okay...we were anxious and deployed this method to implement GAL segregation early this year:


In your mind, will SP2 destroy our Exchange environment? Any suggestions as to a way to migrate our hacked-up multi-tenant SP1 deployment to SP2? (if you'd be so kind...I realize this was a risky move on our part)

Not applicable

My advice would be, build a test lab that mirrors what you have today. Back it up (so you can try, try again). Then reverse all the steps you did to build it, then apply SP2, configure it as you want (Multi-tenany is not just GAL segmentation, read the whitepaper we just published to make sure you have got it coveed), and test, test and test some more. Then once you are happy, head over and repeat the steps on production, accepting you will take an outage.

Or just build something new and migrate all the mailboxes. Not nice either.

And make a promise to never ever make the same mistake again. If you can't unpick the mess, and the helpful person who published a bunch of unsupported steps doesn't provide the way to unpick it, then you are in a bad place.

I knew a guy who hacked around in AD once, and three days later he crashed his car. Let that be a lesson to all of us.

Not applicable

Outlook for mac 2011 seriously broken after upgrade to exchange 2010 SP2. (OSX 10.7.2, Outlook 14.1.4 111121)

Application eventlog on server full with event 1309 EWS / IndexOutOfRangeException messages. Receiving email on mac is generally ok, Sending email from mac is hit and miss, sometimes getting "Mail could not be sent. Error code: -17890" with sometimes duplicate messages going out.

This is very painfull. Look forward to fix soon.

Not applicable


We're about to implement 2010 SP2 in a new forest.

If we update the schema for SP2 and we have issues later is it possible to rebuild the Exchange servers with SP1 RU6?

Not applicable

I haven't seen any mention of the fix for the folder copy and move issue in Outlook that was introduced in RU4 and hasn't been noted as resolved in RU5 or 6.

Can anyone confirm?

Reference KB2581545.  The RU 4 interrim hotfix was 492920.

Would also like to request a return to the previous practice of providing a complete list of fixes included as a seperate downloadable document rather than a webpage link which simply link to other pages (RU's).

Not applicable

Deployed SP2 in a test lab and run it since release with no issues. I've then deployed it in production and no issues found. During the SP2 install in prod, the readiness check failed with 'cscript’ process has open files. This was due to System Center. I've stopped the HealthService and rerun the setup and all was good.

Not applicable

I had to stop Antivirus, Backup Exec Agent, Snap Drive Agent and some other 3rd party Service and then all ran fine. I know it's said to do so but I like the reminder.