Category:

CMT for Exchange

SubCategory:

General Information

Brief Description:


Subject:

CMT for Exchange 3.2.2 Installation Requirements

Problem:

Hardware, software and configuration requirements for the installation of CMT for Exchange 3.2.2

Resolution:

Hardware Prerequisites
CPU (minimum requirement): Pentium IV Class

Memory: Required 1GB; Recommended 2GB

Hard Disk Drive: 5GB + free space

Note:
You require more disk space when you are migrating data to local .pst files.

CMT for Exchange Server (Migration Control Center)

Installation Requirements


• Windows XP with SP2+ with security updates (2 GB RAM Minimum) or Windows 2003 Server (32 bit) with SP1+ (2 GB of RAM Minimum)
Outlook Client Requirements:
• Outlook 2003 with SP1 and SP2 Minimum (Office Suite 2007 with SP2 Recommended) (must be Outlook 2007 if migrating to Exchange 2010)
• All reminders are shut-off (click Tools -> Options -> Other -> Reminder Options).
• Auto-archiving is disabled (click Tools -> Options -> Other -> Auto Archive).
• Outlook must be the default email client, and you must log into the system with local Admin ID.
Notes requirements:
• Notes versions 6.x, 7.x, or 8.x are supported. It should be installed as a single user installation (multi-user installations are not supported). We recommend Notes 7.0.3 for full MIME support.
Note:
Domino/Notes 5.x is not included; however, most of the 5.x functionality is properly handled.
You must use a Notes ID with access to read your Domino directory and manager access to the source mailbox databases, and be able to access Notes from outside applications such as CMT for Exchange (For more details, refer to Notes Migration Accounts Requirements).
• Make sure that you enable the Notes ID security for the option “Don’t prompt for password from other Notes-based programs (Reduces security)”.
• Make sure that you turn off Notes mail reminders in the Notes client preferences mail section.
• Make sure that you enable TCP/IP as the only port in the Notes client install preferences.
• SOAP Toolkit 3.0: It is a part of the IIS installation; you do not need to install it separately. (Need to install it manually if using Windows 2003.)
• IIS with web service components (SMTP and FTP components not needed) (For more details, refer to the next section)
• .NET Framework 2.0 SP2 (For more details, refer to the next section).
• Do not have restrictions in your Group Policies or workstation policies that prevent the automatic creation of MAPI profiles or .pst files.
• You must disable any applications which take over or block the use of port 80 on the Control Center.
• It is recommended that you log into the PC with an account that has at least "take ownership" rights to the mail store that is your migration destination, and that you log into the same domain as your migrations’ destination. If you are migrating to Exchange 2007 or 2010, then you must have Full Access rights.
• Make sure that any personal firewalls and the XP firewall is OFF and disabled as a service.
• Make sure that Antivirus software is disabled. Specifically, the real time scanning protection. Otherwise, migration throughout will be reduced and other issues can occur such as crashes in stressful states of migration workload. If it cannot be disabled, please exclude the following directories from scanning:
• C:\windows\temp and (%TEMP% if different)
• C:\Program Files\BinaryTree\CMT Universal
• C:\Exported PSTs (or the destination folder specified by the user for migrated PSTs)
• Make sure that WSUS, Intel LanDesk, and other such programs are excluded from running on the migration workstations. These programs may halt migrations as their screens pop-up to run tasks as well as re-boots caused by these processes can interrupt migrations.
• Make sure that you turn OFF Automatic Windows updates.

IIS 6.0, ASP.NET in Windows 2003 Service Pack 2


• Base version (v6) within Windows 2003 Service Pack 2
• Windows 2003 Server SP2 logged into the destination Exchange Domain (Preferred)
• If in a domain, then any policy to workstation cannot have restrictions that prevent the automatic creation of MAPI profiles or .pst files.
• The workstation name must be excluded from group policies that restrict local account privileges (Highly recommended to exclude workstation name from Group Policy Objects (GPOs)).
• IIS Server installed with the default website, settings and default locations including:
• Default We Log Path: C:\WINDOWS\system32\LogFiles
• No ISAPI Filters
• Unlimited web site connections
• No bandwidth throttling
• Home directory: C:\inetpub\wwwroot
• Directory Security: SSL Disabled
• ASP.NET v2.0.50727
• Web Service Extensions: ASP.NET v2.0.50727 (Allowed)
• W3SVC Service running as local system account, started, and automatic startup
• Full Anonymous Account Access to the local IIS Server Instance
• The anonymous account needs to be elevated to local station Admin privileges.
• All of the migration workstations must be able to talk with each other over Port 80.
• XML calls must make connections between the migration farm (To/From the migration server) using the Anonymous Access provided above.

Windows Migration Account Requirements


• Domain user account with:
• Local admin access to all control center(s) and migration stations
• Ability to install software
• Configure registry keys
• Full control access the server directories

Notes Migration Account Requirements


• Notes ID user account with:
• Access to read the Domino directory as a general notes client user
• Access to read the mail files for migration scope
If the Notes ID doesn’t have the required level of access, then you can perform any one of the following actions before migrating a user mail file or database:
• Add the ID to the user mail file or database ACL with the required rights.
• Add the ID to a Group with the required rights that is already in the user mail file or database ACL.
• Switch the ID to one that has the required access rights.
• Do not use the Notes Administrator Clients Full Access Administration feature as it is not considered an effective method for granting required level of access to the migrating user data. This is because the migration engine does not invoke the Notes client itself, and the Full Access Administration is often not applied to the session performing migration, which will cause the migration to fail. The Notes ID being used must have access granted in the ACL of the source data via either group membership or explicit membership as stated earlier.

CMT Migration Workstation

Installation Requirements


• Windows XP with SP2+ with security updates (1 GB RAM Minimum)
Windows Server 2003 (32 bit)
Outlook Client Requirements:
• Outlook 2003 with SP1 and SP2 Minimum (Office Suite 2007 w/SP2 Recommended) (must be Outlook 2007 if migrating to Exchange 2010)
• All reminders are shut-off (click Tools -> Options -> Other -> Reminder Options).
• Auto-archiving is disabled (click Tools -> Options -> Other -> Auto Archive).
• Outlook must be the default email client, and you must log into the PC with local Admin ID.
Notes requirements:
• Notes 7.0.3 should be installed as normal single user installation (multi-user installations are not supported).
Note:
BT currently does not support Lotus Notes 7.0.4 on migration workstations.
• You must use a Notes ID with access to read your Domino directory and manager access to the source mailbox databases, and be able to access Notes from outside applications such as CMT for Exchange (For more details, refer to Notes Migration Accounts Requirements).
• Make sure that you enable the Notes ID security for the option “Don’t prompt for password from other Notes-based programs (Reduces security)”.
• Make sure that you turn off Notes mail reminders in the Notes client preferences mail section.
• Make sure that you enable TCP/IP as the only port in the Notes client install preferences.
• SOAP Toolkit 3.0: It is a part of the IIS installation; you do not need to install it separately. (Need to install it manually if using Windows 2003.)
• .NET Framework 2.0 SP2
• You cannot have restrictions in your Group Policies or workstation policies that prevent the automatic creation of MAPI profiles or .pst files.
• You must disable any applications that take over or block the use of port 80 on the migration workstation.
• It is recommend that you log into the PC with an account that has at least "take ownership" rights to the mail store that is your migration destination, and that you log into the same domain as your migrations’ destination. If you are migrating to Exchange 2007 or 2010, then you must have Full Access rights.
• Make sure that any personal firewalls and the XP firewall is OFF and disabled as a service.
• Make sure that Antivirus software is disabled. Specifically, the real time scanning protection. Otherwise, migration throughout will be reduced and other issues can occur such as crashes in stressful states of migration workload. If it cannot be disabled, please exclude the following directories from scanning:
• C:\windows\temp and (%TEMP% if different)
• C:\Program Files\Binary Tree\CMT Universal
• C:\Exported PSTs (or the destination folder specified by the user for migrated PSTs)
• Make sure that WSUS, Intel LAN Desk, and other such programs are excluded from running on the migration workstations. These programs may halt migrations as their screens pop-up to run tasks as well as re-boots caused by these processes can interrupt migrations.
• Make sure that you turn off Automatic Windows updates.

Windows Migration Account Requirements


• Domain user account with:
• Local admin access to all control center(s) and migration stations
• Ability to install software
• Configure registry keys
• Full control access the server directories

Notes Migration Account Requirements


• Notes ID user account with:
• Access to read the Domino directory as a general notes client user
• Access to read the mail files for migration scope
If the Notes ID doesn’t have the required level of access, then you can perform any one of the following actions before migrating a user mail file or database:
• Add the ID to the user mail file or database ACL with the required rights.
• Add the ID to a Group with the required rights that is already in the user mail file or database ACL.
• Switch the ID to one that has the required access rights.
• Do not use the Notes Administrator Clients Full Access Administration feature as it is not considered an effective method for granting required level of access to the migrating user data. This is because the migration engine does not invoke the Notes client itself, and the Full Access Administration is often not applied to the session performing migration, which will cause the migration to fail. The Notes ID being used must have access granted in the ACL of the source data via either group membership or explicit membership as stated earlier.

Server Connection Documents

On each migration workstation, Server Connection documents may be required to provide access to some of the Notes/Domino servers. If connection documents are required, it is the customer’s responsibility to provide the appropriate Destination server address.

Onsite System Administrator

An onsite Notes System Administrator should be available to provide assistance with the Notes ID, Server Connection Documents, Mail-in Database Documents, signing of the CMT for Exchange database and any other system or network tasks. As indicated above, proper access rights are necessary for the migration to be performed and an onsite System Administrator can help ensure the migration completes in a timely fashion.

Microsoft Exchange Requirements

Please note that sufficient disk space must be available on the destination Exchange servers.

If migrating to Exchange 2003, it is recommended that you login to the migration workstation with an account that has at least take ownership rights to the mail store that is your migration destination, and that you are logging into the same domain that you are migrating into.

If migrating to Exchange 2007, the privilege level required to migrate to user mailboxes is Full Access.

If migrating to Exchange 2010, you must ensure that the migration workstation(s) being used have Outlook 2007 on it. Also, the privilege level required to migrate user mailboxes is Full Access.