Released: Exchange Server 2010 SP2

@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.