Pre-Installing Agents
In large distributed networks with sites connected by slow links, agent deployment from Migration Manager can take up all available bandwidth and the Migration Manager application might appear to hang.
This happens because Migration Manager has to transfer the agent setup packages to each remote server before it can start installation. The shared components setup (EMWShared.exe) is about 15MB and can take considerable time and bandwidth to be transferred.
Migration Manager for Exchange includes files necessary for creating the installation package to install the Exchange agents on remote Exchange servers. You can create a package of files that can be distributed to remote sites on any removable media, and local site administrators can install the agents before starting the migration process. The package setup creates all necessary folders and shares on servers and copies files to required locations.
The following files are located in the Migration Manager for Exchange installation folder on the console computer (the %Program Files%\Quest Software\Migration Manager\Exchange Data folder, by default):
- makepack.cmd—creates the installation package on the console computer
- srvsetup.cmd—setup file for servers
These batch files allow you to create an installation package that can be then distributed to remote locations without consuming network bandwidth.
These files do not eliminate the need to run the agent installation procedure in Migration Manager; they simply allow the setup files to be copied to the required locations in advance.
Creating an Installation Package
To create a remote agent installation package, take the following steps:
- Run makepack.cmd from the Migration Manager for Exchange installation folder. By default the installation package is created in the QMMEX Remote Setup Files subfolder of the Migration Manager installation folder, for example, C:\Program Files\Quest Software\Migration Manager\Exchange Data\QMMEX Remote Setup Files.
- To change the path to the installation package, provide a new path as a command-line parameter as in the following example:
makepack.cmd "C:\RemoteSitePack"
The created installation package contains two folders with the required agent files:
- Agents—Folder with agent setup files and hotfixes
- Rcmd—Folder with Quest Agent Installer files
The installation package also contains three .cmd files:
- srvsetup.cmd—Setup file for servers
When running the setup on remote servers, all components are by default copied to a subfolder called Aelita Exchange Migration Wizard, which is created in the %systemroot%\system32 folder. On Microsoft Exchange x64 the default shared folder is created in the %SystemRoot%\SysWOW64 folder. This subfolder is shared as QMMEx$ServerName$. On a non-cluster server this can be changed to the location of other Migration Manager components. Once the files from this installation package are installed, start the desired migration project and work with remote Exchange organizations using Migration Manager.
Installing Agent Files on a Server
To install the agent files from the installation package on a server, take the following steps:
- Copy all files from the installation package to a folder on the Exchange server or Directory Synchronization Agent host server.
- Run srvsetup.cmd. To change the default location of the DMM agent components, specify a new path as a command-line parameter as in the following example:
srvsetup.cmd "C:\DMM Components\"
|
|
NOTE: The path must end with a backslash. If the path contains spaces, it must be enclosed in quotation marks. |
Installing the Agents
Before deciding where to install agents, please read the Migration Manager Agent Servers section in the System Requirements and Access Rights document carefully. Some configurations are not supported by agents.
After the setup files are copied to the correct locations on the remote servers, run the normal agent installation procedure.
When you initiate agent installation using the console (by running the Install Agents Wizard or when setting up a new job), Migration Manager checks whether the setup files exist on the remote server and, if they do, does not transfer them across the network. It only creates the agent services running the setup packages with the necessary parameters.
Calendar Synchronization
Calendar synchronization allows for migration of the Calendar folder data. It is recommended that calendar data migration be performed in parallel with the mailbox and free/busy data migration so that the users can view other users’ free/busy data and can schedule meetings regardless of the environment they log on from.
|
|
Caution: If you are performing calendar synchronization in Microsoft Exchange 2007, it is recommended that the Public Folder database exists in your Exchange 2007 environment. |
To begin calendar synchronization, right-click the Calendar Synchronization node in the management tree and click Add Calendar Synchronization Job. This opens a dialog box that lets you select one of the following methods to synchronize calendars:
- Calendar Synchronization Job
- Office 365 Calendar Synchronization Job
- Legacy Calendar Synchronization Job
The guidelines for choosing the right type of job are in the Calendar Synchronization Process topic.
|
|
NOTE: Office 365 calendar synchronization is described in the dedicated Migrating to Microsoft Office 365 document. |
You can track the calendar synchronization progress using the Statistics dashboard. For information on how to do that, see Tracking the Migration Progress.