How do I manage a client computer from more than one AppManager site? (NETIQKB44809)

  • 7744809
  • 02-Feb-2007
  • 20-Oct-2010

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x

Situation

How do I manage a client computer from more than one AppManager site?
How do I manage a Windows or Unix client computer from more than one AppManager site?

Resolution

AppManager 6.0 can be configured to manage a Microsoft Windows or Unix client computer from more than one AppManager site.  For example, you can run jobs on a managed client computer from more than one AppManager site when you want to:

  • Migrate an agent to a different repository.
  • Store events and data in different repositories.

To manage a Microsoft Windows or Unix client computer from more than one site, you must manually perform some configuration tasks that vary depending on how your site is configured.  See the following sections for more information.

Managing a Windows client computer from more than one AppManager site

When installing the Windows agent, agent communication is automatically restricted to its designated primary and secondary management server.  To enable a Windows agent to communicate with a management server from another site, you must use the AMAdmin_AgentConfigMSRestrictions Knowledge Script to append the names of the management servers in the additional site to the agent's list of authorized management servers.  See the online help for information on using this Knowledge Script.

After you authorize the agent to communicate with the management servers from another site, from the other site use the AMAdmin_SetPrimaryMS Knowledge Script to designate the agent's primary and, optionally, its secondary management server.

Keep in mind that if you cold start the agent using the -oa option, the agent only maintains the primary and secondary management servers that you designated when you last ran the AMAdmin_SetPrimaryMS Knowledge Script.  After you cold start the agent using the -oa option, you would need to re-designate the primary and secondary management servers from the other site.

If your site uses secure communication (either encryption, or encryption and authentication) to communicate with Windows agents, you must:

  • Share the repository key information with the additional repository using the nqKeyGenWindows.exe utility, AND
  • Configure the additional repository to use the same security level for Windows communication. 

See Chapter 2, "Configuring site communication," in the Administrator Guide for more information.

 

Managing a Unix client computer from more than one AppManager site

The Unix agent automatically restricts its management server communication to the management servers you specified during installation OR the management servers that you designated using the AMAdminUNIX_SetPrimaryMS Knowledge Script.  Note that you should always run the AMAdminUNIX_SetPrimaryMS Knowledge Script after agent installation to properly designate the primary and secondary management server.  

To enable a Unix agent to communicate with a management server from an additional site, you must:

  • Edit the nqmcfg.xml and nqmtasks.xml files to include a copy of the <configuration> section for each management server you want to add, AND
  • In the <configuration> section, specify the host name or IP address of the management server, the security level of its site, and the location of the Unix agent key file, if applicable.

See Chapter 10, "Advanced configuration options for UNIX agents," in the Administrator Guide for more information.

If your site uses secure communic.
ation (either encryption, or encryption and authentication) to communicate with Unix agents, you can:

  • Share the repository key information with the additional repository using the nqKeyGenUNIX.exe utility AND configure the additional repository to use the same security level for Unix communication, OR
  • Set up a separate key for the additional repository if using authentication, OR
  • Use a different security level.

This option is NOT available with the Windows agent communication. See Chapter 2, "Configuring site communication," in the Administrator Guide for more information.

Additional Information

Formerly known as NETIQKB44809

Feedback service temporarily unavailable. For content questions or problems, please contact Support.