Exchange & Outlook UPDATE, Exchange Edition--Planning Ahead Keeps You From Falling Behind--March 16, 2006

Exchange & Outlook UPDATE, Exchange Edition--Planning Ahead Keeps You From Falling Behind--March 16, 2006

Subscribe to Windows IT Pro:


Don't miss out! Make sure your copy of Exchange and Outlook UPDATE isn't mistakenly blocked by antispam software. Add [email protected] to your list of allowed senders and contacts.


This email newsletter comes to you free and is supported by the following advertisers, which offer products and services in which you might be interested. Please take a moment to visit these advertisers' Web sites and show your support for Exchange & Outlook UPDATE.




1. Commentary
- Planning Ahead Keeps You From Falling Behind

2. Peer to Peer
- Featured Thread: Post Migration Problems
- Outlook Tip: Creating a Report of Email Senders

3. New and Improved
- Quickly Access and Recover Lost Email Messages

==== Sponsor: DataViz ====

RoadSync is Exchange ActiveSync for non-Microsoft devices. This means wireless access to your Exchange Server 2003 data without the need for middleware or a desktop redirector. Support for SP2 features including Direct Push, Remote Wipe, Global Address List, and Additional Data Compression is now available for Symbian UIQ and Symbian Series 80 devices, including the Sony Ericsson P900/P910, Motorola A1000, Nokia 9300 and 9500. RoadSync is also available for Palm OS and select Java MIDP 2.0 devices (including Treo and Motorola RAZR) and will support Series 60 Third Edition when these devices become available. Sign up to download the Free Office Mobility Kit today.


Editor's note: Share Your Exchange Discoveries and Get $100
Share your Exchange Server and Outlook discoveries, comments, or problems and solutions for use in the Exchange & Outlook Administrator print newsletter's Reader to Reader column. Email your contributions (500 words or less) to [email protected] We edit submissions for style, grammar, and length. If we print your submission, you'll get $100.


==== 1. Commentary: Planning Ahead Keeps You From Falling Behind ====
by Paul Robichaux, Exchange Editor, [email protected]

Last week, I talked a bit about some tools for migrating to Exchange Server from other messaging systems. This is currently a hot topic as Microsoft and IBM Lotus fight it out for total domination in the collaboration space, but there's actually more action in the Exchange Server 5.5 migration space. A surge of migration activity occurred last year as companies rushed to move away from Exchange 5.5 before it hit the end of its 10-year support cycle; after January 1, 2006, customers still running Exchange 5.5 must buy custom support contracts if they want support. Naturally, this has spurred many of them to accelerate their Exchange Server 2003 deployment plans (arguably something that should have been considered last year, before Exchange 5.5 went end-of-life!)

I recently met with a new client company that retained me to help it come up with an Exchange 5.5-to-Exchange 2003 migration plan. It's a financial services company with about 500 mailboxes spread across 13 servers in five sites on two continents. This isn't a huge environment, but it's more complex than most similarly sized sites because it uses replication software to provide disaster-recovery capability to a remote site and because it has a fairly complex SMTP routing structure that doesn't rely on Exchange.

After my initial meeting with the company, I was impressed by some things the technical staff had done--and not done--to make the migration process as smooth as possible.
- They did their homework. When I arrived, they'd already spent a good deal of time reviewing my design proposal, and they asked detailed questions that showed clearly that they had read up on the process. Research is almost always free, and Microsoft spends a huge amount of money building free technical content that you can absorb to help make your own migration projects smooth.
- They knew what they wanted. Many companies never define an explicit service level agreement (SLA), so they're at the mercy of whichever group of users yells the loudest. This company had a clear SLA that defined what service levels were required for normal working hours, weekends, and holidays, and which groups of users it applied to. This made it much easier to build a design that delivered the required service levels without wasting time or money.
- They asked lots of questions. Although they'd invited me to participate as an outside expert, by no means did I get a free pass from questions. I had to be able to justify every point of the proposed design, indicating both the high degree of preparation and their clear understanding of what they wanted. My job was to tell them how to get there, and their questions helped move us all to that end.
- They got their hands dirty. Before I ever met with them, the administrators had spent time trying different things in a test lab. They already knew that their proposed iSCSI SAN configuration would work for SAN booting, for example. This let our discussions focus on how to find the best possible configuration, not on guessing what would or wouldn't work.
5. They didn't rule anything out. The technical staff at this company had some clear preferences for how they wanted the new Exchange environment to look, but in my discussions with them, it quickly became clear that their number one goal was to keep the users happy and productive. As we occasionally uncovered business requirements that forced changes to the Exchange design, they made the needed changes and moved forward. No time, energy, or money was wasted on arguing or fighting over changes that could ultimately be overruled by the business folks who were signing the checks.
6. They didn't rush things. Even though they were very, very interested in moving to Exchange 2003 as quickly as possible, they took the time to plan a series of short pilots that helped them simultaneously build experience with Exchange 2003 and validate various aspects of the design. This approach let them move from success to success without unnecessary delays.

At this point, you might think that this is an unfair portrayal of an organization with lots of budget and a deep bench of talent. However, you can apply the same principles to your own Exchange environment even if you're on a shoestring budget or face technical or political constraints that slow things down. Given the huge amount of migration documentation out there, where should you start? My recommendation is simple: Run the ExDeploy tool from the Exchange 2003 CD-ROM (or download it from and see what it tells you about your environment. If you don't understand the reports it generates, use that to guide your research; as you review ExDeploy's recommendations, you can tailor your design to reflect your needs. If there are holes in your plan, ask questions (either in public forums or of your favorite consultant) to help plug the holes. Doing these things instead of rushing headlong into an ill-planned migration will give you the best results in the long run.


==== Sponsor: Hewlett-Packard ====

Protect mission-critical business information stored on your high-availabilty Exchange systems when you implement backup and restore strategies. You'll also learn the proven best configuration and deployment considerations.


==== Events and Resources ====
(A complete Web and live events directory brought to you by Windows IT Pro: )

Windows Connections Conference, April 9-12, 2006
Don't miss the essential Windows technology conference.

When disaster strikes your servers, whether they are dedicated to Windows, SQL, or Exchange, you need answers. Make sure that if an emergency occurs, you're prepared. Get the full eBook and get started on your recovery plan today!

Learn to gather evidence of compliance across multiple systems and link the data to regulatory and framework control objectives. On-demand Web seminar.

Make sure your email server is secure. Learn everything from basic techniques to defense-in-depth strategies, including network-level access control lists, Web authentication, firewall protocol inspection, and perimeter filtering. Live Web seminar Thursday, March 23

Use Windows Server 2003 R2 as a platform for SQL Server 2005 to support large-database requirements, including clustering and multiple processors. Register for this free Web seminar today!

==== Featured White Paper ====

Use scripted deployments to ensure that all your Exchange servers are configured and deployed with exactly the same options and to maintain a record of your installation configurations. Learn how today!

~~~~ Hot Spot ~~~~ If you use Active Directory – this survey's for you! Just 5 quick questions will enter you to win one of 8- $25 Best Buy Gift Certificates. Fill it out today!

==== 2. Peer to Peer ====

What Do You Think? Don't forget to sound off in our Instant Poll. This month's question is "What's the biggest messaging-security threat your company faces?"

Featured Thread: Post Migration Problems
A forum reader is having problems after migrating users from a Windows 2000 Server domain to a Windows Server 2003 domain. Now when someone types the first couple of letters of a user's name in the to field, two identical email contacts pop up. If you can help, join the discussion at the following URL:
Outlook Tip: Creating a Report of Email Senders
by Sue Mosher, [email protected]

Q: Every month, I need to submit a report listing everyone I've received messages from. Is there an easy way to print just the sender names? I don't want all the messages to print.

Find the answer (and links to more great tips) at

==== Announcements ====
(from Windows IT Pro and its partners)

Windows IT Pro Magazine Article Library--access available
Sign up for a Monthly Online Pass and get INSTANT access to all articles, tools, and helpful resources published on, including exclusive subscriber-only content. You'll get 24/7 access to the full Windows IT article library (includes more than 9,000 articles) and get the latest digital issue of Windows IT Pro delivered right to your inbox. Sign up now:

Windows IT Pro Magazine--SAVE 58%
Windows IT Pro is a must-have in 2006! Subscribe now and plug into the largest independent Windows IT community in the world. Along with loads of how-to articles, time-saving advice, and expert tips and solutions, you'll gain exclusive access to the entire online Windows IT Pro article library FREE. This is a limited-time offer, so order now:

==== 3. New and Improved ==== by Blake Eno, [email protected]

Quickly Access and Recover Lost Email Messages
Unitrends announced Continuous Exchange Protection (CEP), an Exchange data-protection solution that lets you recover server-level email information down to message-level data. CEP functionality is included in all of Unitrends' Data Protection Unit (DPU) appliances, which let you back up from an Exchange Server to a DPU instantaneously or on a scheduled basis. CEP is part of Unitrends' Rapid Recovery System and is available at no additional charge to all customers with a current maintenance agreement. For more information, contact Unitrends at 803-454-0300 or 800-648-2827.


~~~~ Contact Us ~~~~

About the newsletter -- [email protected] About technical questions -- About product news -- [email protected] About your subscription -- [email protected] About sponsoring UPDATE -- [email protected]


This email newsletter is brought to you by Exchange & Outlook Administrator, the leading publication for IT professionals managing, securing, optimizing, and migrating Exchange and Outlook. Subscribe today!

Manage Your Account
You are subscribed as %%$email%%

You are receiving this email message because you subscribed to this newsletter on our Web site. To unsubscribe, click the unsubscribe link:

View the Windows IT Pro Privacy policy at Windows IT Pro a division of Penton Media Inc. 221 East 29th Street, Loveland, CO 80538, Attention: Customer Service Department Copyright 2006, Penton Media, Inc. All Rights Reserved.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.