Exchange & Outlook UPDATE, September 8, 2005

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.

Archive Information in Mailboxes and PST files

Learn How Today's KVM Switches and Serial Console Servers Can Give You More Control

1. Commentary

2. Peer to Peer

3. New and Improved

~~~~ Sponsor: Sherpa Software ~~~~

Need a cost-efficient archiving solution? Archive Attender from Sherpa Software automatically archives information from Exchange mailboxes and PST files to a secure, external storage device.

Recover storage space, address compliance issues, secure information and reduce liabilities. Archive Attender is easy to install and there is no additional hardware or client installation required. Download a FREE TRIAL today!

Editor's note: Share Your Exchange Discoveries and Get $100

==== 1. Commentary: A Religious Debate: Upgrade in Place vs. Reinstall ====

The computing world is full of religious debates. I use the word religious to indicate that most of these debates are based on beliefs that are difficult to quantify and sometimes hard to explain but are sincerely held. If you've been in IT for a while, you probably have your own favorite example. Emacs or vi? Novell NetWare or Windows NT 3.1? Exchange or IBM Lotus Notes/Domino? Macintosh or Windows? You get the idea.

The Exchange community isn't immune to these debates, although for the most part we're a pretty harmonious group. Recently, however, I've noticed a new outbreak of a familiar debate: When upgrading an Exchange server, should you perform an in-place upgrade or a clean installation? Each approach has its adherents, and the high priests in Redmond haven't provided any clear guidance. In this case, the Old Testament prophet Isaiah's admonition ("Come now, and let us reason together") is probably appropriate. Is there a preferred way to do an Exchange upgrades?

Let's start with the pro-starting-over faction. There's no question that a production Exchange server can eventually grow a layer of unproductive crud in the form of assorted files and executable bits that were once needed but are now superfluous. Upgrading a server by performing a clean reinstall of the OS (and service packs and security patches) gives you a clean start, with an opportunity to remove any lingering garbage objects that might have taken up residence in your Active Directory (AD) topology.

Of course, doing things this way is a burden; the obvious problem is that a clean installation requires that you perform some tricks. If you just take an existing box and "pave" it by reinstalling Windows, you're likely to break its ability to join the domain, which in turn will break Exchange. It's safer to remove Exchange (thus removing the server from AD), disjoin the computer from the domain, reinstall, rejoin, and reload Exchange. This process obviously takes time, and it certainly requires you to be careful about backing up any mailbox data on the server. You can cut down the time required, however, by using the Ed Crowley Server Move Method to move mailboxes to a swing server before you rebuild the box, which helps somewhat.

On the other side of the argument, an in-place upgrade offers what seems like a simple proposition: At least in theory, you can upgrade Windows and Exchange (separately, of course) without having to remove or reinstall. You still have to make a good backup first, of course, but when in-place upgrades work smoothly they can save you a lot of time.

The "when" in the above sentence is the killer, however. Microsoft makes an effort to ensure that its upgrade code works in a wide range of circumstances, but the company can't test everything, particularly when you factor in all the additional products that might be found on a typical Exchange server. For example, what if your backup product installs a driver that isn't compatible with the version of Windows you just upgraded to? (The answer is "it depends," which isn't very comforting.)

I guess I should make my own prejudices clear. I lean toward the clean-installation side of the argument because when I'm upgrading a system I want to eliminate as many variables as possible. I typically cheat a bit by performing a parallel installation of Windows whenever I'm not 100 percent sure that the target hardware has a fully supported set of drivers so that I can fall back to the original Windows version if need be. However, when pressed for time, I've been known to cheat by performing an in-place upgrade if the target server is relatively clean.

The interesting question is what upgrade options Exchange 12 will offer. Microsoft has publicly stated that Exchange 12 will use the Windows Installer (a requirement to comply with the Common Engineering Criteria), which should make it easier to perform a successful in-place upgrade. However, depending on how Microsoft chooses to support 64-bit Windows, in some circumstances you might have to perform a complete reinstall when you upgrade. I'm sure more details will be forthcoming as part of the Exchange 12 release effort. In the meantime, I'd love to hear your views on the subject.

~~~~ Sponsor: Raritan ~~~~

Learn How Today's KVM Switches and Serial Console Servers Can Give You More Control

==== Events and Resources ====

Get Ready for SQL Server 2005 Roadshow in Europe

Consolidate Your SQL Server Infrastructure

Discover SQL Server 2005 for the Enterprise. Are You prepared?

Roll Back Data to Any Point in Time, Not Just to the Last Snapshot or Backup

Avoid the 5 Major Compliance Pitfalls

==== Featured White Paper ====

Is Your Exchange Server 2003 Environment Well Cared For?

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

Featured Thread: Setting Public Folders to Mail Enabled

Outlook Tip: Using Outlook 2003 Cached Exchange Mode

Q: Under Outlook 2000, I could synchronize a particular public folder so that I could read it offline. Under Microsoft Office Outlook 2003, I can't see a way to do this. I've tried selecting the Download Public Folder Favorites option, but that downloads all my Favorites, which is a large amount of data. Did Outlook 2003 do away with this feature?

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

==== Announcements ====

Get All the Exchange Tips You Need

VIP Monthly Online Pass = Quick Exchange Answers!

==== 3. New and Improved ====

Reduce Spam Volume and Speed Up Exchange Migrations

==== Sponsored Links ====

Argent versus MOM 2005

~~~~ Contact Us ~~~~

About the newsletter -- [email protected]
About technical questions -- http://www.windowsitpro.com/forums
About product news -- [email protected]
About your subscription -- [email protected]
About sponsoring UPDATE -- [email protected]