Software // Enterprise Applications
Commentary
3/18/2005
03:45 PM
Commentary
Commentary
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Smart Advice: Storage Attachment Made To Order

Expect iSCSI to gain popularity at Fibre Channel SANs' expense, The Advisory Council says. Also, plan your migration to Microsoft Exchange 2003 carefully, and recognize possible need for coexistence of messaging systems during the migration.

Question B: What issues must we address in planning a migration to Microsoft Exchange 2003?

Our advice: You're not alone in still being in the planning stage of your migration to Exchange 2003. It's been estimated that, as of year-end 2004, 40% of Exchange mailboxes are still on Exchange 5.5, 43% are on Exchange 2000, and only 14% are on Exchange 2003.

Messaging is a critical application in almost all organizations. It's imperative that your migration be seamless and transparent to both your internal users and external correspondents. If there's an interruption, you'll hear about it right away. Migrations can cause serious outages if you don't plan carefully.


Related Links

Migrate to Exchange Server 2003

Upgrade to Exchange Server 2003

After Slow Start, Exchange 2003 Begins to Take Hold


If your migration is large enough that you can't move all the users in a single operation, then you must deal with the complexity of co-existence. During co-existence, both messaging systems must appear as a single system to all users, address lists must be synchronized, and mail must flow seamlessly. There are three main paths in which messages flow: inbound from the Internet, outbound to the Internet, and between the existing mail system and the new Exchange servers.

Messages between Exchange and a "foreign" system are typically handled by Exchange Connectors. Exchange provides a suite of connectors to handle just about any non-Microsoft messaging system. A connector tricks the foreign messaging system into thinking the Exchange Organization is of the same-breed mail system. Exchange will use the foreign-messaging system's addressing scheme. Exchange's Connectors are well documented in the Microsoft Exchange library.

Sending mail to the Internet from both Exchange and the foreign-messaging system is usually simple. Just make sure your firewall is configured to permit outbound Simple Mail Transfer Protocol from your new servers.

Inbound Internet mail routing is the most difficult aspect of co-existence, because you will be sharing SMTP name spaces with recipients spanning both messaging systems. Most systems want to be authoritative for any SMTP name space for which they're configured to accept mail. How will the messages get from the Internet to recipients in the other system? The way you will build this depends on the migration tool you use.

Here are some other points to prepare your organization for migration:

  • Test, test, and then test some more. The time you spend in the lab will pay back 100 times over in the time you spend on the production system.
  • For each target storage group, plan to back up many times during the migration to clear the transaction logs. Many people think that frequent backups are too much overhead, so a more realistic approach would be to turn on circular logging. Do not forget to turn circular logging off at the end!
  • Expect to open a support case or two with Microsoft. Despite any engineer's level of expertise, this is almost inevitable. Most migrations are such complex operations that there are just some things you can't fix.
  • Evaluate your migration tool thoroughly. I've seen many companies backed into a corner because they didn't understand how their migration tool handled specific Exchange functions such as public-folder E-mail addresses, foreign-language mailboxes, or inbox rules. You'll either catch these in the lab, or be overwhelmed by a backlash from users when they find out something doesn't work like the old system.
  • -- Brian O'Neil


    Beth Cohen, TAC Thought Leader, has more than 20 years of experience building strong IT-delivery organizations from user and vendor perspectives. Having worked as a technologist for BBN, the company that literally invented the Internet, she not only knows where technology is today but where it's heading in the future.

    Brian O'Neil, TAC Expert, has more than 10 years experience in IT designing, migrating, and managing enterprise network infrastructures for the U.S. Department of Defense, financial organizations, medical institutions, and law firms. He has been the primary technical lead and project manager for large migrations to Microsoft Active Directory and Exchange 2003.

    Previous
    2 of 2
    Next
    Comment  | 
    Print  | 
    More Insights
    Building A Mobile Business Mindset
    Building A Mobile Business Mindset
    Among 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps – and it's past time for those with no plans to get cracking.
    Register for InformationWeek Newsletters
    White Papers
    Current Issue
    InformationWeek Tech Digest September 18, 2014
    Enterprise social network success starts and ends with integration. Here's how to finally make collaboration click.
    Flash Poll
    Video
    Slideshows
    Twitter Feed
    InformationWeek Radio
    Archived InformationWeek Radio
    The weekly wrap-up of the top stories from InformationWeek.com this week.
    Sponsored Live Streaming Video
    Everything You've Been Told About Mobility Is Wrong
    Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.