Now that Microsoft has halted support for Exchange Server 2003, some organizations are gearing up to migrate to a supported version of Exchange Server, such as Exchange 2007.
If your organization wants to migrate to Exchange 2007, know that Microsoft doesn't offer a way to perform in-place upgrades from Exchange 2003 to Exchange 2007. However, it's possible to install a 2007 server into existing Exchange organizations and then move Exchange resources, including mailboxes and public folders, to the new 2007 deployment. After running in a coexistence period, organizations can move all of their resources to Exchange 2007 and finish with decommissioning its Exchange 2003 servers. Microsoft offers a detailed description of the process on its TechNet site.
Exchange migration station
This is part one in a series about upgrading Exchange Server 2003 deployments. Click here for part two, which covers the features and capabilities organizations can expect if they choose to migrate to Exchange 2010, and click here for part three, which covers Exchange 2013.
This three-part series covers expectations of migrating to Exchange 2007, Exchange 2010 or Exchange 2013. Part one covers a few of the things your organization can expect if it decides to migrate to Exchange 2007. We'll look at different Exchange 2007 features your organization could benefit from, including server roles, hypervisor features, clustering and unified messaging.
1. Calendar features get a makeover
Microsoft redesigned the calendaring features in Exchange 2007 and Outlook 2007, making them more practical and efficient for end users. Organizations can expect to see changes to resource mailboxes, work hours and the scheduling assistant.
2. Exchange 2007 lets you use Unified Messaging
You can implement UM to give end users access to their faxes, email and voicemail. This chapter excerpt explains the pros and cons.
3. You can bring catch-all functionality back
If you migrate to Exchange 2007, you may notice that it's missing native support for catch-all functionality. There is a workaround for the missing function. If you want to bring it back, consider using the CatchAllAgent transport protocol agent available in CodePlex.
4. Changes to Exchange 2007 clustering
Clustering went through a few changes in Exchange 2007, including role changes to back-end and front-end servers as well as adjustments to replication features.
5. Exchange 2007 server roles also get a makeover
Although the concept of server roles has been in an Exchange admins' vernacular since Exchange 2000, Exchange 2007 includes a marked difference -- a shift to role-based deployments. Get a closer look at how the five pre-configured roles in Exchange 2007 work.
6. Exchange 2007 includes tools to secure mobile devices
Although mobile devices are changing the rules of traditional workplaces, security is still a top priority. If you plan to migrate to Exchange 2007, consider how these mobile security tools can protect your enterprise.
7. There are special considerations for virtualizing Exchange 2007
If your organization is thinking of virtualizing Exchange 2007, there are a few things to keep in mind. It can work with hardware virtualization, but only when the hypervisor is on the SVVP list. Also remember that the UM server role can't be virtualized.