A First Look at Exchange 2010

Microsoft’s latest mail server introduces improved high availability and easier management

Anyone dedicated to trivia will note that the code name for Microsoft Exchange Server 2007 was Exchange 12, but the next major release of its mail server has been code named Exchange 14. Microsoft skipped 13 for the same reason that many hotels don’t have a thirteenth floor—superstition! Exchange 14 is expected to ship in late 2009 and have a final name of Microsoft Exchange Server 2010. Exchange 2010 follows up the architectural changes made in Exchange 2007 with some big ...

Buy This Project Plan Now!

This content is part of the Exchange Server 2010 Migration Project Plan.

Purchase this project plan to receive:

  • Step-by-step guidance for managing your project, start to finish
  • Tested advice for preparing for and completing your project
  • Insights to help you avoid common pitfalls and traps

Already registered? here

Discuss this Article 13

muraty
on Apr 17, 2009
Tony, databases allways change. It is not an obstacle to upgrade. Microsoft could succesfully upgrade Exchange 5.5 databases to Exchange 2000 databases, which were superior to 5.5 ones. Microsoft could also upgrade 16-bit Windows 3.0 to 32-bit Windows 95, 14 years ago. And now, after all these technical advances, we can not upgrade exchange 2007 databases to exchange 2010 databases, we cannot upgrade 32-bit OSs to 64-bit OS, even we cannot upgrade Windows Mobile 5.0 to Windows Mobile 6.0 and so on. And you say Microsoft hasn't forgotten how to upgrade? Exchange Server advances in the wrong direction since exchange 2007.
waple02
on Nov 27, 2010
Hi Tony,
Lucky me i found your website. I'm planning to implement exchange 2010 clustering in our company. On the previous previous of exchange 2003, exchange 2007 it requires enterprise for the exchange as well as the operating system.Kindly give me an advice what are the requirements fo implementing exchange 2010.Thanks in advance Waple02
TRedmond
on Apr 16, 2009
Microsoft hasn't forgotten the upgrade option. They just learned from Exchange 2003 how difficult it is to engineer reliable upgrades for all of the circumstances that exist in installations around the world and they learned from Exchange 2007 how smoothly deployments can go when you build servers from scratch. Given that there is a new database schema (8KB to 32KB page size etc.) and a new OS (Windows 2008) for most people, it's inconceivable in my mind to even consider an in-place upgrade. Do you really want to take servers offline for many hours to upgrade a database, upgrade the OS, and then upgrade Exchange? Much better to install a new server, get it working right, and then move mailboxes. A moving train approach (setup new server, move mailboxes from old server, recycle old server) is the way to approach this move. As to always having a positive view on new versions, well, I like progress... what can I say? And I think Exchange 2010 is progress. What would you expect Microsoft to do - not develop new releases? Not include new features? Not attempt to automate common tasks?
Ken (not verified)
on Jul 14, 2009
Tony, You mention in your article that Exchange compresses attachments in the store - this is contrary to the information I have from Microsoft - they have stated that only the email headers and body text/html are compressed. These are the easily compressed parts of the mail object (low CPU cost) as opposed to attachments which would be CPU intensive and grind Exchange to a halt. .. Ken
dkalemis
on Apr 24, 2009
Tony, in Exchange Server 2007, if you only had to support internal Outlook clients (that's a "big" if), you did not have to have a Client Access Server role. You only needed the Mailbox Server role and the Hub Transport Server role. Now. with Exchange Server 2010, even if you only have to support internal Outlook clients, you will need the Client Access Server role as well, because of the new component you mentioned called "RPC Client Access Layer". Am I correct in assuming this?
Charles (not verified)
on May 28, 2009
Tony I found the article informative and interesting. I tend to agree with some that praise it not always deserved, on the other hand I do agree with you that they are moving in the right direction. My biggest disappointment is their reluctance to invest the resources necessary to move the exchange databases to SQL Server. Sometimes it makes no sense at all to me why they have not done this already. They dump how many man-hours and resources into developing high-availability, recoverability and scalability into their new releases of exchange when a lot of those options already exist in SQl Server. It seems like they are re-inventing a large part of the wheel here and in the process torturing us Exchange Administrators by getting us so close to what we need that we can taste it and then never really getting there. For instance - why is LCR restricted to a single database on a storage group? This would not be an issue with SQL server. As I said - they are moving inthe right direction, which is good, but when I hear things like "...the engineering investment to do this proved too great..." it makes me cringe. Too great?! For one of their core business aps?! Sorry - I find that hard to believe. On the other hand - when you're the '500 pound gorilla', how much does it really matter what other people think?
muraty
on Apr 15, 2009
Tony, Microsoft lost his way for the Exchange Server and you do not help with your current allways-praise-all-new-versions attitude. Can't you see that Microsoft forgot the upgrade option? Before Exchange 2007 we could upgrade whatever we had to new versions using the in-place upgrades. Now, we cannot upgrade anything. Is it good? Exchange shops bought new 64-bit machines to upgrade to exchange 2007 and now again they will be forced to buy newer machines just to upgrade! Microsoft lost its mind. So did many Exchange experts.
JimMurph501
on Apr 21, 2009
What about the licensing stuff? Is Microsoft going to go back to allowing the install of the Outlook client that ships with Exchange 2010 as long as you had purchased the CALS, just like up through Exchange 2003? Or are they going to maintain the ripoff deal like Exchange/Outlook 2007 and require customers to buy the full Office 2010 package or subscribe to Software Assurance in order to be able to install Outlook 2010?

Please or Register to post comments.

Exchange Server 2010 Project Plan

<<< Back to the Project Plan


Planning


A First Look at Echange 2010

Exchange 2010 SP1: More Than a Simple Upgrade

Exchange Server Deployment Options

Preparing to Deploy Exchange 2010

Advancements in Exchange 2010 and Communications Server "14"

Planning for Exchange Server 2010 Personal Archives

Load Testing with Exchange 2010

Exchange 2010: Can You Have Too Much RAM?

Session 1: Bigger Mailboxes, Fewer Disks, Less Money

Migrating


Migrating from Exchange Server 2003 to Exchange Server 2010: A Small Organization Perspective

Going Virtual with Exchange 2010

Exchange Server's Client Access: An Introduction

Exchange Server's Client Access: Deploying Your Servers

Session 2: Virtualization The Straight Scoop

Exchange Server's Client Access: Load-Balancing Your Servers

Exchange Server’s Client Access: Securing Your Servers

Moving Mailboxes the Exchange 2010 Way

Exchange Server 2010 SP1 Mailbox Import and Export

Working with the Features of Exchange 2010


Mastering Exchange Server 2010’s Exchange Control Panel

Exchange 2010: High Availability with DAGs

Deploying Database Availability Groups in Exchange Server 2010

What’s New In Exchange 2010 & Remote PowerShell

Exchange Server’s Client Access: Server Administration

Exchange Server 2010 Role Based Access Control

Auditing Administrators’ Actions with Exchange 2010

Database Maintenance in Exchange Server 2010 SP1

Information Rights Management in Exchange 2010

Exchange 2010 High Availability

Walkthrough of Exchange 2010 DAG Creation

Multi-Mailbox Search in Exchange Server 2010

Exchange 2010 MRM: Implementing New Retention Policies

Exchange 2010 MRM: How to Modify and Reduce Help Desk Calls About Retention Policies

Manipulating Mailbox Contents in Exchange 2010

More Exchange 2010 SP1 Mailbox Cmdlets

Prevent Problems with Exchange Server 2010's MailTips

OWA Customization in Exchange 2010

Exchange Server 2010: A New Mobile Frontier

Unified Messaging in Exchange 2010

Session 3: Exchange Management Shell