Issues addressed in AppManager Agent 7.0.25 Hotfix 71704 (NETIQKB71704)

AppManager Agent 7.0.25 Hotfix 71704 -Uusing the HashStringSHA1 function causes a memory leak in the NQCOMMON object.

Hotfix 71704 for the AppManager version 6.0.2 and 7.0.1 has been released to correct this issue.  To correct this issue, you will need to download and install Hotfix 71704 as indicated in this article or in the Readme file that is included with the Hotfix package from the following location:

https://www.netiq.com/f/downloads/download.asp?id=46AA2AC7-B34C-445A-AEB9-730D16A4FBB6

Why Install This Hotfix?

This hotfix resolves an issue where using the HashStringSHA1 function causes a memory leak in the NQCOMMON object. (ENG272145)

For more information about the issue resolved with this hotfix, see NetIQ Knowledge Base article NETIQKB71704.

System Requirements

This hotfix requires the following previous hotfixes:

Hotfix 71647, for Control Center.
Hotfix 71471, for the management server.

NetIQ Corporation recommends that you apply the following hotfixes before you apply this hotfix:

Hotfix 71470, for the Operator Console.
Hotfix 71473, for the Operator Web Console.
Hotfix 71516, for the AppManager repository.

This hotfix supports AppManager agents on the following operating systems and platforms:

• Windows 2000 Standard Server Service Pack 4 on 32-bit processors
• Windows 2000 Advanced Server Service Pack 4 on 32-bit processors
• Windows Server 2003 Service Pack 2 Standard and Enterprise editions on 32-bit, 64-bit, and Itanium processors
• Windows Server 2003 R2 Service Pack 2 Standard and Enterprise editions on 32-bit and 64-bit processors
• Windows Server 2008 Service Pack 2 Enterprise edition on 32-bit and 64-bit processors
• Windows Vista Service Pack 2 Enterprise edition on 32-bit and 64-bit processors
• Windows XP Service Pack 2 on 32-bit and 64-bit processors
• Windows XP Service Pack 3 on 32-bit and 64-bit processors
  

Contents of the Download Package

The download package includes the files necessary for the following installation scenarios:

Install a new version 7.0.25 agent.
Upgrade a version 6.0.2 or 6.0.3 agent to version 7.0.25.
Upgrade a version 7.0.1 or 7.0.2 agent to version 7.0.25.

Note
To upgrade a version 7.0 agent to version 7.0.25, first upgrade to version 7.0.1, and then upgrade the version 7.0.1 agent to version 7.0.25. For information about upgrading from version 7.0 to version 7.0.1, contact Technical Support.

Files to Install a New Agent or Upgrade a 6.0.2 or 6.0.3 Agent

The download package contains the following files for installing a new version 7.0.25 agent or upgrading a version 6.0.2 or 6.0.3 agent to version 7.0.25:

• AM7025_ReadMe71704.htm, this readme.
• In the New Agent Install and 6x Agent Upgrade folder:
  • NetIQ AppManager agent.msi, the Windows agent installation program.
  • AM70-WindowsAgent-7.0.25020.0.xml, the remote agent installation package. Use this package to install or upgrade more agents on remote Windows computers in your environment. For more information about remotely installing or upgrading agents, see Installing This Hotfix Remotely.
  • AM70-WinOS-7.5.208.0.msi, the AppManager for Windows module installation program.
  • AM70-WinOS-7.5.208.0.xml, the remote AppManager for Windows module installation package. Use this package to install the AppManager for Windows module on remote Windows computers in your environment. For more information about remotely installing the module, see Installing This Hotfix Remotely.

Files to Upgrade a 7.0.1 or 7.0.2 Agent

The download package contains the following files for upgrading a version 7.0.1 or 7.0.2 agent to version 7.0.25:

• AM7025_ReadMe71704.htm, this readme.
• In the 7.0.1 and 7.0.2 Agent Upgrade folder:
  • AM7025_Hotfix71704_Setup.exe, the hotfix setup program.
  • BaseInstall.dll
  • MFC71u.dll
  • msvcp71.dll
  • msvcr71.dll
  • Patch.ini
  • Setup Files, a folder that contains:
    • AM7025_Hotfix71704_MCSetup.msp, the Windows agent upgrade file. The hotfix setup program automatically runs this file to upgrade the Windows agent.
    • AM70-WindowsAgentUpdate-7.0.25020.0.xml, the remote agent upgrade package. Use this package to upgrade more agents on remote Windows computers in your environment. For more information about remotely upgrading agents, see Installing This Hotfix Remotely.
    • AM70-WinOS-7.5.208.0.msi, the AppManager for Windows module installation program.
    • AM70-WinOS-7.5.208.0.xml, the remote AppManager for Windows module installation package. Use this package to install the AppManager for Windows module on remote Windows computers in your environment. For more information about remotely installing the module, see Installing This Hotfix Remotely.

Installing This Hotfix

This hotfix supports the following installation scenarios:

Install a new version 7.0.25 agent.
Upgrade a version 6.0.2 or 6.0.3 agent to version 7.0.25.
Upgrade a version 7.0.1 or 7.0.2 agent to version 7.0.25.

Note
The version 7.0.25 agent installation program displays version 7.0.2 in the title bar.

Installing a New Agent or Upgrading a 6.0.2 or 6.0.3 Agent

If you are installing a new agent or upgrading a 6.0.2 or 6.0.3 agent, use the files in the New Agent Install and 6x Agent Upgrade folder.

To install a new version 7.0.25 agent or upgrade a version 6.0.2 or 6.0.3 agent to version 7.0.25:

Run NetIQ AppManager agent.msi on the computer where you want to install or upgrade the Windows agent.

Notes
To generate a log file for the Windows installer portion of the installation, type the following command from a command prompt on the computer where you want to install or upgrade the Windows agent:

msiexec /i "path to NetIQ AppManager agent.msi" /l*v "Windows_Installer_Log"

Windows_Installer_Log is the path to the Windows installer log file.
For example, "C:\Program Files\NetIQ\temp\NetIQ_Debug\AM7025_Hotfix71704_MCSetup.msp.log".

Option /L*v enables verbose output to the Windows installer log file.

If you are running Windows Server 2008 with User Account Control (UAC) enabled, you must run the installation program with administrative privileges. To run the installation program with administrative privileges:

• From the Start menu, right-click Command Prompt and select Run as.
• Select the administrator account and enter the password, then click OK.
• On the command line, type the command provided above.

Install the latest version of the AppManager for Windows module by running AM70-WinOS-7.5.208.0.msi on the computer where you installed or upgraded the agent, the AppManager repository computer, and the Control Center computer.

Discover the new or upgraded agent and update the Knowledge Scripts for the AppManager for Windows module on the Operator Console computer by running the Discovery_NT Knowledge Script.

For information about installing or upgrading more agents on remote Windows computers in your environment, see Installing This Hotfix Remotely.

For information about installing or upgrading agents in silent mode, see Installing This Hotfix in Silent Mode.

Upgrading a 7.0.1 or 7.0.2 Agent

If you are upgrading a 7.0.1 or 7.0.2 agent, use the files in the 7.0.1 and 7.0.2 Agent Upgrade folder.

To upgrade a version 7.0.1 or 7.0.2 agent to version 7.0.25:

Run AM7025_Hotfix71704_Setup.exe on the computer with the version 7.0.1 or 7.0.2 agent you want to upgrade.

Note
Because other AppManager components that do not have a version 7.0.25 agent share the installation program, the title bar on the AppManager Update Install and Finish screens displays version 7.0.1.

Install the latest version of the AppManager for Windows module by running AM70-WinOS-7.5.208.0.msi on the computer where you upgraded the agent.

For information about upgrading more agents on remote Windows computers in your environment, see Installing This Hotfix Remotely.

For information about upgrading agents in silent mode, see Installing This Hotfix in Silent Mode.

The PATCH.log file lists all changes and problems encountered during the installation process. The Windows installer log file, AM7025_Hotfix71704_MCSetup.msp.log, lists only the changes associated with the hotfix installation. By default, these files are located in the \NetIQ\Temp\NetIQ_Debug folder.

Installing This Hotfix Remotely

If you have the following AppManager components installed, you can install or upgrade more agents on remote Windows computers in your environment:

• AppManager repository (QDB)
• Management server
• Control Center console
• Windows agent

To remotely install a new version 7.0.25 agent or upgrade a version 6.0.2, 6.0.3, 7.0.1, or 7.0.2 agent to version 7.0.25:

• On the Control Center console Administration pane, select Packages under the Deployment folder.
• On the Tasks pane, click Check in Packages.
  • If you are installing a new version 7.0.25 agent or upgrading a version 6.0.2 or 6.0.3 agent, navigate to the New Agent Install and 6x Agent Upgrade folder and open AM70-WindowsAgent-7.0.25020.0.xml.
  • The Deployment Package Check in Status dialog box displays the status of the package check in.
  • If you are upgrading a version 7.0.1 or 7.0.2 agent, navigate to the 7.0.1 and 7.0.2 Agent Upgrade folder and open AM70-WindowsAgentUpdate-7.0.25020.0.xml from the Setup Files subfolder.
  • The Deployment Package Check in Status dialog box displays the status of the package check in.
• Configure a deployment rule to select the computers where you want to install or upgrade the agent.
• Repeat the steps above to use AM70-WinOS-7.5.208.0.xml to remotely deploy the latest version of the AppManager for Windows module.

For more information about remote installation, see the Control Center User Guide on the AppManager Documentation web site.

Known issue in the AppManager Agent

Formerly known as NETIQKB71704

Installing This Hotfix in Silent Mode

You can install or upgrade agents in silent mode.

Silently Installing a New Agent

To silently install a new version 7.0.25 agent, type the following command from a command prompt:

• msiexec.exe /i "path to NetIQ AppManager agent.msi" /qn MC_B_UPGRADE=0 INSTALLDIR="AppManager_Installation_Directory" additional parameters as described below /L*v "Windows_Installer_Log"

AppManager_Installation_Directory is the AppManager installation directory. For example, "C:\Program Files\NetIQ\".

Windows_Installer_Log is the path to the Windows installer log file.
For example, "C:\Program Files\NetIQ\temp\NetIQ_Debug\AM7025_Hotfix71704_MCSetup.msp.log".

Option /L*v enables verbose output to the Windows installer log file.

The additional parameters you can specify are as follows:

• MC_MSPRIMARY
  Primary management server name.
• MC_MSSECONDARY
  Secondary management server name.
• MC_B_MSPRISEC_REMOVEALLOWMSSTAR
  Remove communications authorization for all management servers to this computer during installation. The AllowMS registry key stores the list of management servers that are allowed to communicate with a managed client. The key uses an asterisk (*) to allow all management severs to communicate with a managed client when no primary management server is designated. If you set the primary management server during installation, the
• C_B_MSPRISEC_REMOVEALLOWMSSTAR parameter removes the asterisk from the AllowMS registry key. If you are not setting the primary management server during installation, this parameter indicates that the AllowMS registry key should be left unchanged until you run the SetPrimaryMS Knowledge Script.
• MC_B_PROXY
  Install the agent as a proxy:
  1 = Yes
  0 = No
• MC_B_WINUSER
  Run the agent using a Windows domain user account:
  1 = Yes
  0 = Use the Windows local system account.
• MC_WINDOMAINUSER
  Service account domain and user name under which the agent services will run. Use the format domain\username.
• MC_WINPWD
  Service account password under which the agent services will run.
• MC_MAILBOX
  Mailbox name when MAPI email option MC_B_MAPI=1.
• MC_PROFILE
  Exchange profile name when MAPI email option MC_B_MAPI=1.
• MC_EXCHSVR
  Exchange Server name when MAPI email option MC_B_MAPI=1.
• MC_B_PORT
  Change the default RPC ports where the management server and agents listen for communications from each other:
  1 = I will change the ports.
  0 = Use the default ports.
  The default ports are:
  9999 (management server listens for agent communications)
  9998 (agents listen for management server communications)
• MS_PORT
  RPC port number where the management server listens for agent communications. This option requires MC_B_PORT=1.
• MC_PORT
  RPC port number where the agent listens for management server communications. This option requires MC_B_PORT=1.
• MC_SECLEVEL
  Security level to use:
  0 = No security (clear text)
  1 = Encryption only
  2 = Management server authentication and encryption
• MC_SECPWD
  Encryption or authentication agent key file password. This option requires MC_SEVLEVEL=1 or 2.
• MC_B_AUTODISCOVERY
  Discover agent automatically:
  1 = Discover agent during installation.
  0 = Discover agent later using a Discovery Knowledge Script.
• MC_B_DISPLAYNAME
  Change agent computer display name for the computer on which the agent is being installed:
  1 = Yes
  0 = Use the default tree view name for the computer on which the agent is being installed.
• MC_B_MAPI
  Send e-mail automatically, using the MAPI protocol, as part of a Knowledge Script job:
  1 = Yes
  0 = No
• MC_B_MSPRIMARY_EXIST
  Primary management server is available:
  1 = Yes
  0 = No
• MC_B_MSSECONDARY_EXIST
  Secondary management server is available:
  1 = Yes
  0 = No
• MC_B_MSPRISEC
  Management server has passed the primary/secondary check:
  1 = Passed
  0 = Failed
• MC_B_MSPRISEC_REMOVESTAR
  Allow the anonymous management server to exchange reports with the agent:
  1 = No
  0 = Yes
• MC_B_REPORTAGENT
  Enable agent reporting capabilities:
  1 = Enable
  0 = Disable
• MC_B_ONMS
  Management server is present on the computer where the agent is being installed:
  1 = Yes
  0 = No
• MC_ALLOWMS
  For manual or AppManager setup installation, where the value depends on the MC_B_MSPRISEC parameter:
  MC_ALLOWMS = *; allows anonymous management server
  MC_ALLOWMS = primary management server, secondary management server; allows only primary management server/secondary management server to communicate
  For a remote installation, there are three cases:
  MC_ALLOWMS = * allows anonymous management server
  MC_ALLOWMS = ; does not allow anonymous management server
  MC_ALLOWMS = *; allows anonymous management server until primary/secondary for this agent is set
• MC_DISPLAYNAME
  Agent installation computer tree view name.
• MC_MDBPATH
  Default local repository path that is the local MDB folder location.
• MC_WINUSER
  Service account user name.
• MC_WINDOMAIN
  Service account domain number under which the agent will run.
• MC_WINPWDE
  Windows service account encrypted password under which the management server services will run.
• MC_INPUTXML
  XML input file for remote installation.
• MC_B_WEBSERVER
  Specify web server name to be used by the agent:
  1 = Yes
  0 = Use the default, which is domain name
• MC_WEBSERVER
  Deployment web server name to be used by the agent. This option requires MC_B_WEBSERVER=1.

Silently Upgrading a Version 6.0.2 or 6.0.3 Agent

You can silently upgrade a version 6.0.2 or 6.0.3 agent with the same configuration you specified when you installed the agent, or you can alter the configuration. For information about the configuration parameters you can alter, see Silently Installing a New Agent.

To silently upgrade a version 6.0.2 or 6.0.3 agent to version 7.0.25 using the configuration you specified when you installed the agent, type the following command from a command prompt:

msiexec.exe /i "path to NetIQ AppManager agent.msi" /qn MC_B_UPGRADE=1 /L*v "Windows_Installer_Log"

To alter the configuration, type the following command from a command prompt:

msiexec.exe /i "path to NetIQ AppManager agent.msi" /qn MC_B_REINSTALL=1 additional parameters as described in Silently Installing a New Agent /L*v "Windows_Installer_Log"

Windows_Installer_Log is the path to the Windows installer log file.
For example, "C:\Program Files\NetIQ\temp\NetIQ_Debug\AM7025_Hotfix71704_MCSetup.msp.log".

Option /L*v enables verbose output to the Windows installer log file.

Silently Upgrading a 7.0.1 or 7.0.2 Agent

To silently upgrade a version 7.0.1 or 7.0.2 agent to version 7.0.25, type the following command from a command prompt:

msiexec /qn /update "path to AM7025_Hotfix71704_MCSetup.msp" PATCHPACKAGE="MC" SERVICESTOSTOPSTART="netiqmc,netiqccm,netiqms,nqcqs" TERMINATEPROCESS="" REINSTALLMODE="omus" REINSTALL="ALL" /L*v "Windows_Installer_Log" INSTALLDIR="AppManager_Installation_Directory"

Windows_Installer_Log is the path to the Windows installer log file.
For example, "C:\Program Files\NetIQ\temp\NetIQ_Debug\AM7025_Hotfix71704_MCSetup.msp.log".

AppManager_Installation_Directory is the AppManager installation directory. For example, "C:\Program Files\NetIQ\".

Option /L*v enables verbose output to the Windows installer log file.