Hi all I'll be installing Exchange 2007 SP2 or SP3 on 27 Exchange servers over the coming 7 weeks, but with only a 2 hour window once per week for downtime!! Without the ability to test this "exactly" as I want to, has anyone come across problems updating 3 CAS servers concurrently (I have 12 to do)? I would probably stagger them slighty, perhaps 20 minutes apart, but no more than that. I need to pay attention to the activesync policy being added so that I can delete it, but apart from that there isn;t much else I'm concerned with. Anyone done this successfully? Tom

I typically start slow and then move fast. So, I may space out the first few over a few days or week. If that goes well and no issues are encountered, then roll the rest out rather quickly. Dont forget to save any customized OWA features before applying any updates.

Cheers Andy, I'd definitely only do 1 cas box initially, then wait till the following Tuesday to do the next (We only have a 2 hr maintenance window once per week). We have ridiculously strict windows of time to do this per week, weekends are classed as normal office hours. It may well be that in this environment it just has to take months to do these things. Normally I'd happily just drain a CAS from NLB and do it whenever I please, but we have an issue with ActiveSync policies being applied in that I have to cut off access to this service via the ISA for the duration of the update, which then is classed as a service outage so has to be done in the 2 hour window!!! Thanks for the OWA customisation heads up, I had it on my plan but thanks. When you say roll em out quickly does that mean you'd hallipy start of 2 or 3 CAS installs at the same time? Tom

Not usually at the same time. Superstitious :) But I will update easily a bunch in one day .

Upgrades going nicely, thank you for all thew assistance folks. Found out that IMAP Service has problems with ONLY SP2 installed, crashed a few times or hung within first 2 days, so installed RU4 and it has been stable for nearly 2 weeks.