This post is also available in: Polish
Unfortunately last update released by Microsoft for Exchange 2010 SP2 (Rollup 5) causes many issues with Exchange DAG.
After installation of Rollup 5 for Exchange 2010 SP2 you will receive EventID 4999 in Event Log and also you won’t be able to run Get-DatabaseAvailabilityGroup -Status and the MSExchangeADTopology service started acting strangely.
Like we said first test this Rollup 5 in your test environments.
In Event Log you will find errors 4999 like below about watson:
Watson report about to be sent for process id: 792, with parameters: E12, c-RTL-ADM64, 14.02..0318.004 RemotePowershell, M Exchange Management M.E.C.R dagTaskHelper.GetServersInDeferredRecovery, System.TypeLoadException, 253d, 14.02.0328.005
and when you run below command:
Get-DatabaseAvailabilityGroup -Identity DAG01 -Status
you will receive error like below:
After uninstallation of Rollup 5 all errors goes away.
So for now we recommend do not install this rollup in production environment.
English 
polski
Had the same when I tested it two days ago.
Reported the issue to MS so they are ware but RU5 hasn’t been retired from the download site (yet).
http://unifiees.blogspot.fr/2012/11/alerte-exchange-server-2010-sp2-rollup-5.html
Thanks for informations hope they will release new version or some workaround
You write “So for now we recommend do not install this rollup”
Who is we?
I haven’t seen an official statement from Microsoft.
We it means we us authors of this blog.
We always recommend to install new Rollups in Lab/Test environment first.
Even Exchange Team Blog didn’t write anything about released this Rollup 5
Thanks for the clarification.
Maybe you should update your post at http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/df0e3031-6efd-4611-a2ee-4f40e523ac3c#21225938-b6e6-44af-b3c0-b949a93fc68e
.where you write that “it’s not recommended to install now” and say something like that you don’t recommend it.
thank you
done
Thanks!
Let’s hope that the problem will be resolved soon.
I also faced this error in my test enviroment.