Exchange 2007 RTM'd

Thursday afternoon the following was posted to the MS exchange blog...

This morning, we signed off Exchange 2007 for release to you!

We've bet the company on this product. Here at Microsoft, we have over 120,000 mailboxes running in production on Exchange 2007 – exceeding our SLA of 99.95% availability. Likewise, over 200 Technology Adoption Partners and Rapid Deployment Partners have over 55,000 mailboxes in production operating within their enterprise SLA's.

In addition to taking the time to ensure this software was rock solid for you, we've invested more time in documentation and deployment guidance than we have for any other release previously. Please do check it out and let us know if we're missing something you need.

Thank you for all of your support, feedback, and patience during this journey by our team. We are committed to working with you on successful deployments in the coming months and years.

On behalf of the entire Exchange team, thank you for choosing Exchange.

With any luck, it will be on MVLS/MSDN within the next few days.

News Source: MS Exchange Blog

Report a problem with article
Previous Story

GRAW 2 Officially Announced!

Next Story

RIAA Wants Less Money For the Artists


Commenting is disabled on this article.

Since Exchange 2007 works a lot different than Exchange 2003, requires 64 bit hardware only, and that we have over 500 exchange servers in production (on 32 bit hardware)... This upgrade is not going to happen anytime soon.

5.5-> 2000 was painful

2000-2003 was less painful, still a lot of non-automated things i needed to do.

Not planning on upgrading to 07 for office or exchange any time soon.

Also, not planning on going to vista.

not only would we have to buy a ton of software, but we would need a ton of hardware upgrades.

4 hours?!??!!? You call that "major problems"???

What planet are you from?

4 days would be a major problem but 4 hours is just a minor glitch.

I'd say that depends on the company/industy, ahhell. For a bank/financial institutions or a hospital four hours is too long.

Quote - ahhell said @ #8.1
4 hours?!??!!? You call that "major problems"???

What planet are you from?

4 days would be a major problem but 4 hours is just a minor glitch.

4 hour wages times 10 people is nothing.
4 hour wages times 100 or a 10000 people is a lot.
It often depends on the complexity of the migration. When downtime is ineffability, schedule it in the off-hours.

The university I work at had massive issues migrating from 5.5 to 2000, so it took our network administrator a long time to build up the guts to go to 2003. He just upgraded over the summer with minimal issues.

Hopefully it won't take him this long next time

The upgrade path from Exchange 5.5 to 2000 was horrible. It was two upgrades in one and you had to re-learn Exchange administration. The upgrades from 2000 to 2003 and 2003 to 2007 should be much simpler in comparison.

migration in exchange servers its a pain i remember when my company was migrating from 2000 to 2003 lot of issues happened =/ anyways lets hope for a easier transition

Don't blame Exchange. I have done allot of migration from 5.5, 2000 and 2003 to 2003. All of them successful and with no or little problems.

It's often the people that don't know how to migrate that cause the problems.

the speech recog and the unified messaging are really good.

64bit only was a wise decision, opening up the database to a larger amount of memory will release some of the I/O bottlenecks on larger roll outs.

The mirror copying is a good idea aswell for instant fall over recovery.

I know some companies that just upgraded to Exchagne 2003. I would if they are going to release the server version to Vista soon. (just like they did with XP and Server 003 and Exchange 2003, claiming you will see added benefits)

I just migrated our company last year but was able to talk management into buying software assurance so the upgrade to 2007 (after SP1 is released, of course) will be "free".