I installed the new Rollup 2 and have had nothing but problems since. I'm running a CCR cluster and two Hub/CAS servers. After installing the update the IMAP service and Exchange System Host service time out on startup and will not start. No error messages just times out when starting. In addition starting the EMC or EMS takes a very long time after the update and the mmc console will report that snap in has crashed or timed out.I have rolled back to Rollup 1 and everything is fine now. Just wondering if anyone else is having these problems? I also tried removing Rollup 1 then installing Rollup 2 and the same issues occur.Thanks,

Yep same problem here all the core services are running bar the MSE Monitoring service and MSE service host, the unified messaging service will start then say it is stopping. Anyone managed to get them running with out rolling back?

Guys, Not to be a pain on this one, but the issue you are describing might have a workaround in the following article: http://support.microsoft.com/?kbid=935490 At the bottom, the known issues, they reference services being disabled after installing, as well as the workaround. Regards MK

Thank you for the link but it did not help as I have none the symptons mentioned. I have installed the update on four servers and several in a virtual evniroment and the same problem on everyone. Everything is very standard and nothing special. Four of the systems are Server 2003 SP-2 x64 and the other two are Server 2008 x64 and both behave the same way. Only thing installed on these is Exchange 2007.Now the only thing I think could be wrong is I installed the demo version downloaded from MS. The only media we have here is the RTM version but since I was doing a clean install I wanted to use the new SP-1 installer so I used the demo version which appears to be the full version. When I enter our license key its happy and all is well. Rollup 1 works great with it but Rollup 2 breaks it.Windows 2003 x64.NET 2.0 SP-1 x64Powershell 1.0 x64MMC 3.0 is included with SP-2IISAll current updatesExchange 2007 SP-1 x64 Demo with valid Enterpise license key entered.Thats it.Thanks,

Ok Guys,Good news. I have just resolved this issue on my Exchange server (is only happening on my CAS/Hub Transport server).This is what fixed it for me: -Open Internet Explorer. -Open Tools->Internet Options. -Select the "Advanced" tab. -Scroll down and un-check the box labelled "Check for publisher's certificate revocation". -Click OK. Close IE and try opening the Management Console again. Worked for me... Microsoft is not sure why this is. The only difference I can think of is that this server is not using the default certificate for Exchange 2007 - I have replaced it with a SAN (Subject Alternate Name) certificate.This is the only thread I could find about the issue - hope it helps!Paul