Rollup 1 for Exchange Server 2007 Service Pack 1 is now released

sometimes you have to laugh

Update rollup 1 for E12 SP1 is not availble for download yet - the page pops a 404 http://download.microsoft.com/download/1/4/3/143090ec-7e48-4a65-8927-d400e628e60c/Exchange2007-KB945684-x64-EN.msp

Also windows update on Sever 2008 does not find any updates for E12 SP1.

Which is almost as funny as Server 2008 not finding the URL for activation.

Is it April yet? :)

thx!

But it's still applied to Exchange with SP1, right ?

the source for installing exchange came with SP1 (need no update)

That was quick. I guess we'll stop bitching about rollup 6 now. :D

There is a slight delay in the update getting out via Microsoft Update (MU). The folks on the MU team want to make sure everything is fine for our first rollup for Service Pack 1 and it is in the final stages of review. You can still get the rollup via the download center listed in the link.

ETA is for tomorrow. I will update this if this is delayed thru the weekend.

Hmm, it doesn't seem to want to install when E2K7 SP1 is on W2K8.  Gives an error about ending prematurely and not having done anything to my server.  Anyone else?

Hello,

must we install the Rollup 1 for SP1 at the same time on Hubtransport Server and Mailbox Server or can we install the Rollup first on Hubtransport Server and later on Mailbox Server.

i think the update rollout 1 seems to break the ability to create new gal or AL.

1. you are able to create address lists and gal's through the emc and ems.
2. install update rollout 1 on all mailbox servers
3. try to create a new address list or gal through either emc or ems. fails.
Unable to validate the filter: 'The Exchange server address list service failed to respond.
4. uninstall update rollout 1 on at least one mailbox server and you can create the lists/gal.

can someone else verify? i've tried it a number of times and it appears to follow that layout.

gmatteson,

Not aware of that actually! Could you please open a support case on this and we can figure it out?

arvehv on Experts Exchange writes:

Try to change the date forward with one day, so that you have a system date that is 01.03.2008 instead of 29.02.2008. I tried this now, and then everything worked, tried to go back and received the same error again. Did restart the server between the change of dates.

I therefore guess that the problem will be solved as soon as the clock passes 24:00 today:)

I know this may sound stupid, but it seems like exchange 2007 has trouble with this date.

That's correct, it is a leap year bug! More info here (www.buit.org) and here (http://www.buit.org/2008/02/29/exchange-2007-servers-worldwide-experience-leap-year-bug/)