Is Agent Host the same as Alternate Host?
Can it just be easily introduced in the middle of a migration?
The answer is yes and no.
An Agent Host is not exactly an Alternate Host, the concept has slightly changed during the years.
If you already had a synchronization job configured and now decided to use another Agent Host (eg. support advised to use another agent) then you will first need to delete all existing collections and even the job (server pair) in QMM Exch, and then you need to commit the changes.
If you just re-create the job and select another server as Agent Host, and this server doesn't have any agents installed, then you will receive an error when committing the changes.
Correct procedure is the following:
decide which server will be used as Agent Host and then register this machine (not absolutely needed, but a good idea) and install the Shared Components and the Agents, the Agent Installation Wizard in QMM Exch can be used to accomplish this task.
Once the agents have been installed you can safely create the new job and select this new Agent Host and proceed to create collections.
Knowing this it is important to make sound decisions in advance, otherwise you will have to delete and recreate existing jobs.
But on the other hand creating a new job takes only few minutes, considering that collections can easily be populated via a DL, using an LDAP filter or an import file.
Summary: when deploying a new Agent Host in the middle of migration you will need to delete all old jobs and to commit changes, then you need to register the new agent and to install the agents and shared components, only then should you create the job, select the new agent and commit changes.
Another difference between an Alternate Host and an Agent Host is the following: in QMM 8.6.1 and older you could specify an Alternate Host for a server, and then when installing/uninstalling the agents and selecting the server the agents would be always installed/uninstalled from the Alternate Host machine. With Agent Hosts this is not the case anymore, the agents get installed/uninstalled directly on the machine which has been selected in the GUI.
Important: Please see QMM Release Notes for Agent Host requirements, when migrating to Exchange 2010 all agents dealing with
Exchange 2010 should meet specific requirements, some of them are: new MAPI CDO and Exchange 2010 Management Tools need to be installed, and it can be only a 64 bit machine (otherwise you will not be able to install Exchange 2010 Management Tools.
Installing Shared Components is very important, because this step also installs the Quest Migration Attendant for Exchange service.
When using Remote Users Collections (also called RUC or OST collections) please be aware that in this situation the MSA will have to deal with Exchange 2010 and to create mailboxes in the target environment, for more information and ideas please refer to the KB article SOL77709
https://support.quest.com/Search/SolutionDetail.aspx?id=SOL77709
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center