AppManager requires a Windows login account with Administrator privileges. The privileges can be for the local computer (required) or the Domain (optional). If your Windows login account does not have Administrator privileges, see your system administrator.
The AppManager repository requires approximately 50 MB of available disk space on the drive where you plan to install the AppManager repository program files.
The AppManager repository requires approximately 150 MB of available disk space on the drive where you plan to install the AppManager repository database.
-- At least 100 MB is required for the repository data device.
-- At least 50 MB is required for the repository log device.
Values for the data and log devices can be reduced for small departmental solutions or increased for large-scale organizations.
Disk space is checked on the drive where SQL Server is installed. If you plan to install the repository database on a different drive, you'll need to verify the disk space yourself.
SQL Server must be configured with the Named Pipes network protocol (you can have other protocols in addition to Named Pipes). If SQL Server isn't configured for any network protocol, then rerun SQL Server Setup before installing AppManager and at a minimum add the Named Pipes protocol.
The Pre-installation Check program checks the Microsoft SQL Server version. The AppManager repository must be installed on either:
- SQL Server 2000 with Service Pack 3 (or later).
The Results page displays the current SQL Server version, including any Service Packs. If Service Pack information is not displayed, SQL Server Service Packs are not installed. The SQL Server Catalog version is provided for informational purposes only.
Tip: You can download Service Packs for SQL Server from the Microsoft Web site at http://www.microsoft.com.
These SQL Server services must be installed and running:
-- For SQL 2000 (8.0) using default: MSSQLServer and SQLServerAgent. With instancename: MSSQL$instancename and SQLAgent$instance.
You can manually start these services, or let the pre-installation check program automatically start them. If these services are not running, other requirements might fail.
AppManager requires a valid password for the SQL Server login account. If this requirement fails, the remaining repository requirements will not be checked.
Version 3.0 SP 1 or greater of the Microsoft XML Parser (MSXML) is required for license manager. If you need to install MSXML, the setup program for MSXML Version 3.0 SP1 (msxml3sp1.exe) is included on the AppManager installation CD in the \appmanager\extras\utilities\msxml_setup folder. See the readme.txt in this folder additional instructions.
User running the setup must provide sysadmin level security previlege on the SQL Server before attempting QDB installation or upgrade. If using NT authentication (or integrated security) then the NT account or group must be in sysadmin Server Role. If using SQL authentication, then the SQL account must be in sysadmin Server Role.
The upgrade program deletes existing Knowledge Scripts and Knowledge Script Group members that are version 3.x. After the repository upgrade completes, you cannot check in Knowledge Scripts that are earlier than version 4.3.
Review the list of version 3.x Knowledge Scripts below and check out a backup copy of any Knowledge Script you want to keep. Note that for Knowledge Script Group members, the name of its Knowledge Script Group appears in front of the colon:
The upgrade program deletes existing Knowledge Scripts and Knowledge Script Group members that are version 4.0.x. After the repository upgrade completes, you cannot check in Knowledge Scripts that are earlier than version 4.3.
Review the list of version 4.0.x Knowledge Scripts below and check out a backup copy of any Knowledge Script you want to keep. Note that for Knowledge Script Group members, the name of its Knowledge Script Group appears in front of the colon:
Notes:
-- A copy of MDAC 2.6 is included on the AppManager CD-ROM in the \appmanager\extras\utilities\mdac_setup folder. See the readme.txt file in this folder for additional instructions.
The AppManager management server requires the use of port 9999. If this port is being used by another application, reconfigure the application to use another port.
(Optional) To use MAPI Mail recovery actions, Microsoft Exchange Client must be installed. In addition, you need to create an Exchange mail profile for AppManager to use. For information on installing Exchange Client and creating a mail profile, see your Exchange Administrator.
Note: The pre-installation check program is unable to verify this requirement. If you want to use MAPI Mail recovery actions, you need to verify this requirement yourself.
The NetIQ management server requires a valid Microsoft XML parser version 3.0 SP1 to be installed. If the preinstall check failed, please install msxml3sp1.exe from the CD.
The AppManager client resource monitor requires an Intel-based Pentium computer running one of these versions of Windows NT SP6a, Windows 2000, Windows XP, or Windows 2003:
-- Windows NT 4.0 Standard Server, Enterprise, Terminal Server or Workstation with NT SP6a (or later).
-- Windows 2000 Standard Server, Advanced Server, Datacenter Server, or Professional.
-- Windows XP Professional.
-- Windows 2003 Standard Server, Web Server, Enterprise Server or Datacenter Server.
The AppManager client resource monitor installer requires 30 MB of available disk space on the temp drive for temporary installation files. The installer identifies the temp drive by checking the environmental variable TEMP. If TEMP does not exist, the installer checks the environmental variable TMP. If TMP does not exist, the installer uses the system root directory specified in the registry by the value "SystemRoot" under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion.
The AppManager client resource monitor requires the use of port 9998. If this port is being used by another application, reconfigure the application to use another port.
Note: If using the AMADMIN_AgentInstall Knowledge Script, also open TCP port 9979.
(Optional) To use MAPI Mail recovery actions, Microsoft Exchange Client must be installed. In addition, you need to create a Windows domain account and an Exchange mailbox for AppManager to use. For information on installing Exchange Client and creating a mailbox, see your Exchange Administrator.
Note: The pre-installation check program is unable to verify this requirement. If you want to use MAPI Mail recovery actions, you need to verify this requirement yourself.
AppManager client resource monitor requires MDAC 2.0 or higher. Please install MDAC 2.0 on your system. For information on which version of MDAC to install and copies of the MDAC installation programs, see the \appmanager\extras\utilities\mdac_setup folder on the AppManager installation CD.
AppManager report agent requires MDAC 2.5 or higher. Please install MDAC 2.5 on your system, which is included on the AppManager CD-ROM in the \appmanager\extras\utilities\mdac_setup folder. See the readme.txt file in this folder for additional instructions.
The Windows Authentication feature requires 128-bit Encryption support, which is available with Windows 2000 Service Pack 2 (SP2) or Windows NT 4.0 with the High Encryption Pack.
This version of AppManager does not provide monitoring support for the following systems and applications:
Brocade Switches Check Point FireWall-1 HP TopTools for Servers IBM Netfinity Manager Microsoft Application Center 2000 Microsoft BizTalk Server 2000 Microsoft Commerce Server Microsoft Exchange Conferencing Server Microsoft Internet Security and Acceleration Server Microsoft Message Queue Server Microsoft Network Load Balancing Microsoft Proxy Server Microsoft Systems Management Server 1.2 Microsoft Systems Management Server Microsoft SNA Server Microsoft Transaction Server Network Appliance Filers Network Associates/McAfee NetShield Novell NetWare ResponseTime for Lotus Domino SAP R/3 Sybari Antigen for Microsoft Exchange Trend Micro ScanMail for Microsoft Exchange
If you want to continue monitoring these applications with AppManager, you should not upgrade the AppManager agent on this computer. If you upgrade the agent on this computer to AppManager 6.0, you will not be able to monitor any of the listed systems or applications. For information about obtaining monitoring support for these applications, visit the NetIQ AppManager Supported Products page at http://www.netiq.com/support/am/supportedproducts.asp.
The AppManager Active Directory module requires Microsoft Active Directory services to be installed. The Microsoft Active Directory Installation Wizard, dcpromo.exe, installs Active Directory services on a server, making the server a domain controller.
AppManager requires a valid password for the SQL Server login account. AppManager uses the login account to query system tables and devices and to create a netiq SQL Server login account.
SQL Server performace counters must be installed. To verify that the counters are installed:
1. Start SQL Performace Monitor.
2. Click the Add counter (+) button.
3. In the Object list, verify that the SQL Server counters are listed.
The counters must be installed at the time SQL Server is installed, not after. See your SQL Server administrator for instructions on installing counters.
The Microsoft WinMgmt service must be installed and running. This service has different display names in Windows NT 4.0 vs. Windows 2000, Windows XP Professional and Windows 2003.
-- For Windows NT: Windows Management.
-- For Windows 2000, Windows XP Professional and Windows 2003: Windows Management Instrumentation and Windows Management Instrumentation Driver Extensions.
Microsoft ODBC Driver for SQL Server must be installed on the client machine in order to use ODBC. Microsoft ODBC Driver for SQL Server is usually installed with MDAC.
The AppManager console requires one of these versions of Windows:
-- Windows 2000 Standard Server, Advanced Server, Datacenter Server, or Professional with SP4 (or later) and MMC 2.0.
-- Windows 2003 Standard Server, Web Server, Enterprise Server, or Datacenter Server.
-- Windows XP Professional.
AppManager console requires at least 70 MB of available disk space.
Depending on the number of managed clients you are monitoring, events you expect to generate, and jobs you expect to run in data collection mode, you may need to allow additional disk space for the local cache folder and paging files.
For SQL 2000, AppManager Console requires MDAC 2.6 or 2.7 (MDAC 2.7 allowed only if installing on Windows 2000 and connecting to a repository on Windows 2000).
The AppManager UI requires a valid Microsoft XML parser version 3.0 SP1 or greater to be installed. If the preinstall check failed, please install msxml3sp1.exe from the CD.