How do I prepare Managed Clients to be migrated to another location? (NETIQKB53148)

  • 7753148
  • 02-Feb-2007
  • 12-Jan-2011


NetIQ AppManager 6.x
NetIQ AppManager 7.0.x


How do I prepare Managed Clients to be migrated to another location?
How do I move Managed Clients from one AppManager computer to another with the least amount of administrative overhead?


To migrate Managed Clients to a new AppManager computer:

  1. Run AMADMIN_SetPrimaryMS from the original Primary Management Server against all the agents you want to move.
  2. Configure the AMADMIN_SetPrimaryMS Knowledge Script with the new Management Server set as the Primary Management Server and the original Management Server as the Secondary Management Server.
  3. Add the affected Managed Clients to the new Management Server repository and run Discovery_NT to ensure communication is authorized.  You can substitute a different Discovery Knowledge Script if you are not monitoring Windows NT objects on the migrated agents.
  4. When you are ready to completely turn off any communication from the agent to the old repository, simultaneously drop the server from the old repository's tree view and run AMADMIN_SetPrimaryMS from the new Management Server, specifying only the new Management Server as Primary and leaving the Secondary Management Serverblank.

Additional Information

Formerly known as NETIQKB53148

If you do not run AMADMIN_SetPrimaryMS  before migrating the Managed Clients, you must cold start the agent services of each Managed Client with a -oa parameter to remove the site communication tables from the local repository.  In addition to this, the AllowMS registry key must be manually altered to include MS2 within the following location: 

HKEY_Local_Machine > Software > NetIQ > 4.0 > NetIQmc > Security > AllowMS

For registry changes to take effect, you must restart the AppManager NetIQ Client Resource Monitor service.

Although ideal, it is not necessary to configure the AMADMIN_SetPrimaryMS with a Secondary Management Server. The process of including the orginal Mangement Server as a secondary Management Server ensures the original Management Server repository will be able to communicate with and monitor the Managed Client in the event of failure with the new Management Server repository.