So, here's the thing about Windows Server 2008: It's been getting rave reviews from everyone I've talked to. We've already migrated much of our infrastructure to it at 3Sharp, and I know several people who have replaced the Vista installations that came on their late-model laptops with Server 2008. However, I haven't yet seen a big surge of enthusiasm toward Server 2008 as a platform for Exchange Server deployments. That's got me thinking about why that might be so.

On one hand, Server 2008 and Exchange Server 2007 would seem to be a natural match. Server 2008 adds several useful features, including the ability to stretch clusters across multiple IP subnets and greatly expanded support for hot-swappable hardware.

On the other hand, this support comes at a price.

First, you can't perform an in-place upgrade from Exchange 2007 running on Windows Server 2003 to Server 2008. That means you essentially have three choices to upgrade your servers:

• build a new server with Server 2008, then move mailboxes from existing servers to the new one;
• move mailboxes from the existing server to a "swing" server, then upgrade the existing server, then move the mailboxes back; or
• back up the mail data from the existing server, then upgrade it to Server 2008, either through a clean install or by removing all the existing components that can't be upgraded, such as Exchange and PowerShell.

None of these options are trivial to implement, and that's clearly part of the problem: Administrators who are already nervous about the prospect of moving to the x64 version of Windows 2003 are generally not in a hurry to move to Server 2008. The no-in-place-upgrade problem will also inhibit casual experimentation with the new combination.

The second limitation of using Server 2008 as an Exchange platform is that some of Server 2008's most intriguing new features aren't usable with Exchange. For example, the new Server Core role, which lets you run many server-based applications without a GUI on the server, doesn't support PowerShell or the .NET Framework—both of which Exchange 2007 requires. So, no Exchange on Server Core. Exchange doesn't make use of Server 2008's read-only domain controllers, so you might not get much value from deploying them in your Exchange environment.

A third strike against Server 2008 for Exchange, whether fair or not, is that many administrators have the firmly held opinion that they won't deploy any Microsoft product until its first service pack is released. Exchange 2007 SP1 is available now, but it will be a while until Server 2008's first service pack is released.

Despite all this, there's one killer feature that I think will drive adoption of Server 2008 for use with Exchange: Hyper-V. Virtualization is becoming an increasingly hot topic in the Exchange world, and Hyper-V promises to provide full support for virtualized Exchange deployments—something that has been in increasing demand as virtualization has become more and more broadly deployed. Look for more on this topic in a future column.

Reader Comments

I have to say another big loss for smaller shops is the lack of an included backup utility that supports Exchange ESE streaming backup APIs in Server 2008. They left the APIs in there, but Windows Server Backup cannot be used to backup E2K7. So now what? SMB are forced to purchase a third party backup program? Bad Mircosoft.

W2k8 is already SP1 no need to wait if that is a reason :)

You're right about the loss of an included backup tool. This will be a big deal for smaller shops, but it's also an effective way to "help" people move to VSS-based backup solutions-- something Microsoft has been wanting to do for a while now.

Also they maybe limited by the Antivirus software they run on the servers. Our vendor Symantec does not have a supported release yet that I know of.

I plan on bringing my first W2K8/E2K7 SP1 CAS/Hub T into production in the next 3 weeks. Your article mentions that 3sharp has a number of systems running W2K8. How about your Exchange Servers?

Our Exchange servers are still on Windows 2003, although we have plans to migrate to Windows 2008 later in the year.

Is the following quote from InstantDoc #98714 true ??? CanNOT find any other references on the web saying that Exchange 2007 canNOT function with aonly a RODC. ==="Exchange doesn't make use of Server 2008's read-only domain controllers, so you might not get much value from deploying them in your Exchange environment."===

Derek, the product documentation at says that Exchange 2007 "essentially ignores" RODCs. You have to have at least one writable GC available for Exchange. Hope this helps answer your question!