The NetIQ AppManager Suite delivers comprehensive systems management, including monitoring, reporting & analysis, diagnostics and resolution. It is designed to manage a variety of components – from physical hardware to server applications to end-user response time. AppManager is a much more efficient approach to systems management. The extensible, flexible nature of AppManager allows customers to achieve greater time to value with AppManager than other competitive solutions.

This document outlines why you should install the AppManager Suite, provides additions to the documentation, and identifies any known issues. For information about installing AppManager, see the Installation Guide for AppManager.

Why Install this Version?

AppManager 7.0.1 consolidates improvements that have been provided since the release of AppManager 7.0 and includes the following enhancements:

• From the Control Center Console, you can now configure preferences for managing software inventory information. To access these options, click Tools > Options > Deployment > Software Inventory. For information on how to configure the software inventory options, see the online help.
• AppManager console application support for the 32-bit version of Windows Vista Business and Enterprise. The AppManager console applications, including the Control Center Console, can now be installed on the 32-bit version of Windows Vista Business and Enterprise.
• AppManager agent support for the 32-bit version of Windows Vista Business and Enterprise. The AppManager agent can now monitor the operating system only on the 32-bit version of Windows Vista Business and Enterprise. Click here for more information.
• The Discovery_Cluster Knowledge Script now allows you to discover the virtual nodes of a cluster. With this improvement, application monitoring is accomplished from the virtual server perspective. AppManager automatically runs jobs and collects data on the appropriate physical node and maintains continuity across all nodes of a cluster.
• The AppManager Diagnostic Console has been updated to work with AppManager 7.0.1. AppManager Diagnostic Console 2.1 is provided on the AppManager Suite installation kit.
• The Web Recorder and URL Check Recorder provided with the AppManager ResponseTime for Web module are now integrated with the Control Center Console. Note that when updating from AppManager 7.0, this module is downloaded separately.
• The following Knowledge Scripts now properly report data values for CPU utilization on a computer with multiple CPUs:
  • NT_CPUByProcess
  • NT_CPULoaded
  • NT_CPUResource
  • NT_RunAwayProcesses
  • NT_TopCPUProcs

AppManager 7.0.1 includes updated application-monitoring support that has been provided since the release of AppManager 7.0. Note that if you are updating AppManager 7.0 components to Version 7.0.1, you must download and install the updated modules separately.

Updating AppManager from Version 7.0

This section provides information on updating from AppManager 7.0 to AppManager 7.0.1. Information on updating from AppManager 7.0 to AppManager 7.0.1 is not included in the Upgrade and Migration Guide for AppManager.

To update AppManager and Control Center 7.0 (build 7.0.315.0) core components to Version 7.0.1, you need the Service Pack 1 (SP1) update program. The SP1 update program, AM701_Update_Setup.exe, is included in this download package. Run the SP1 update program on the local computer to update the AppManager components on that computer. Do not directly run the other component installers in the \Setup Files folder.

The SP1 update program does not include module updates that have been provided since the release of AppManager 7.0. To get the latest AppManager 7.0 modules, you must download them from the NetIQ Extended Support web site and install them separately.

To upgrade AppManager 6.0.2 (build 6.0.58745.285) components to Version 7.0.1, and to install AppManager 7.0.1 components, you need the AppManager 7.0.1 Windows installation kit. You can download the AppManager 7.0.1 Windows installation kit from NetIQ Extended Support web site.

For information on upgrading the AppManager UNIX agents to Version 7.0.1, see the Release Notes on the AppManager 7.0.1 UNIX installation kit.

This download package allows you to update AppManager 7.0 components to AppManager 7.0.1. See the following topics for more information:

• How the AppManager SP1 Update Program Works
• The Most Essential Update Procedures

How the AppManager SP1 Update Program Works

When the SP1 update program starts, it automatically identifies all relevant AppManager components on a computer. In general, the update program automatically updates all components on a computer. However, if you have more than one AppManager repository on a SQL Server computer, you must run the update program more than once on the repository computer to update each AppManager repository separately. This update program includes updates for all AppManager 7.0 (build 7.0.315.0) components.

The SP1 update program provides information about which components will be updated and asks if you want to proceed with the update. If you proceed with the update, the update program updates all the listed components. If you cancel, the components are left untouched. You cannot update selected components; you must update all components on a computer.

After the update finishes, you can find a record of changes made and problems encountered in a file named PATCH.log, which can be found in the \NetIQ\Temp\NetIQ_Debug folder.

The Most Essential Update Procedures

Update your AppManager 7.0 components in the order shown below by running the SP1 update program on the local computer.

If you have more than one AppManager component on a computer, do not restart the computer until the SP1 update program completes its update of all AppManager components on the computer. Click here for more information.

1. AppManager repository. If you are using Control Center, update the primary AppManager repository first. If you installed the AppManager repository on a clustered server, or on a local node of a cluster, run the update program on all nodes in the cluster.

   If you have more than one AppManager repository on a computer, you must run the update program separately to update each AppManager repository. The update program does not automatically update all AppManager repositories on the SQL Server computer.

   Make sure you close any AppManager programs that are running on the computer before you update the repository. Temporarily disconnect all repository clients (for example, console programs, the management server, the web management server), then restart them after the update:

   1. Stop all AppManager console programs (for example, close any open Operator Consoles connected to the repository to be updated).
   2. If the management server is on a different computer than the repository, stop the NetIQ AppManager Management Service. (If it is on the same computer as the repository, the management server is stopped, upgraded, and restarted automatically.) If you have multiple management servers, be sure to stop the NetIQ AppManager Management Service on all of them.
   3. Disconnect any additional connections to the repository (for example, if isql or SQL Server Enterprise Manager are connected to the repository, shut down the connections before updating).

   The update program does not include module updates that have been provided since the release of AppManager 7.0. To install the Knowledge Scripts provided with an updated module, you must download the updated AppManager module from the NetIQ Extended Support web site and run the module setup program on the repository computer. To access this web site, you must have a MyNetIQ account.

2. AppManager management server. If you installed the AppManager management server on a clustered server, or on a local node of a cluster, run the updater program on all nodes in the cluster. You do not need to stop running jobs. The updater stops the management server during the update and then restarts it when finished. Note that Microsoft XML Parser 6.0 SP1 must be installed, however, the SP1 update program does not validate this requirement.
3. AppManager Web management server. Before updating, close any Operator Web Consoles that are attached to the Web management server you are updating. The update program prompts you to temporarily stop the Web publishing service during the update, and it restarts the Web publishing service when the update is finished.
4. AppManager consoles (which includes the Operator Console, Chart Console, and Security Manager). Before updating console programs, close any console programs that are running. The update does not change any of your preference settings.

   The update program does not include module updates that have been provided since the release of AppManager 7.0. To install the online help provided with an updated module, you must download the updated AppManager module from the NetIQ Extended Support web site and run the module setup program on the console computer. To access this web site, you must have a MyNetIQ account.

5. AppManager report agent. After you update the report agent:
   • Run AMAdmin_SetReportPaths to update the base output path for the report agent. You cannot view existing reports until you update the base output path. If you previously configured the URL mapping parameter, be sure to update this parameter as well. Note that the configuration of the URL mapping parameter has changed. See the online help for more information.
   • If you changed the report footer, for example, to change to the report logo, run the AMAdmin_ChangeFooter Knowledge Script to update the footer configuration.
6. Control Center repository.
7. Control Center Command Queue Service.
8. Control Center Deployment Web Service.
9. Control Center Deployment Service.
10. AppManager agents and managed objects. See Upgrading AppManager Agents on Windows for more information.

Updating AppManager Agents on Windows

This topic assumes that you have upgraded your AppManager and Control Center core components to Version 7.0.1.

In an ideal world, you would immediately upgrade all of your AppManager agents with each new release. Naturally, this provides the most efficient and predictable environment for monitoring your systems and applications. However, we recognize that for practical reasons you may have managed computers running differing levels of AppManager agents and managed objects.

This topic covers:

• Before You Start
• Centrally Updating Remote Managed Computers
• Upgrading Jobs on Managed Windows Computers

Before You Start

To update AppManager 7.0 (build 7.0.315.0) agents to Version 7.0.1, you can run the AppManager SP1 update program, AM701_Update_Setup.exe on the local computer.

If you are updating an agent from AppManager 7.0, you must also download the AppManager module updates you want and install them separately. You can download updated AppManager modules from the NetIQ Extended Support web site. To access this web site, you must have a MyNetIQ account.

To upgrade AppManager 5.0.1 (build 4.6.204.0) or 6.0.2 (build 6.0.58745.285) agents to Version 7.0.1, you need the AppManager 7.0.1 Windows installation kit. You can download the AppManager 7.0.1 Windows installation kit from NetIQ Extended Support web site.

Centrally Updating Remote Managed Computers

Use the Control Center Console to deploy updates to remote AppManager 7.0 agents and to upgrade remote AppManager 5.0.1 or 6.0.2 agents to Version 7.0.1. Depending on the version of the agent, the deployment rule and package you need varies. To:

• Update an AppManager 7.0 agent, use the NetIQ AppManager Windows Agent 7.0 to 7.0.1 Update installation package. For your convenience, a default rule is created to install the agent update package. Configure the AppManager for Windows Agent 7.0 to 7.0.1 Update rule to select the AppManager 7.0 agents you want to update. When configuring the rule to select the target computers, do not select computers with the AppManager 5.0.1 or 6.x agent. Click here for more information.
• Upgrade an AppManager 5.0.1 or 6.x agent, configure the NetIQ AppManager Windows Agent installation package to upgrade the agent. The AppManager 7.0.1 version of the agent installation package is 7.0.101xx.0. For your convenience, a default rule, AppManager for 7.0.1 WindowsAgent, is created to install the 7.0.1 version of the agent installation package.

  Note that if you previously installed or upgraded to AppManager 7.0, the AppManager 7.0 version of the AppManager for WindowsAgent deployment rule and the NetIQ AppManager Windows Agent installation package, which are both version 7.0.315.0, are not removed. To avoid generating deployment tasks with the older 7.0 version of the agent installation package, you should disable this rule.

In either case, the agent packages do not automatically update application-monitoring support on the agent. For more information on using the Control Center Console to deploy the AppManager agent, see the Control Center Console online help or the Control Center User Guide for AppManager.

Upgrading Jobs on Managed Windows Computers

To provide the most efficient and predictable environment for monitoring your systems and applications, NetIQ Corporation recommends that you update the Windows agent and managed objects to Version 7.0.1 before you update the existing jobs on the upgraded agent.

If you are updating from AppManager 7.0, you must download updated AppManager modules from the NetIQ Extended Support web site and install them separately. The AppManager SP1 update program does not include module updates that have been provided since the release of AppManager 7.0. Job upgrade information for AppManager modules is provided with the module documentation.

Click here for a list of modules that have been updated since AppManager 7.0.

In addition, the following Knowledge Scripts have been updated with this release:

• Action_DosCommand
• Action_SMTPMail
• AMAdmin_ChangeFooter
• AMAdmin_SetDeploymentWebService
• AMAdmin_SetReportPaths
• AMAdminUNIX_SetSecurityLevel
• Async_NTEventLog
• Discovery_UNIX
• General_MachineDown
• General_PingMachine
• NT_ConfigLogicalDisks
• NT_ServiceDown
• NT_ServiceDownLR
• NT_TopCpuProcs
• UNIX_ApplicationProcessMonitor
• UNIX_AsciiLog
• UNIX_CpuByProcess
• UNIX_CpuLoaded
• UNIX_CpuResources
• UNIX_CPUUtil
• UNIX_DNSConnectivity
• UNIX_DNSHealth
• UNIX_DNSReplication
• UNIX_FailedLogon
• UNIX_FileSystemSpace
• UNIX_FileSystemSpaceLC
• UNIX_GeneralCounter
• UNIX_LargeDir
• UNIX_LogicalDiskBusy
• UNIX_LogicalDiskIO
• UNIX_LogicalDiskIO26
• UNIX_LogicalDiskUtilization
• UNIX_MemByProcess
• UNIX_MemShortage
• UNIX_MemUtil
• UNIX_NetInterfacesCollision
• UNIX_NetInterfacesDown
• UNIX_NetInterfacesErrors
• UNIX_NetInterfacesIO
• UNIX_PagingHigh
• UNIX_PhysicalDiskBusy
• UNIX_PhysicalDiskIO
• UNIX_PingMachine
• UNIX_PrinterQueue
• UNIX_PrivilegedProcs
• UNIX_ProcessDown
• UNIX_Processes
• UNIX_ProcessUp
• UNIX_RemoteProcessDown
• UNIX_RunAwayProcs
• UNIX_SwapLow
• UNIX_SystemUpTime
• UNIX_TopCpuProcs
• UNIX_TopMemoryProcs
• UNIX_ZombieProcs

Use the AMAdmin_UpgradeJobs Knowledge Script to update existing jobs to take advantage of the improvements in the corresponding 7.0.1 Knowledge Script. For more information, see the Knowledge Script online help.

Performing a Silent (Non-Interactive) Update

You can update the following AppManager 7.0 components to 7.0.1 by running a command that provides information required by the update program.

When running MSI from the command line, make sure you specify the path to the required AppManager .MSP file and specify the path where you want the resulting log file to be created.

• AppManager agent

  msiexec /p "<install_dir>\Setup Files\AM701_Update_MCSetup.msp" /qn REINSTALLMODE=omus REINSTALL=ALL PATCHPACKAGE="MC" SERVICESTOSTOPSTART="netiqms,netiqmc,netiqccm" TERMINATEPROCESS="" /L* "<log destination>\AM701_Patch_MCSetup.msp.log"

• AppManager management server

  msiexec /p "<install_dir>\Setup Files\AM701_Update_MSSetup.msp" /qn REINSTALLMODE=omus REINSTALL=ALL PATCHPACKAGE="MS" SERVICESTOSTOPSTART="netiqms" TERMINATEPROCESS="" /L* "<log destination>\AM701_Patch_MSSetup.msp.log"

• AppManager web management server

  msiexec /p "<install_dir>\Setup Files\AM701_Update_WMSSetup.msp" /qn REINSTALLMODE=omus REINSTALL=ALL PATCHPACKAGE="WS" SERVICESTOSTOPSTART="" TERMINATEPROCESS="" /L* "<log destination>\AM701_Patch_WMSSetup.msp.log"

• AppManager Operator Console

  msiexec /p "<install_dir>\Setup Files\AM701_Update_UISetup.msp" /qn REINSTALLMODE=omus REINSTALL=ALL PATCHPACKAGE="UI" SERVICESTOSTOPSTART="netiqmc,netiqccm,netiqms" TERMINATEPROCESS="" /L* "<log destination>\AM701_Patch_UISetup.msp.log"

General Notes

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact NetIQ Solutions Support (www.netiq.com/support).

• Running Programs on Vista
• Accessing Modules
• Upgrade Issues
• Installation Issues
• Console Application Issues
• Agent Issues on Windows
• Knowledge Script Issues
• Documentation Issues

Running Programs As Administrator on Windows Vista

When running an AppManager program on Windows Vista, you must run the program as an Administrator.

To run a program as an Administrator, open the Command Prompt window as an Administrator by right-clicking the Command Prompt program, cmd.exe, and clicking Run As Administrator. On Windows Vista, after you open the Command Prompt as an Administrator, you can run AppManager programs such as:

• An MSI package, for example, NetIQ AppManager agent.msi, to perform a silent installation of the AppManager agent. Note that to run an MSI package as an Administrator, you must do so from a Command Prompt.
• An executable, for example, ServiceMapImageExporter.exe, to export a Service Map view to an image file.

To view charts in the Operator Web Console on Windows Vista:

1. You must start the Operator Web Console as an Administrator.
2. After you start Internet Explorer as an Administrator, start the Operator Web Console by specifying the following URL: http://web-server/netiq/login.asp where web-server is the name of the AppManager Web Management Server.
3. After you log into the Operator Web Console, you must download and install the chart component, NetIQAMChartComponent.exe, on the Operator Web Console computer:
1. If the Operator Web Console link to Charts does not work, specify the URL to the AppManager Chart Component: http://web-server/netiq/download/NetIQAMChartComponent.exe.
2. Save the download file to the Vista computer. Do not run the executable program.
3. On the Vista computer, view the Path system variable by opening System Properties > Advanced > Environment Variables. If you do not see an entry to \NetIQ\Common\Bin, append a path entry to specify where the AppManager Chart Component should be installed, for example, C:\NetIQ\Common\Bin, and restart the Vista computer.
4. Open a Command Prompt and choose the option to Run as Administrator.
5. In the Command Prompt, change directories to the location where you saved NetIQAMChartComponent.exe and run the setup program.

Accessing Module Updates

• Updated application-monitoring support for AppManager 7.0.1 is available from the NetIQ web site. Before you install or upgrade to AppManager 7.0.1, check the NetIQ Extended Support web site for the latest application-monitoring support. You can also use this link to access new and updated AppManager modules from the NetIQ Web Site for evaluation and production use. To access this page, you must have a MyNetIQ account.
• If you are upgrading from AppManager 6.0.2, the modules listed below are automatically included. However, these modules are not included when you update from AppManager 7.0 and must be downloaded separately:
  • AppManager ResponseTime for Web
  • AppManager SNMP Toolkit for Windows
  • Call Data Analysis
  • Cisco CallManager (4.x and earlier)
  • Cisco CallManager Express
  • Cisco Integrated Contact Distribution
  • Cisco Intelligent Contact Management
  • Cisco Interactive Voice Response
  • Cisco IP Telephony Security
  • Cisco Unified CallManager (5.0 and later)
  • Cisco Unity
  • Cisco Unity Express
  • Citrix MetaFrame
  • Dell OpenManage
  • HP Compaq Insight Manager (CIM)
  • Lotus Domino
  • Nortel BCM
  • Nortel BCMx
  • Nortel Communications Server 1000
  • Nortel Contact Center
  • Microsoft Cluster Server
  • Microsoft SharePoint 2007
  • Microsoft SQL Server
  • Oracle Database (UNIX)
  • Siemens ServerView
  • Symantec Backup Exec

  If you are updating from AppManager 7.0, you must download and install the updated modules separately.

Upgrade Issues

• When using the Control Center Console to deploy the NetIQ AppManager Windows Agent 7.0 to 7.0.1 Update installation package to AppManager 7.0 agents, if the deployment rule selects target computers with an AppManager 5.0.1 or 6.x agent, Control Center incorrectly generates a deployment task for AppManager 5.0.1 and 6.x agent computers. If you approve the deployment task, the task fails with the following error:

  Unable to complete deployment to machine computer name. Details: Unable to invoke installation command - exception: Could not find file "C:\WINDOWS\temp\WmiRel\nqAD_40c4405c-0d31-48a8-90cc-779b0678800d.err".

  To resolve this problem, reconfigure the task to upgrade the AppManager 5.0.1 or 6.x agent by deploying the 7.0.101xx.0 version of the NetIQ AppManager Windows Agent installation package. Click here for more information.
• If you deploy the AppManager 7.0.1 agent update to AppManager 7.0 agents, the update is installed successfully but the updated 7.0.1 agent does not automatically report its updated software inventory to the Control Center Deployment Web Service.

  To avoid generating a duplicate deployment task to update the agent on the remote computer, do not delete the computer's deployment task until the agent reports its updated software inventory. By default, the agent reports its software inventory every 6 hours.

  Alternatively, you can force the agent to report its software inventory by:

  • Manually restarting the agent
  • Installing or removing another package on the agent, for example, upgrading a module

  Note that if you deploy the AppManager 7.0.1 agent update to the same computer more than once, the task completes successfully.

• When updating the AppManager repository or the Control Center repository computer from AppManager 7.0 to 7.0.1, if there is more than one AppManager 7.0 component on the computer, the SP1 update program incorrectly prompts you to restart the computer before it updates all of the components on the computer. The SP1 update program immediately prompts for a reboot after updating the AppManager repository and the Control Center repository.

  To enable the SP1 update program to update all AppManager components on the computer, if you are prompted to restart the computer before all components are updated, click the No, I will restart my computer later option. After all components on the computer are updated, the update program indicates it is finished and you can now restart the computer to complete the update.

  Note that if you restart the computer before all AppManager components are updated, the other AppManager components on the computer are not updated to version 7.0.1. To resolve this problem, run the SP1 update program on the computer again to complete the update.

• StartPoint Knowledge Script Groups are obsolete. The AppManager 6.0.2 versions of the StartPoint Knowledge Scripts and reports are included with AppManager 7.0. These Knowledge Scripts and reports have not been updated for AppManager 7.0.

  If you have created ad hoc StartPoint jobs in AppManager 6.0.2, after you upgrade, you cannot view the job properties of the StartPoint job. StartPoint jobs that are run as part of a Knowledge Script Group, including policy-based jobs, work properly. If you are currently running StartPoint Knowledge Scripts and reports, as part of your upgrade process, you should plan to replace them with the corresponding AppManager 7.0 Knowledge Script or report.

• After you upgrade the AppManager core components, run AMAdmin_SetReportPaths to update the base output path for the report agent. You cannot view existing reports until you update the base output path. If you previously configured the URL mapping parameter, be sure to update this parameter as well. Note that the configuration of the URL mapping parameter has changed. See the online help for more information.
• When upgrading the AppManager management server on a cluster, the pre-installation check does not validate whether Microsoft XML parser 6.0 SP1 is installed. To upgrade the AppManager management server, Microsoft XML Parser 6.0 SP1 must be installed on all nodes in the cluster. For your convenience, the setup program for the 6.0 SP1 version of the Microsoft XML Parser is included on this installation kit in the \Prerequisites\Microsoft XML Parser folder.
• When updating the AppManager 7.0 management server, the update program does not validate whether Microsoft XML parser 6.0 SP1 is installed. Microsoft XML Parser 6.0 SP1 must be installed on the management server computer. You can download the 6.0 SP1 version of the Microsoft XML Parser from the Microsoft web site.
• When using the AMAdmin_UpgradeJobs Knowledge Script to run an Instant Check Query based on Agent build IDs, the agent build identifier information that is displayed does not match the version of the agent. There is no workaround for this problem.
• To install new Control Center 7.0.1 components on a computer where the AppManager 6.0.2 repository or Operator Console are configured to work with Control Center 6.0.2, you must:
  1. Make sure the AppManager 6.0.2 repository is not currently managed by Control Center. In the Control Center Console, click File > Manage Repositories, and in the Manage Repositories dialog box, if necessary, select the repository and click Remove.
  2. Uninstall the Control Center 6.0.2 patch that is applied to the AppManager repository and Operator Console. In Add/Remove Programs, select NetIQ AppManager Control Center and click Remove.
  3. Run the AppManager setup program to upgrade the AppManager 6.0.2 repository and Operator Console to AppManager 7.0.1, and then install the Control Center 7.0.1 components.
• To upgrade AppManager 7.0.1 on Microsoft Windows XP and Microsoft Windows Server 2003, you should disable Data Execution Prevention (DEP). If Data Execution Prevention is enabled, it can prevent you from installing AppManager and Control Center components, including the AppManager repository and management server.
• As of AppManager 7.0.1, NetIQ no longer provides Knowledge Base content for AppManager Knowledge Scripts. You can continue to find information about any Knowledge Script in the AppManager Help.
• When updating AppManager 7.0 components to version 7.0.1, the file version information is only updated when the file is updated as part of this service pack. For example, this service pack does not update LicenseManager.exe. The Version tab of the File Properties dialog box for LicenseManager.exe indicates the AppManager 7.0 version is 7.0.315. The file version number for components that are updated with this service pack is 7.0.100xx.
• When using Control Center deployment to upgrade a remote Windows agent, the managed objects on the remote computer are not automatically upgraded when you upgrade the agent. For example, to upgrade a remote managed computer with both the AppManager for SQL Server and AppManager for IIS modules, you can create a different rule to upgrade each module, or configure the rule that upgrades the agent to also upgrade the SQL and IIS modules.

  To upgrade the managed objects on a remote computer, you must first upgrade the AppManager agent. To avoid generating unwanted deployment tasks, do not configure a rule to install all of the modules in your environment. Some installation packages, such as ResponseTime modules, do not perform a pre-installation check and will always generate a deployment task.

  To validate the managed object versions on a managed client computer, use the ReportAM_CompVersion report.

• Migrating the AppManager repository database from Microsoft SQL Server 2000 to Microsoft SQL Server 2005 requires additional manual steps. Before you migrate the AppManager repository database, see the Upgrade and Migration Guide for AppManager for information about how to migrate the database successfully.
• To upgrade AppManager core components and Control Center to version 7.0.1, you must upgrade these components from the most recent version. AppManager 7.0.1 allows you to directly upgrade:
  • AppManager 6.0.2 core components
  • Control Center 6.0.2.1 components
  If your AppManager core and Control Center components are an earlier version, you must upgrade them to the versions listed above and then upgrade to version 7.0.1.
• If you configure a rule-based management group to select computers based on custom property value information, only computers with the AppManager 7.0 (or later) agent are displayed. If you have AppManager 6.0.2 (or earlier) agents, you must upgrade them to version 7.0 (or later) to include them in a rule-based management group that selects computers based on custom property information.
• If you want to install AppManager Knowledge Base, you must download the latest version of the application.

  AppManager Knowledge Base is not included with AppManager 7.0 installation kit and is only available from the NetIQ web site.

  To download this application, check the NetIQ Extended Support web site. Use this link to access new and updated AppManager modules from the NetIQ Web Site for evaluation and production use. To access this page, you must have a MyNetIQ account.

• As of AppManager 7.0.1, NetIQ no longer provides Knowledge Base content for AppManager Knowledge Scripts. If you need information on a Knowledge Script, you can continue to access the Help for the Knowledge Script from the Values tab of the Job Properties dialog box.
• Backward compatibility with AppManager 6.0.2 repositories. Control Center 7.0.1 can manage AppManager 6.0.2 repositories to some extent as described below. To fully utilize all the capabilities of Control Center 7.0.1, you should upgrade all of your managed repositories to version 7.0.1:
  • Repositories
    • Register repositories to Control Center
    • Un-register repositories from Control Center
  • Management Group Members
    • Add repository views to a management group
    • Remove repository views from a management group
    • Add repository server groups to a management group
    • Remove repository server groups from a management group
    • Add rules to a management group is not supported
    • Add wildcards to a management group is not supported
  • Jobs
    • Synchronize jobs to the Control Center repository
    • Start existing jobs
    • Stop existing jobs
    • Close existing jobs
    • Delete existing jobs
    • Create jobs (ad hoc and policy) is not supported
    • Modify jobs (ad hoc and policy) is not supported
    • View job properties is not supported
  • Events
    • Synchronize events to the Control Center repository
    • Acknowledge existing events
    • Close existing events
    • Delete existing events
    • Update event comment
  • Servers
    • Synchronize servers to the Control Center repository
    • Add Computer to a server group
    • Delete computer from repository
    • Enable maintenance mode (status not synchronized between management groups)
    • Disable maintenance mode (status not synchronized between management groups)
• AppManager users who belong to a custom AppManager role must be updated after upgrade completes. If you have configured a custom AppManager role for an AppManager user, you must refresh the role for each user after you upgrade. The refresh is required to enable the user who belongs to that custom role to log into the AppManager console applications. In the treeview of the Security Manager:
  1. Select a user who belongs to a custom role.
  2. Change the role to a standard, out-of-the-box role, for example, the Administrator role.
  3. Change the role back to the custom role that given previously.
  4. Click Apply.
  5. Repeat these steps for each AppManager user who belongs to a custom role.
• After you upgrade to Control Center 7.0.1, you must manually update your existing Control Center permission sets. In addition, you must now associate a user group with a particular permission set. After you upgrade to Control Center 7.0:
  1. Update your existing Control Center permissions sets:
     1. In the Control Center Console, click File > Manage Security.
     2. In the Manage Security dialog box, click Permission Sets.
     3. Click a permission set and click Modify to update the permission set to work with Control Center 7.0.
     4. In the Permission Set Properties dialog box, validate the permissions you want are given and click OK to save your changes.
     5. Repeat these steps for each Control Center permission set.
  2. Configure your existing Control Center user groups to specify a particular permission set:
     1. In the Control Center Console, click File > Manage Security.
     2. In the Manage Security dialog box, click User Groups.
     3. Click a user group and click Modify.
     4. In the User Group Properties dialog box, select the permission set you want and click OK to save your changes.
     5. Repeat these steps for each Control Center user group.
  3. Validate your management group permissions.
     1. In the Control Center Console, right-click a management group and click Properties.
     2. In the Properties dialog box, click the Security tab.
     3. In the Security tab, verify that each user group is configured with the correct permission set. If necessary, add and remove user groups as needed.
     4. Repeat these steps for each management group.
• If Control Center resides in a semi-distributed or distributed environment and there are AppManager repositories using Windows Authentication you may see the error "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON." If you receive that error, you should configure Kerberos delegation to properly perform authentication. For more information about how to configure Kerberos delegation, see Microsoft Corporation Technical Support. Alternatively, you can configure SQL Server authentication on the AppManager repository that is raising an error in the Cache Manager to use SQL Server and Windows authentication.
• If you upgrade a Control Center 6.0.2.1 computer that is also configured with AppManager 6.0.2 console applications, after you upgrade Control Center, the splash screen that is displayed when you open an AppManager 6.0.2 console application is incorrectly updated to indicate the console version is 7.0.1. To resolve this problem, upgrade the Appmanager components on the computer. Note that the correct version of the AppManager console application can be displayed by opening the application and clicking Help > About.

Installation Issues

• To install a new Control Center component on a computer where a Control Center component is already installed, in Add/Remove Programs, select NetIQ AppManager Control Center and click Modify. In the Select Features dialog box, simply select the Control Center components you want to add. This is required, for example, when you have upgraded the Control Center repository from 6.0.2.1 to 7.0.1, and you want to install the Control Center Deployment Web Service.

  Do not deselect the components that are already installed. Any Control Center components that are installed will not be reinstalled. If you deselect a component, it will be uninstalled.

• To install a new AppManager 7.0.1 component on a computer where you have previously installed an AppManager 7.0 component, you must install the 7.0 version of the component and then update it to 7.0.1.
• When uninstalling an AppManager evaluation where you have installed all AppManager components on the same computer, the uninstall process encounters an error when attempting to uninstall the AppManager agent before the uninstalling the AppManager management server. To resolve this problem, in Add/Remove Programs, uninstall the NetIQ AppManager Management Server, then uninstall the NetIQ AppManager Agent.
• When performing a silent installation of Control Center and using the /v option to specify command-line options, you must enclose the command-line options in quotation marks. For example, to install the Control Center Console on the E:\ drive, specify:

  netiqccsetup.exe /s "/v CC_CONSOLE=1 INSTALLDIR=E:\Program Files\NetIQ CC_AD_SERVICE=0 CC_AD_WEBSERVICE=0 CC_CCDB=0 CC_CQS=0"

• Control Center Deployment Service. The Deployment Service must be configured to run as LocalSystem.
• Control Center Deployment Web Service. To install the Deployment Web Service:
  • IIS must installed with the service pack updates required by AppManager. If you installed IIS after installing a service pack for Windows 2003 Server, you must reapply the current Windows service pack to update IIS to the same service pack level.
  • The IUSR_ user account must be given permission to the \NetIQ\AppManager\web folder. If you did not install AppManager on the system drive, for example, AppManager is installed on the E:\ drive and IIS installed on the C:\ drive, you must give the IUSR_ user account permission to the \NetIQ\AppManager\web folder on the E:\ drive. By default, IIS does not give IUSR access to files on a different drive.
  • Microsoft BITS and ASP.Net must be installed and enabled.

• AppManager management server. When installing the AppManager management server on a cluster, the pre-installation check does not validate whether Microsoft XML parser 6.0 SP1 is installed. To install the AppManager management server, Microsoft XML Parser 6.0 SP1 must be installed on all nodes in the cluster. For your convenience, the setup program for the 6.0 SP1 version of the Microsoft XML Parser is included on this installation kit in the \Prerequisites\Microsoft XML Parser folder.
• The Control Center setup program incorrectly allows you to install the Control Center Command Queue Service and the Deployment Service on Windows Vista. Do not install these components on Windows Vista. The setup program will install the components but they will not work properly.
• On Windows Vista, Windows Defender detects the AppManager agent as a potential risk. For more information, see the Installation Guide for AppManager.
• If you want to monitor the applications listed below, you must first download the corresponding AppManager 7.x module. AppManager 7.0.1 consolidates most of the AppManager monitoring support for applications. However, monitoring support for the following applications is only available from the NetIQ web site and is not included with the AppManager 7.0.1 installation kit:
  • Apache Web Server
  • AppManager for SNMP (UNIX)
  • BEA WebLogic Server
  • VMWare Virtual Center

  To download the latest AppManager 7.x application-monitoring support, check the NetIQ Extended Support web site. To access this page, you must have a MyNetIQ account.

• If you want to install AppManager Knowledge Base, you must download the latest version of the application.

  AppManager Knowledge Base is not included with AppManager 7.0.1 installation kit and is only available from the NetIQ web site.

  To download this application, check the NetIQ Extended Support web site. Use this link to access new and updated AppManager modules from the NetIQ Web Site for evaluation and production use. To access this page, you must have a MyNetIQ account.

• AppManager 7.0 works with Analysis Center 2.5. You do not need to install the Analysis Center hotfix for the AppManager UNIX agent that is referenced in the Analysis Center 2.5 release notes. This hotfix is included with AppManager 7.0.
• Agent deployment task incorrectly created for management server when the agent is already installed. If you configure a rule to install the AppManager agent and you specify a range of target computers that includes the management server, a deployment task is incorrectly created for the management server computer. To resolve this problem, reject the task or configure the target computers for the rule to not select the management server computer.
• When installing or upgrading the NetIQ AppManager Control Center Command Queue Service, if the Log On As Account for the SQLServerAgent service is specified using the username@domainaccount format, NetIQ recommends choosing the setup option to Use the account the CQS is using. If you do not choose this option, you must instead choose the Use Windows default service account option, click Next, and in the error message dialog box, click OK to then specify the correct domain, user name, and password. The setup program does not support the username@domainaccount format.
• When installing the Control Center repository, if the Control Center Console is not already installed on the same computer, you cannot use the setup program to add an AppManager repository. To resolve this problem, after installation completes, use the Control Center Console to add the repository.
• When performing an Evaluation Mode installation of AppManager on a case-sensitive SQL Server, you must specify the user account information in the setup program using the correct case. If you do not specify the correct case, the setup program does not raise an error and the Control Center repository is installed incorrectly.
• You cannot install the AppManager repository database on a computer where both SQL Server 2000 and SQL Server 2005 are installed. To resolve this problem, install the AppManager repository database on a SQL Server 2000 computer or a SQL Server 2005 computer.

Console Application Issues

• At this time, only Microsoft SQL Server can be monitored from the virtual server perspective.
• In the Operator Console and the Control Center Console, the same Inactive job status icon is used to indicate a computer is in scheduled maintenance and to indicate a clustered node is configured with a resource dependency.
• In the Control Center Console, if you change the status of event, the console automatically updates the status of the event. However, if you press F5 immediately after changing the status of an event, the console displays the status of the event based on the status information in Control Center repository. If the repository has not yet updated the event status, the console displays the old event status. To resolve this problem, press F5 until the event status in the console is correct.
• When using the Operator Web Console on Windows Vista, do not press F5 to refresh Microsoft Internet Explorer. Instead, click the Refresh button in Microsoft Internet Explorer to refresh the Operator Web Console. If you press F5, the Operator Web Console prompts you to install an ActiveX add-on for the Web Console Report Viewer.
• In the Operator Console, you cannot add a new computer to the AppManager repository from a snapshot view that is based on the Master view. You must use the Master view to add a new computer to the repository. Note that from a snapshot view, you can add resources that appear in the Master view by clicking TreeView > Add Discovered Resources.
• In the Control Center Console, you cannot configure a rule-based management group to select computers based on the NT_MachineFolder object. You can use another object to select a computer by operating system, such as NT > Windows Version.
• If the name of a Knowledge Script Group is longer than 35 characters, you cannot override the parameter values for policy-based jobs created with the Knowledge Script Group on an AppManager repository that is not the primary repository for Control Center.
• In the Developer Console, if you attempt to open a Knowledge Script (.QML) file after you have imported a Perl script, the Developer Console displays a "Failed to open document" message. To resolve this problem, close and then open the Developer Console, then open the Knowledge Script (.QML) file.
• In the Operator Web Console, on the Computers page, the same icon is displayed for a virtual machine and physical server.
• In the Control Center Console, if you delete a management group that is configured with a monitoring policy, the Cache Manager status will temporarily indicate an Error status. You can disregard the Error status of the Cache Manager.
• When you log into the Chart Console with a SQL user account that has not been granted access to the AppManager repository database, the Chart Console displays a data point value of ????. To resolve this problem, use the AppManager Security Manager console application to grant the user access.
• On Windows Vista, in the Administrator layout of the Control Center Console, the Rules view does not refresh automatically. To refresh the status information for deployment rules, press Ctrl+F7 then press F5.
• On Windows Vista, the Chart Console does not properly export a chart image to a file. This problem occurs when you export:
  • A chart to an image file.
  • A chart to an HTML report that includes the chart.
  These problems also occur when running the Chart Console from the Operator Web Console on Windows Vista.
• Viewing charts between consoles. When you log into the Chart Console or the Operator Web Console, always specify either the repository server name or IP address. You cannot view charts between consoles when the repository server is specified differently at logon. For example, if you create a chart in the Chart Console while logged in using the repository host name, you cannot view the chart from the Operator Web Console while logged in using the repository IP address.
• Operator Console limitations. There are certain operations that can only be performed in the Control Center Console. From the Operator Console, you cannot:
  • Remove a monitoring policy created in the Control Center Console. If you attempt to delete a Knowledge Script Group from a monitoring policy, and the Knowledge Script Group was added in the Control Center Console, the Knowledge Script Group is temporarily removed from the Monitoring Policy tab of the View Properties dialog box, however, the jobs continue to run and after a few minutes, the Knowledge Script Group reappears in the Monitoring Policy tab.
  • View or change the override value for a parameter in the Values tab of the Job Properties dialog box. To view and change override values for a job, you must use the Control Center Console.
  • Add or change custom properties. You must use the Control Center Console to manage custom property information.
• Control Center Console duplicate policy-based jobs. When implementing a monitoring policy on a management group, it is a good idea to limit the number of members in the management group. If you add more than one member to a management group, make sure you do not select a computer more than once. For example, if you add the NT view and a management group rule that selects computers based on discovered NT resources, duplicate policy-based jobs are created on computers that are selected by both members.
• Control Center Console does not display policy members from Operator Console. If you configure a monitoring policy in the Operator Console, the Knowledge Script Group members that were added in the Operator Console do not appear in the Control Center Console.
• Control Center Console limitations. There are certain operations that can only be performed in the Operator Console. From the Control Center Console, you cannot:
  • View audit information for jobs, events, and maintenance mode activity.
  • Add a computer that is not accessible from the Control Center Console computer.
  • Delete a discovered resource folder, such as SMTP Sites or a particular resource, such as Default SMTP Sites.
  • Set AppManager repository preferences.
  • View the development (checkin/checkout) history of a Knowledge Script.
  • Modify the properties of a parent job.
  • Add a child job to an existing parent.
  • View or configure a monitoring policy configured in the Operator Console.
  • View information about graph data streams.
• If the Control Center repository is installed on a Windows 2000 computer with Microsoft SQL Server 2005, when you create a Knowledge Script Group in the Control Center Console, an error message is incorrectly displayed. You can disregard the following message:

  (This message is created by command UpdateKSProperty)
  

• If you configure a Knowledge Script to collapse duplicate events or raise an event when the original event condition no longer exists, and the Knowledge Script is configured to run an action, the Action Knowledge Script only runs the first time an event is raised. If you acknowledge or close the original event and a new event is created, the Action tab of the Event Properties dialog box indicates the following problem:

  *** This can only be an MC Action
  

  To avoid this problem, do not configure a Knowledge Script that is configured to run an action to also collapse duplicate events or raise an event when the original event condition no longer exists.
• To run a group of ad hoc jobs in the Control Center Console, you must be logged as a user with db_owner permissions on the Control Center repository database.

Agent Issues on Windows

• AppManager 7.0.1 adds support for the AppManager agent on Windows Vista with the following limitations:
  • When you run the Discovery_NT Knowledge Script on a Windows Vista computer, the Product Type information is incorrectly displayed as Windows NT WorkstationProfessional. This is a known limitation.
  • The AppManager agent is not supported on the 64-bit version of Windows Vista.
  • The AppManager agent monitors the Windows Vista operating system only. AppManager 7.0.1 does not include application-monitoring support on Windows Vista.
  • The AppManager report agent is not supported on Windows Vista. Note that although you can configure the agent installation to enable the report agent, the report agent does not generate reports properly on Windows Vista and the following error is displayed:

    Microsoft VBScript runtime error [Line: 576] ActiveX component can't create object: 'NETIQOLE.APPMANAGER'

Knowledge Script Issues

• The IIS_Centralized_Binary_Logging Knowledge Script requires the Microsoft Log Parser to parse the IIS_Binary.ibl log file. To use this functionality, complete the following steps:
  1. Download the Microsoft Log Parser from the Microsoft web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=en
  2. Install the Microsoft Log Parser to the AppManager bin folder, by default: C:\Program Files\NetIQ\AppManager\bin
• When creating or modifying a Knowledge Script, do not use static legends. Dynamic legends work properly with NetIQ Analysis Center.
• ReportAC Knowledge Scripts are no longer applicable. The ReportAC Knowledge Scripts are not applicable with Analysis Center 2.0 (or later) and are not included with AppManager 7.0.
• Configuring General_WMICounter can cause the Operator Console to close unexpectedly. If you configure the WMI object's property to monitor parameter to select the root\CIMV2 class, do not select the:
  • Second, Minute, or Hour schema for the Win32_CurrentTime
  • QuotaVolume schema for the Win32_DiskQuota
  If you select one of these schemas, the Operator Console may close unexpectedly.
• The General_ASCIILog Knowledge Script can monitor more than one log file by specifying wildcards, but the list of files monitored does not change to monitor new files in the target directory that match the naming convention. Contact NetIQ Technical Support for information about monitoring more than one ASCII text file.
• To remotely install or change AppManager monitoring support on a 6.0.2 (or earlier) version of the AppManager Windows agent, run one of the following Knowledge Scripts on an AppManager 6.0.2 agent that is configured with the remote agent installation option:
  • AMAdmin_AddManagedObjectProxy
  • AMAdmin_AgentInstallProxy
  • AMAdmin_AgentUninstallProxy
  
  
  • AMAdmin_AgentUpdateProxy
  The following Knowledge Scripts are obsolete in AppManager version 7.0. You cannot use these Knowledge Scripts to install or change AppManager monitoring support on a 5.0.1 or 6.x version of the AppManager Windows agent:
  • AMAdmin_AddManagedobject
  • AMAdmin_AgentInstall
  • AMAdmin_AgentUninstall
  • AMAdmin_AgentUpdate
  • AMAdmin_MaintenanceInstall
• Do not use the Domino_RunAgent Knowledge Script. This Knowledge Script is not supported in AppManager 7.0.

Documentation Issues

• Some developer-related documentation is only available from NetIQ Extended Support. The AppManager Developer Guide, Managed Objects Reference Guide, and the NetIQ OLE Object Reference Guide are only available from the NetIQ Extended Support web site. To access this page, you must have a MyNetIQ account. Developer documentation for the AppManager reporting object is included on the installation kit in the \Documentation\Administration\Developers folder.
• Updated documentation is available from NetIQ Extended Support. Check NetIQ Extended Support web site for the latest AppManager documentation. To access this page, you must have a MyNetIQ account.

Legal Notice

NetIQ AppManager version 7.0 is covered by United States Patent No(s): 05829001, 05986653, 05999178, 06078324, 06397359, 06408335.

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

© 1995-2007 NetIQ Corporation, all rights reserved.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government’s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

Check Point, FireWall-1, VPN-1, Provider-1, and SiteManager-1 are trademarks or registered trademarks of Check Point Software Technologies Ltd.

ActiveAgent, ActiveAnalytics, ActiveAudit, ActiveReporting, ADcheck, AppAnalyzer, AppManager, the cube logo design, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, Exchange Administrator, File Security Administrator, IntelliPolicy, Knowing is Everything, Knowledge Scripts, Mission Critical Software for E-Business, MP3check, NetConnect, NetIQ, the NetIQ logo, NetIQ Change Administrator, NetIQ Change Guardian, NetIQ Compliance Suite, NetIQ Group Policy Administrator, NetIQ Group Policy Guardian, NetIQ Group Policy Suite, the NetIQ Partner Network design, NetIQ Patch Manager, NetIQ Risk and Compliance Center, NetIQ Secure Configuration Manager, NetIQ Security Administration Suite, NetIQ Security Analyzer, NetIQ Security Manager, NetIQ Vulnerability Manager, PSAudit, PSDetect, PSPasswordManager, PSSecure, Server Consolidator, VigilEnt, Vivinet, Work Smarter, and XMP are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies.