Changing POP/IMAP/Webmail clients…
MDaemon allows several types of clients to connect to it, we saw in the last article a way to migrate Outlook Connector to the new environment using a script. However, we still have to play with POP/IMAP and Webmail clients during the migration process.
Your client may have been configured to use either a DNS host name or IP configuration in POP/SMTP/IMAP client configuration. We are covering all aspects of a coexistence scenario and the POP/IMAP clients should be tested before moving the users’ data. We have a couple of scenarios where we need to prepare to the user’s configuration, as follows:
End-users using POP/IMAP clients (non-Outlook) configured to an IP Address/Hostname
Possible Solution: Change the IP Address to the new server for the migrated user(s)
Recommended solution: Install Outlook 2007 on the user workstation and migrate the local data to Exchange Server
End-Users using Outlook client configured to an IP Address/Hostname
Possible solution: In this scenario, the client should use a PST, in theory, we just need to create a new profile and attach the PST to the new profile and move data to Exchange Server. We can go a little bit further and create a script to read the current PSTs files in use and configure a new Outlook profile and re-attach the old PSTs into the new profile.
The steps described to import data from an Outlook Express client to Outlook 2007 are described in the followingMSExchange.org Article.
After migrating the last user we should change any IP Address, host name or firewall rule pointing from MDaemon to the new Exchange Server. This configuration will allow any user that hasn’t been configured yet to be able to have some connectivity to the new server. Unfortunately, we cannot do this at the beginning because the majority of the users are using the MDaemon Server and they have not had their data migrated over.
Changing Webmail and mobility users
During the coexistence we need to instruct the migrated users to use a different URL to access the webmail page from internal network and also from the Internet. A new firewall rule in your current firewall to publish OWA is required to provide webmail for the remote users.
Another firewall change that should be made is related to Outlook Anywhere and web services, after moving users to the new environment they will be able to use all Exchange Server mobility features and they require some configuration at your firewall level. If you are using ISA you can use the built-in wizards to help you out to create the publishing rules. The same method can be used to create rules to publish Exchange to mobile users using Activesync devices.
One of the last steps for a coexistence scenario migration is the real data migration. We have several ways to move data from MDaemon to Exchange Server. All methods that will be described here must be synchronized with the end-user migration.
The first method is using Microsoft Transport Suite and all steps involved in this process are described in the following article series.
Based on the articles series above, we just need to validate two points on the MDaemon side, as follows:
All accounts that will be migrated using the Transporter tool, must be enabled as POP or IMAP (during the Migration wizard we can decide which protocol will be used). In order to enable POP/IMAP on an MDaemon Mailbox, open the MDaemon Console, click on Accounts, and Account Manager. Double click on selected users and make sure that the protocols are enabled in the Account tab, as shown in Figure 1.
As we saw in the first article, we can export MDaemon account list and use some of those columns to create a migration file. Open MDaemon Console, click on Accounts, Exporting and then click on Export accounts to comma delimited file.
We can use the exported file from Mdaemon to create the file required by Microsoft Transporter Tool, we can use Excel or a simple notepad to change the format. In the table below we can see all required columns by Transporter Tool and what we already have using the exported file that came from MDaemon.
|Transporter Column||MDaemon Column|
A second option is using Import-Mailbox cmdlet, where we can import data from a PST file to an existent Exchange mailbox. This method can be useful if the user does not have any data on the MDaemon Server and all information is kept in his/her local PST. In this scenario the Microsoft Transporter Tool would not be useful because it only copies data from the Mdaemon Server to Exchange Server.
My fellow MVP Henrik Walther wrote about the process to import using Import-Mailbox cmdlet, and you can check his article series here.
A third option is to do the migration on the client side, if user has an Outlook express we should install Outlook client and migrate the content; if the user has an existent Outlook using PST we just need to migrate the data over to the server.
Wrapping it up…
During this article series we went over some procedures for each step that can be used during a coexistence migration scenario to move from MDaemon mail server to Exchange Server 2007. A lot of these procedures covered in this article series can be used on any other third-party mail server. Each third-party mail server has its own features and set of configuration but the main steps will be similar. Just make sure that you have a lab to test and validate your migration plan.
In the next article we are going to go over some administrative tasks that an MDaemon administrator should know how to do in their new Exchange Server 2007 environment.
If you would like to be notified of when Anderson Patricio releases the next part in this article series please sign up to our MSExchange.org Real-Time Article Update newsletter.