- Notes, cautions, and warnings
- Introduction
- Preinstallation Setup
- Prerequisite Checker
- Installation Requirements
- Configuring SNMP Agents
- Secure Port Server And Security Setup
- Remote Enablement Requirements
- Installing Managed System Software On Microsoft Windows Operating Systems
- Deployment Scenarios For Server Administrator
- Installer Location
- Installing Server Administrator
- System Recovery On Failed Installation
- Upgrading Managed System Software
- Uninstalling Managed System Software
- Deployment Scenarios For Server Administrator
- Installing Managed System Software On Microsoft Windows Server and Microsoft Hyper-V Server
- Using Microsoft Active Directory
- Active Directory Schema Extensions
- Extending The Active Directory Schema
- Frequently Asked Questions
Dell EMC OpenManage Installation Guide — Microsoft Windows Version 9.3.1
Prerequisite Checker
The setup.exe (available at srvadmin\windows) starts the prerequisite checker program. The prerequisite checker program examines the prerequisites for software components without launching the actual installation. This program displays a status window that provides information about the system’s hardware and software that may affect the installation and operation of software features.
NOTE: : To use supporting agents for the Simple Network Management Protocol (SNMP), install the operating system support for the SNMP standard before or after you install Server Administrator. For more information about installing SNMP, see the installation instructions for the operating system you are running on the system.
Run the prerequisite checker silently by running runprereqchecks.exe /s from the srvadmin\windows\PreReqChecker directory on the Systems Management Tools and Documentation software. After running the prerequisite checker, an HTML file (omprereq.htm) is created in the %Temp% directory. This file contains the results of the prerequisite check. The Temp directory is at X:\Documents and Settings\username\Local Settings\Temp. To find %TEMP%, go to a command-line prompt and type echo %TEMP%.
The results are written under the HKEY_LOCAL_MACHINE\Software\Dell Computer Corporation\OpenManage \PreReqChecks\MN\ key for a managed system:
While running the prerequisite checker silently, the return code from runprereqchecks.exe is the number associated with the highest severity condition for all the software products. The return code numbers are the same as those used in the registry. The following table details the return codes.
| Return Code | Description |
|---|---|
| 0 | No condition, or conditions, is associated with the software. |
| 1 | An informational condition, or conditions, is associated with the software. It does not prevent a software product from being installed. |
| 2 | A warning condition, or conditions, is associated with the software. It is recommended that you resolve the conditions causing the warning before proceeding with the installation of the software. To continue, select and install the software using the custom installation. |
| 3 | An error condition, or conditions, is associated with the software. Resolve the conditions causing the error before proceeding with the installation of the software. If you do not resolve the issues, the software is not installed. |
| —1 | A Microsoft Windows Script Host (WSH) error. The prerequisite checker does not run. |
| —2 | The operating system is not supported. The prerequisite checker does not run. |
| —3 | The user does not have Administrator privileges. The prerequisite checker does not run. |
| —4 | Not an implemented return code. |
| —5 | The prerequisite checker does not run. The user failed to change the working directory to %TEMP%. |
| —6 | The destination directory does not exist. The prerequisite checker does not run. |
| —7 | An internal error has occurred. The prerequisite checker does not run. |
| —8 | The software is already running. The prerequisite checker does not run. |
| —9 | The WSH is corrupted, is a wrong version, or is not installed. The prerequisite checker does not run. |
| —10 | An error has occurred with the scripting environment. The prerequisite checker does not run. |
NOTE: : A negative return code (-1 through -10) indicates a failure in running the prerequisite checker tool. Probable causes for negative return codes include software policy restrictions, script restrictions, lack of folder permissions, and size constraints.
NOTE: : If you encounter a return code of 2 or 3, it is recommended that you inspect the omprereq.htm file in the windows temporary folder %TEMP%. To find %TEMP%, run echo %TEMP%.
Common causes for a return value of 2 from the prerequisite checker:
- One of the storage controllers or drivers has outdated firmware or driver. See firmwaredriverversions_<lang>.html (where < lang > stands for language) or firmwaredriverversions.txt found in the %TEMP% folder. To find %TEMP%, run echo %TEMP%.
- RAC component software version 4 is not selected for a default install unless the device is detected on the system. The prerequisite checker generates a warning message in this case.
- Intel, Broadcom, and QLogic agents are selected for a default install only if the corresponding devices are detected on the system. If the corresponding devices are not found, prerequisite checker generates a warning message.
- Domain Name System (DNS) or Windows Internet Name Service (WINS) server running on the system can cause a warning condition for RAC software. See the relevant section in Server Administrator readme for more information.
- Do not install managed system and management station RAC components on the same system. Install only the managed system RAC components, as they offer the required functionality.
Common causes for a return code of 3 (failure) from the prerequisite checker:
- You are not logged in as a built-in Administrator, Domain Administrator, or user who is a part of Domain Admins and Domain Users group.
- The MSI package is corrupt or one of the required XML files is corrupt.
- Error during copying from a DVD or network access problems while copying from a network share.
- Prerequisite checker detects that another MSI package installation is running or that a reboot is pending: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\Windows\CurrentVersion\Installer\InProgress indicates that another MSI package installation is in progress. HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\PendingFileRenameOperations indicates that a reboot is pending.
- Running the 64-bit version of Windows Server 2008 Core, since certain components are disabled from being installed.
Ensure that any error or warning is corrected before you proceed to install systems management software components.
Related Link
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\