Online resources for migrating to Exchange 2007 Print

Author: Simon Bisson

Migrate mailboxes from Exchange 5.5 to Exchange 2007
If you need to migrate mailboxes from Exchange 5.5 to the latest version you’ll find that mailboxes can’t be moved using the built-in wizards, which only support Exchange 2000 or later. Microsoft’s Exchange team blog describes how to use a copy of Exchange 2003 to handle the interim stages of a mailbox migration using the built-in tools – as well as pointing out third-party applications that can handle a full mailbox archive and restore between various versions of Exchange.

Working with the SBS Transition Pack
Your clients may well grow bigger than Small Business Server 2003’s 75 user limit. If you don’t want to build completely new active directory architecture, and want to keep the existing server, you can use a Transition Pack to convert SBS into a standard Windows Server (and all the associated CALs into Windows Server CALs). This Technet blog entry shows just how to handle the transition, and how to use the tools in the Transition Pack.

Change the welcome mail sent to new SBS users
Clients often want new users to be given a quick start that helps them fit into the business. You can use the first mail Exchange sends to users to give details of key resources, either phone numbers of people or links to information held on the company Intranet or SharePoint system. Use the details in this blog post to modify the HTML of the default message, and turn it into a useful resource.

Use a non-standard SMTP port to send mail to a Smart Host
If you’re used to working with earlier versions of Exchange, you’ll have discovered that Exchange 2007 makes it impossible to use the Exchange GUI tools to set the port used for SMTP traffic to a smart host. If your clients’ ISP wants to use a non-standard port you’ll need to use PowerShell to make the changes. This Technet blog from Microsoft shows just what to do.

Let applications send mail via Exchange Server 2007
Your clients’ line of business software may need to send email – either sending alerts to users or messages to suppliers and customers. If ERP or CRM systems need access to Exchange 2007 you’ll need to change some of the default security settings. If an application is associated with an Active Directory user, you can use that user ID to authenticate against the mail server. Alternatively you can use a custom Exchange connector to handle anonymous access from the server IP addresses. Follow the instructions in this Exchange Team blog entry to set up your mail server appropriately.

Using Exchange logs to troubleshoot message transport issues
Exchange’s log files are an important diagnostic tool – though many of the logs you might want to use aren’t enabled by default. Use the tips in this Exchange Team blog entry to use PowerShell to enable Exchange 2007 logging, and then work with Microsoft’s Log Parser tool to search through massive log files to find the one piece of information you need to solve a problem.

Get 21 days to move files from a SBS 2003 server to a new Windows Server system

If you’re retiring an old SBS server in favour of new hardware (with a new operating system) you’re limited to running SBS for only 7 days with the FMSO roles on another machine before the SBS server starts rebooting every hour. Use the instructions in this blog entry to download a Microsoft hotfix that extends that time limit to 21 days – plenty of time to handle file and user migrations.

Link to a Relevant FeatureClick here to go to the Main Feature - Upgrading Small Business Server 2003 to Exchange 2007

Show other articles by this author