Dell OpenManage™ Version 5.1 Installation and Security User’s Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2006 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Systems Management Software Overview . Dell OpenManage Systems Management Software Kit Contents . . . . . . . . . . . . What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 . . . . . . . 12 . . . . . . . 12 . . . . . . . 14 . . . . . . . 15 . . .
3 Setup and Administration . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 32 . . . . . . . . . . . . . . . . . . . . . . . . 34 Installation Requirements Supported Operating Systems System Requirements . . . . .
Installing Management Station Software . Overview . . . . . . . . . . . . . 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Installation Requirements System Requirements . . . . . . . . . . . . . . . . . Management Station Requirements . . . . . . . . . IT Assistant Database Requirements . . . . . . . . . Enabling CIM Discovery and Security in IT Assistant Installing SNMP . . . . . . . . . . . . . . . . . . .
Installing Managed System Software on Microsoft® Windows® Operating Systems Overview . . . . . . . . . . . . 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Dell PowerEdge Installation and Server Management CD . Unattended and Scripted Silent Installation . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . 73 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Kernel Support (DKS) . . . . . . . . . . . . OpenIPMI Device Driver . . . . . . . . . . . . . . . Installing and Upgrading Managed System Software Performing an Unattended Installation of the Managed System Software . . . . . . . . . . . . . . Upgrading From Previous Versions . . . . . . . . . . Uninstalling Managed System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
Introduction Overview This guide contains information to help you install Dell OpenManage™ software on management stations and their managed systems. A managed system is a system that has supported instrumentation or agents installed that allow the system to be discovered and polled for status. A management station is used to remotely manage one or more managed systems from a central location. See Figure 1-1 for a view of a management station and its managed systems.
A management station can be used to remotely configure and maintain one or more managed systems from a central location. Dell OpenManage IT Assistant and the other management station applications enable you to manage from one to thousands of managed systems. For instance, a management station can be used to deploy images of physical media to virtual media at many managed systems.
Dell OpenManage Systems Management Software Kit Contents The Dell OpenManage Systems Management Software Kit includes, but is not limited to, the following components: • Dell OpenManage Software Quick Installation Guide — Provides an overview of applications that you can install on your management station (console) and on your managed systems.
Dell OpenManage Systems Management Software Components Deployment Software (Dell PowerEdge Installation and Server Management CD) For managed systems, Dell OpenManage Server Assistant provides streamlined operating system installation, reducing the time required for the installation of Windows, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server operating systems by guiding you through an easy-to-follow, step-by-step process.
Dell Remote Access Controller Management Station The Dell Remote Access Controller (DRAC) console is management station software designed to provide remote management capabilities for PowerEdge systems. You can remotely connect to RAC hardware using the DRAC Tools software.
Active Directory Snap-in Utility The Microsoft Active Directory Snap-in utility provides an extension snap-in to the Microsoft Active Directory, which allows you to manage Dell-specific Active Directory objects. You can use this option when the Dell-specific schema classes have been added to the Active Directory schema.
Storage Management Service The Storage Management Service provides enhanced features for managing a system's locally-attached RAID and non-RAID disk storage.
Other Documents You Might Need Besides this guide, you can find the following guides either on the Dell Support website at support.dell.com or on the Documentation CD: 16 • The Dell OpenManage Software Quick Installation Guide provides an overview of applications that you can install on your management station, or console, and on your managed systems. It also has procedures for installing your console and managed system applications.
• The Dell Remote Access Controller Installation and Setup Guide provides complete information about installing and configuring a DRAC III, DRAC III/XT, or ERA/O controller, configuring an ERA controller, and using a RAC to remotely access an inoperable system. • The Dell Remote Access Controller Racadm User's Guide provides information about using the racadm command line utility to manage DRAC III, DRAC III/XT, ERA, and ERA/O controllers.
Introduction
Dell OpenManage™ Security Security Features The Dell OpenManage systems management software components provide the following security features: • Authentication for users through hardware-stored user IDs and passwords, or by using the optional Microsoft® Active Directory®. • Role-based authority that allows specific privileges to be configured for each user. • User ID and password configuration through the Web-based interface or the command line interface (CLI), in most cases.
Table 2-1. Port # Dell OpenManage UDP/TCP Ports Default Locations Protocol Port Type Version Max. Encryption Direction Usage Level Configurable Dell OpenManage Baseboard Management Controller - PowerEdge™ x8xx systems 623 RMCP UDP PowerEdg None e x800 systems only In/Out IPMI access via LAN No Dell OpenManage Baseboard Management Utility 623 Telnet TCP 1.x None In/Out Accepts incoming Telnet connections Yes 623 RMCP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Max. Encryption Direction Usage Level Configurable 162 SNMP UDP 6.x None Out Event transmission via No SNMP 1024-65535 DCOM (Dynamically assigned) TCP/UDP 6.x, 7.x None In/Out Monitoring and configuration via WMI > 32780 DMI (Dynamically assigned) TCP/UDP 6.x None In/Out Monitoring and Varies from configuration via DMI one system to another.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Max. Encryption Direction Usage Level Configurable 135 RPC TCP 6.x, 7.x None In/Out Event reception via CIM from Server Administrator — For systems supporting Windows® No 135 RPC TCP/UDP 6.x None In/Out DMI discovery of remote systems No 135 RPC TCP/UDP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol 443 Port Type Version Max. Encryption Direction Usage Level Configurable Proprietary TCP 8.0 None In/Out EMC Storage discovery and inventory No 623 RMCP UDP 8.0 None In/Out IPMI access via LAN No 6389 Proprietary TCP 8.0 None In/Out Enables No communication between a host system (through NaviCLI/NaviSecCLI or Navisphere Host Agent) and a Navisphere Array Agent on a Storage system.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Max. Encryption Direction Usage Level 139 NetBIOS TCP 2.0 None In/Out Remote Server No Administrator Command Line (for IT Assistant). Remote Software Update (for Windows). 161 SNMP UDP 1.x, 2.0 None In/Out SNMP query management No 162 SNMP UDP 1.x, 2.0 None Out SNMP trap event No 445 NetBIOS TCP 2.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Max. Encryption Direction Usage Level Configurable 80 HTTP TCP 1.0 None In/Out Web GUI redirected to HTTPS No 162 SNMP UDP 1.0 None Out SNMP trap event No 443 HTTPS TCP 1.0 128 bit SSL In/Out Web management GUI No 443 HTTPS TCP 3.2 128 bit SSL In/Out Remote racadm CLI utility No 5869 Proprietary TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Max. Encryption Direction Usage Level Configurable 162 SNMP UDP 1.0 None Out SNMP trap event No 443 HTTPS TCP 1.0 128 bit SSL In/Out Web management GUI and remote racadm CLI utility Yes 636 LDAPS TCP 1.0 128 bit SSL In/Out Optional Active No Directory Services (ADS) authentication 3269 LDAPS TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Type Version Max. Encryption Direction Usage Level Configurable 389 LDAP TCP 1.0 None In/Out Optional Active No Directory Services (ADS) authentication 443 HTTPS TCP 1.0 128 bit SSL In/Out Web management GUI and remote racadm CLI utility 636 LDAPS TCP 1.0 128 bit SSL In/Out Optional Active No Directory Services (ADS) authentication 3269 LDAPS TCP 1.
User Privileges Server Administrator grants different access rights based on the user's assigned group privileges. The three user levels are User, Power User, and Administrator. Users can view most information. Power Users can set warning threshold values, run diagnostic tests, and configure which alert actions are to be taken when a warning or failure event occurs.
Table 2-4 defines the user privilege level abbreviations used in Table 2-3. Table 2-4. Legend for Server Administrator User Privilege Levels U User P Power User A Administrator Authentication The Server Administrator authentication scheme ensures that the correct access types are assigned to the correct user privileges. Additionally, when you invoke the CLI, the Server Administrator authentication scheme validates the context within which the current process is running.
Dell OpenManage™ Security
Setup and Administration Before You Begin • Read the applicable instructions in this chapter. • Read the installation requirements to ensure that your system meets or exceeds the minimum requirements. • Read the Dell OpenManage™ Server Administrator Compatibility Guide.
• Windows Server 2003 SP1 (Web Edition) • Windows SBS 2003 SP1 (except IT Assistant) • Windows XP SP2 • Windows Storage Server 2003 R2 — Includes Express, Standard, Workgroup, and Enterprise editions • Red Hat Enterprise Linux AS, ES, and WS (version 3) x86, Update 6 NOTE: Support for updated kernels released by Red Hat and for later versions of Red Hat Enterprise Linux may require the use of Dynamic Kernel Support (see "Dynamic Kernel Support (DKS)" for a description of this feature).
• A mouse, keyboard, and monitor to manage a system locally. The monitor requires a minimum screen resolution of 800 x 600. The recommended screen resolution setting is 1024 x 768. • The Server Administrator Remote Access Service requires that a remote access controller (RAC) be installed on the system to be managed.
Table 3-1 shows the availability of the systems management standards for each supported operating system. Table 3-1. Availability of Systems Management Protocol by Operating Systems Operating System SNMP CIM/WMI Supported Windows operating systems. Available from the operating system installation media. Always installed. Supported Red Hat Enterprise Linux operating systems. You must install the SNMP package provided with the operating system. Unavailable.
Viewing Localized Versions of the Web-Based Interface When using Internet Explorer or Netscape Navigator on systems running Windows, to view localized versions of the Web-based interface, do the following: 1 Open the Windows Control Panel and double-click the Regional Options icon. 2 Select the desired locale from the Your locale (location) drop-down menu.
5 In the console tree, under Local Users and Groups, click Groups. 6 Click the group to which you want to add the new user: Users, Power Users, or Administrators. 7 Click Action, and then click Properties. 8 Click Add. 9 Type the user name that you are adding and click Check Names to validate. 10 Click OK. New users can log into Dell OpenManage software with the user privileges for their assigned group.
3 Type the appropriate user name information in the dialog box, and then click Next. NOTICE: You must assign a password to every user account that can access Dell OpenManage software to protect access to your critical system components. Additionally, users who do not have an assigned password cannot log into Dell OpenManage software on a system running Windows Server 2003 due to operating system constraints. 4 Click Next, and then click Finish.
Creating Users NOTE: For questions about creating users and assigning user group privileges, or for more detailed instructions, see your operating system documentation. Creating Users With User Privileges 1 Run the following command from the command line: useradd -d home-directory -g group username where group is not root. NOTE: If group does not exist, you must create it by using the groupadd command. 2 Type passwd username and press . 3 When prompted, enter a password for the new user.
Configuring the SNMP Agent Dell OpenManage software supports the SNMP systems management standard on all supported operating systems. The SNMP support may or may not be installed depending on your operating system and how the operating system was installed. An installed supported systems management protocol standard, such as SNMP, is required before installing Dell OpenManage software. See "Installation Requirements" for more information.
Enabling SNMP Access By Remote Hosts on Windows Server 2003 Windows Server 2003, by default, does not accept SNMP packets from remote hosts. For systems running Windows Server 2003, you must configure the SNMP service to accept SNMP packets from remote hosts if you plan to manage the system by using SNMP management applications from remote hosts. To enable remote shutdown of a system from IT Assistant, SNMP Set operations must be enabled.
5 Click the Security tab to add or edit a community name. a To add a community name, click Add under the Accepted Community Names list. The SNMP Service Configuration window appears. b Type the community name of a system that is able to manage your system (the default is public) in the Community Name text box and click Add. The SNMP Service Properties window appears. c To change a community name, select a community name in the Accepted Community Names list and click Edit.
Configuring Your System to Send SNMP Traps to a Management Station Dell OpenManage software generates SNMP traps in response to changes in the status of sensors and other monitored parameters. You must configure one or more trap destinations on the Dell OpenManage software system for SNMP traps to be sent to a management station. 1 If your system is running Windows Server 2003, click the Start button, right-click My Computer, and point to Manage.
SNMP Agent Access Control Configuration The management information base (MIB) branch implemented by Server Administrator is identified by the 1.3.6.1.4.1.674 OID. Management applications must have access to this branch of the MIB tree to manage systems running Server Administrator. For Red Hat Enterprise Linux operating systems, the default SNMP agent configuration gives read-only access for the "public" community only to the MIB-II "system" branch (identified by the 1.3.6.1.2.1.1 OID) of the MIB tree.
To change the SNMP community name used for retrieving management information from a system running Server Administrator, edit the SNMP agent configuration file, /etc/snmp/snmpd.conf, and perform the following steps: 1 Find the line that reads: com2sec publicsec default public or com2sec notConfigUser default public 2 Edit this line, replacing public with the new SNMP community name.
Configuring Your System to Send Traps to a Management Station Server Administrator generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Server Administrator for SNMP traps to be sent to a management station. To configure your system running Server Administrator to send traps to a management station, edit the /etc/snmp/snmpd.
3 Select the Security Level by tabbing to it and pressing the spacebar. The selected Security Level is indicated by an asterisk. NOTE: Press for more information about the firewall security levels. The default SNMP port number is 161. If you are using the X Windows GUI, pressing might not provide information about firewall security levels on newer versions of the Red Hat Enterprise Linux operating system. a To disable the firewall, select No firewall or Disabled and go to step 7.
Sever Administrator SNMP Install Actions Server Administrator SNMP communicates with the SNMP agent using the SNMP Multiplexing (SMUX) protocol. When Server Administrator SNMP connects to the SNMP agent, it sends an object identifier to the SNMP agent to identify itself as a SMUX peer. Because that object identifier must be configured with the SNMP agent, Server Administrator adds the following line to the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.
Changing the SNMP Community Name Configuring the SNMP community name determines which systems are able to manage your system through SNMP. The SNMP community name used by management applications must match an SNMP community name configured on the Server Administrator system, so the management applications can retrieve management information from Server Administrator.
Configuring Your System to Send Traps to a Management Station Server Administrator generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Server Administrator for SNMP traps to be sent to a management station. To configure your system running Server Administrator to send traps to a management station, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.
Perform the following steps to set up your secure port server preferences: 1 Click Preferences on the global navigation bar. The Preferences home page appears. 2 Click General Settings, and the Web Server tab. 3 In the Server Preferences window, set options as necessary. • The Session Timeout feature can set a limit on the amount of time that a session can remain active. Select the Enable radio button to allow a time-out if there is no user interaction for a specified number of minutes.
X.509 Certificate Management Web certificates are necessary to ensure the identity of a remote system and ensure that information exchanged with the remote system cannot be viewed or changed by others. To ensure system security, it is strongly recommended that you either generate a new X.509 certificate, reuse an existing X.509 certificate, or import a root certificate or certificate chain from a Certification Authority (CA).
Setup and Administration
Using Server Assistant to Install an Operating System Overview Dell OpenManage™ Server Assistant provides a streamlined and time-saving installation procedure by guiding you through an easy-to-follow, step-by-step process for installing the Microsoft® Windows®, Red Hat® Enterprise Linux, and SUSE® Linux Enterprise Server operating systems. Server Assistant is used to install operating systems for systems being installed as managed systems.
• Windows SBS 2003 SP1 (except IT Assistant) • Windows Server 2003 x64 R2 (includes Standard and Enterprise Editions) • Windows Storage Server 2003 R2 (includes Express, Standard, Workgroup, and Enterprise Editions) • SUSE Linux Enterprise Server (version 9) SP3 for Intel EM64T • SUSE Linux Enterprise Server (version 10) Gold, for Intel EM64T Installing Your Operating System Perform the following steps to determine if an operating system has been installed on your system: 1 Ensure that the keyboar
Installing Management Station Software Overview The Dell™ Systems Management Consoles CD provides a setup program to install, upgrade, and uninstall Dell OpenManage™ Management Station software on your system. Using the setup program on the Dell Systems Management Consoles CD, you can install and upgrade Management Station software on systems running Microsoft® Windows® operating systems.
• Windows SBS 2003 SP1 (except IT Assistant) • Windows Server 2003 Standard and Enterprise x64 R2 (except IT Assistant) • Windows Storage Server 2003 R2 (includes Express, Standard, Workgroup, and Enterprise editions) • Windows XP SP2 • SUSE Linux Enterprise Server (version 9), SP3, (BMC management utility and RAC Management Station) • SUSE Linux Enterprise Server (version 10) Gold for Intel EM64T NOTE: The Dell OpenManage 5.
Installing SNMP The SNMP service must be installed and running on the IT Assistant system. SNMP (or CIM) must also be installed on the systems that you want to discover and manage. If you attempt to install the IT Assistant on a system without SNMP, the installation program stops and prompts you to install SNMP. In addition, if you stop the SNMP service, the IT Assistant services also stop.
Installing and Upgrading Management Station Software This section explains how to install and upgrade Management Station software. The installation options are as follows: • Use the setup program on the Dell Systems Management Consoles CD to install or upgrade IT Assistant and other Management Station software. • Use the unattended installation method through the msiexec.exe Windows Installer Engine (see Table 5-1) to install IT Assistant and other Management Station software on multiple systems.
Custom Installation The custom installation path enables you to choose specific software features to install. NOTE: Management Station and managed system services can be installed in the same or in different directories. You can select the directory for installation. Installing Management Station 1 Log on with Administrator privileges to the system where you want to install the Management Station software features. 2 Close any open application programs.
8 Click Next to accept the selected software features for installation. The IT Assistant Custom Settings dialog box opens. NOTE: IT Assistant requires a default instance of a database to be installed on the system. IT Assistant cannot use a named instance of database. NOTE: Microsoft SQL Server 2005 Express requires Microsoft Data Access components 2.8 (MDAC 2.8) and .NET 2.0 Runtime to be installed. The prerequisite checker utility will prompt you to install MDAC 2.8, If MDAC 2.
Custom Upgrade 1 Insert the Dell Systems Management Consoles CD into your system's CD drive. If the installer does not automatically start, navigate to the windows folder on the CD and double-click the setup.exe file. The Dell OpenManage Management Station Prerequisite Status screen opens and runs the prerequisite checks for the Management Station. Prerequisite Status displays any relevant informational, warning, or error messages.
8 Click Install to install the selected software features. The Installing Dell OpenManage Management Station screen opens. Messages provide the status and progress of the software features being installed. When the selected features are installed, the Install Wizard Completed dialog box opens. 9 Click Finish to leave the Management Station installation. Custom Repair 1 Click the Start button, point to Settings→ Control Panel. 2 Double-click Add/Remove Programs.
When upgrading from Dell OpenManage software version 4.3 to version 5.x, an error will roll back the system to its previous state. NOTE: Installations, uninstallations, and upgrades canceled by the administrator during installer cleanup or after the installation transaction is completed will not be rolled back.
Mapping a Drive to Act as the Typical Unattended Installation Package To map a drive to act as the Typical unattended installation package, do the following: 1 Share an image of the Dell Systems Management Consoles CD with each remote system on which you want to install Management Station. You can accomplish this task by directly sharing the CD or by copying the entire CD to a drive and sharing the copy. 2 Create a script that maps a drive from the remote systems to the shared drive described in step 1.
Distributing Custom Unattended Installation Packages NOTE: The MgmtSt.msi installation package for Management Station used in the Custom Setup unattended installation as described in the previous section is located in the \windows\ManagementStation directory. 1 Configure your ISV distribution software to execute the batch script once your installation package has been distributed. 2 Use your ISV distribution software to distribute the custom unattended installation package to the remote systems.
Table 5-1. Command Line Settings for MSI Installer (continued) Setting Result /f[p|o|e|d|c|a|u|m|s|v] Repairs a product. /fp – This option reinstalls a product only if a file is missing. /fo – This option reinstalls a product if a file is missing or if an older version of a file is installed. /fe – This option reinstalls a product if a file is missing or an equal or older version of a file is installed.
Uninstall Management Station Software Using the Dell Systems Management Consoles CD To uninstall the Management Station software using the Dell Systems Management Consoles CD, do the following: 1 Insert the Dell Systems Management Consoles CD into your system's CD drive. If the CD does not automatically start the setup program, go to your system's desktop, double-click My Computer, double-click the CD drive icon, double-click the windows folder and double-click the setup.exe file.
Performing an Unattended Uninstallation of Management Station Software The Dell Systems Management Consoles CD features a procedure for the unattended uninstallation of the Management Station software. Unattended uninstallation enables you to uninstall Management Station software simultaneously from multiple systems. The unattended uninstallation package is distributed to the remote systems using a software distribution tool from an ISV.
Table 5-2. Feature IDs for the Management Station Feature ID Description ADS Active Directory Snap-in Utility BMU Baseboard Management Controller Management Utility ITA IT Assistant RACMS DRAC Tools NOTE: You have to type the ADDLOCAL, REINSTALL, and REMOVE CLI parameters in upper case as they are case-sensitive. You can include the ADDLOCAL customization parameter on the command line, and assign the feature ID (or IDs) of the software feature that you would like to install.
This command runs the installation for Management Station and simultaneously installs Active Directory Snap-in Utility, reinstalls IT Assistant, and uninstalls the Baseboard Management Controller. This execution will be in an unattended and verbose mode. NOTE: A Dell OpenManage Globally Unique Identifier (GUID) is 128 bits long. The product GUID uniquely identifies the application. In this case the product GUID for Dell OpenManage Management Station is {DA60872C-9147-4A6E9AEF-95BAB5EF3A3B}.
Installing, Upgrading, and Uninstalling Management Station Software on Systems Running Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server Operating Systems Installing Management Station Software Only the BMC and the RAC features of the Management Station suite of software can be used on a management station running Red Hat Enterprise Linux and SUSE Linux Enterprise Server.
To upgrade the DRAC Tools feature, perform the following steps: 1 Log on as root to the system where you want to upgrade the Management Station features. 2 If necessary, mount the CD to a desired location using the mount command or a similar command. 3 Navigate to the /linux/rac directory and upgrade the RAC software using the rpm -Uvh *.rpm command.
Installing Managed System Software on Microsoft® Windows® Operating Systems Overview You can install managed system software using several methods. The Dell™ PowerEdge™ Installation and Server Management CD provides a setup program to install, upgrade, and uninstall managed system software features on your managed systems. You can install the software on multiple systems through an unattended installation across a network.
Before You Begin • Read the installation requirements section below to ensure that your system meets or exceeds the minimum requirements. • Read the Dell OpenManage Server Administrator Compatibility Guide. This guide contains compatibility information about Server Administrator installation and operation on various hardware platforms running supported Windows, Red Hat® Enterprise Linux, and SUSE® Linux Enterprise Server operating systems. • Read the installation readme_ins.
System Requirements Server Administrator must be installed on each managed system. You can then manage each system running Server Administrator locally or remotely through a supported Web browser. The setup.exe utility calls the Prerequisite Checker on the CD to determine if the system requirements have been met. (For more information see the section titled "Prerequisite Checker.
Supported Systems Management Protocol Standards A supported systems management protocol standard must be installed on the managed system before installing Server Administrator. On supported Windows operating systems, Server Administrator supports the Common Information Model/Windows Management Instrumentation (CIM/WMI) and Simple Network Management Protocol (SNMP). CIM and WMI are always installed, and SNMP is available from the operating system installation media.
Digital Certificates All Server Administrator packages for Microsoft are digitally signed with a Dell certificate that helps guarantee the integrity of the installation packages. If these packages are repackaged, edited, or manipulated in other ways, the digital signature will be invalidated. This manipulation results in an unsupported installation package and the Prerequisite Checker will not allow you to install the software.
Use the "Custom" installation setup type later during installation to select this feature if you have an Intel(R) NIC installed. An error message describes a condition of which you should be aware that prevents the software feature from being installed. You must resolve the condition causing the error before proceeding with the installation of the software feature. If you do not resolve the issue, the software feature will not be installed.
Custom Installation The sections that follow show how to install and upgrade Server Administrator and other managed system software using the Custom Setup option. NOTE: Management station and managed system services can be installed in the same or in different directories. You can select the directory for installation. 1 Log on with Administrator privileges to the system where you want to install the system management software features.
8 Click Next to accept the selected software features for installation. The Ready to Install the Program dialog box appears. NOTE: You can cancel the installation process by clicking Cancel. The installation rolls back the changes that you made. If you click Cancel after a certain point in the installation process, the installation may not roll back properly, leaving the system with an incomplete installation. See "System Recovery on Failed Installation.
During the upgrade, you cannot add to the list of managed system software features to install because all features appropriate for your system are pre-selected. NOTICE: Dell OpenManage Array Manager is no longer supported. If you are upgrading a system (installed with Dell OpenManage version 4.3 or later) with Array Manager installed, Array Manager will be removed during the upgrade process. You can use Storage Management Service instead. NOTE: All user settings are preserved during upgrades.
Upgrade Using the Windows Installer Patch File You can upgrade your Managed System software using the Windows Installer Patch (.MSP) file. The MSP file is available on the Dell Support website at support.dell.com. To apply the MSP file either double-click on the MSP file or enter the following command in your command-prompt window: Msiexec.exe /p filename.msp NOTE: You can use other msiexec parameters like "/q" for silent upgrades. Custom Modify 1 Click the Start button, point to Settings→ Control Panel.
Custom Repair 1 Click the Start button, point to Settings→ Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell Server Administrator and click Change. The Welcome to the Install Wizard for Dell OpenManage Server Administrator dialog box opens. 4 Click Next. The Program Maintenance dialog box opens. 5 Select the Repair option and click Next. The Ready to Repair the Program dialog box opens. 6 Click Install to install the selected software features.
An installation cannot be rolled back once it has finished; transacted installation is only intended as a safety net that protects the system during an installation session. If you want to remove an installed application, for instance, you should simply uninstall that application. NOTE: Driver installation and removal is not executed as part of the installation transaction and therefore cannot be rolled back if a fatal error occurs during execution.
Once activated, you can find the log files that are generated in your %TEMP% directory. Some log files generated in this directory are: • Managed System Installation • • SysMgmt.log Management Station Installation • MgmtSt.log These particular log files are created by default if the Prerequisite Checker user interface (UI) is running. Upgrading the MSI Engine Dell OpenManage software allows you to upgrade the MSI engine while doing interactive installs.
Creating and Distributing the Typical Unattended Installation Package The Typical Setup unattended installation option uses the Dell PowerEdge Installation and Server Management CD as the unattended installation package. The msiexec.exe /i SysMgmt.msi /qb program accesses the Dell PowerEdge Installation and Server Management CD to accept the software license agreement and install all required Server Administrator features on selected remote systems. The msiexec.exe /i SysMgmt.
Creating and Distributing Custom Unattended Installation Packages To create a custom unattended installation package, perform the following steps: 1 Copy the windows directory from the CD onto the system hard drive. 2 Create a batch script that will execute the installation using the Windows Installer Engine (msiexec.exe). NOTE: For Customized Unattended Installation, each required feature must be included as a Command Line Interface (CLI) parameter for it to be installed. An example is msiexec.
Optional Command Line Settings Table 6-1 shows the optional settings available for the msiexec.exe MSI installer. Type the optional settings on the command line after msiexec.exe with a space between each setting. NOTE: See support.microsoft.com for full details about all the command line switches for the Windows Installer Tool. Table 6-1. Command Line Settings for MSI Installer Setting Result /i This command installs or configures a product. /i SysMgmt.
Table 6-1. Command Line Settings for MSI Installer (continued) Setting Result /f[p|o|e|d|c|a|u|m|s|v This command repairs a product. ] /fp – This option reinstalls a product only if a file is missing. /fo – This option reinstalls a product if a file is missing or if an older version of a file is installed. /fe – This option reinstalls a product if a file is missing or an equal or older version of a file is installed.
Table 6-2. Software Feature IDs Feature ID Description BRCM Broadcom NIC Agent INTEL Intel NIC Agent IWS Server Administrator Web Server OMSM Storage Management RAC3 Remote Access Controller (DRAC III) RAC4 Remote Access Controller (DRAC 4) RAC5 Remote Access Controller (DRAC 5) SA Server Administrator You can include the ADDLOCAL customization parameter on the command line, and assign the feature ID (or IDs) of the software feature that you would like to install. An example is msiexec.
MSI Return Code An application event log entry is recorded in the SysMgmt.log file. Table 6-3 shows some of the error codes returned by the msiexec.exe Windows Installer Engine. Table 6-3. Windows Installer Return Codes Error Code Value Description ERROR_SUCCESS 0 The action completed successfully. ERROR_INVALID_PARAMETER 87 One of the parameters was invalid. ERROR_INSTALL_USEREXIT 1602 The user canceled the installation.
4 Select the Remove option and click Next. The Remove the Program dialog box opens. 5 Click Remove. The Uninstalling Dell OpenManage Server Administrator screen opens. Messages provide the status and progress of the software features being uninstalled. When the selected features are uninstalled, the Install Wizard Completed dialog box opens. 6 Click Finish to exit the Server Administrator uninstallation.
For managed systems, use this command: msiexec.exe /x {89C7A9F7-2C31-4739-842D-F037B6C9B674} For management stations, use this command: msiexec.exe /x {DA60872C-9147-4A6E-9AEF-95BAB5EF3A3B} Performing an Unattended Uninstallation of Managed System Software The Dell PowerEdge Installation and Server Management CD features an unattended uninstallation procedure. Unattended uninstallation enables you simultaneously to uninstall managed systems software from multiple systems.
Managed System Software Installation Using Third-Party Deployment Software You can use third-party deployment software, such as Altiris Deployment Solution, to install managed systems software onto supported Dell systems. To distribute and install Server Administrator using Altiris, start your Altiris application and import OpenManage_Jobs.bin located on the Dell PowerEdge Installation and Server Management CD at \srvadmin\support\Altiris. Specify a job folder into which to import it.
Installing Managed System Software on Red Hat® Enterprise Linux and SUSE® Linux Operating Systems Overview You can install managed systems software by one of two methods. The Dell™ PowerEdge™ Installation and Server Management CD provides installation scripts and RPM packages to install, upgrade, and uninstall Dell OpenManage™ Server Administrator and other managed system software components on your managed system.
Before You Begin • Read the installation requirements to ensure that your system meets or exceeds the minimum requirements. • Read the Dell OpenManage Server Administrator Compatibility Guide. This guide contains compatibility information about Server Administrator installation and operation on various hardware platforms running supported Microsoft® Windows®, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server operating systems. • Read the Dell OpenManage installation readme_ins.
System Requirements Managed systems software must be installed on each system to be managed. You can then manage each system running the managed systems software locally or remotely through a supported Web browser. Managed System Requirements • One of the supported operating system versions. • A minimum of 64 MB of RAM. • A minimum of 256 MB of free hard drive space. • Administrator rights. • A TCP/IP connection on the monitored system and the remote system to facilitate remote system management.
Installation Procedures This section explains how to install, upgrade, and uninstall Server Administrator on a system that is running a supported Red Hat Enterprise Linux or a supported SUSE Linux Enterprise Server operating system. Server Administrator can be installed and upgraded from the Dell PowerEdge Installation and Server Management CD using scripts or RPM commands.
Determining the Running Kernel 1 Log in as root. 2 Type the following command at a console and press : uname -r The system displays a message identifying the running kernel. If it is not one of those listed in the managed system software readme file, then the managed system software may need to use DKS to support it. Dynamic Kernel Support Prerequisites For managed system software to use DKS, the following dependencies must be met before starting Server Administrator.
Copying a Dynamically Built Device Driver to Systems Running the Same Kernel When Server Administrator dynamically builds a device driver for the running kernel, it installs the device driver into the /lib/modules//kernel/drivers/firmware directory, where is the kernel name (returned by typing uname -r).
Forcing Dynamic Kernel Support on Red Hat Enterprise Linux Update Releases When Kernel is Tainted Server Administrator provides precompiled device drivers for the "Gold" releases of supported Red Hat Enterprise Linux operating systems. Red Hat Enterprise Linux supports loading device drivers built for the "Gold" release, on the Update releases.
OpenIPMI Device Driver The Server Administrator Instrumentation Service of Server Administrator requires the OpenIPMI device driver in order to provide IPMI-based information and functionality. It also requires a minimum version of the OpenIPMI device driver. The minimum version required is defined based on the Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system. This requirement is checked and enforced by Server Administrator at three instances.
Re-attempt to install the srvadmin-hapi RPM and any other RPMs that failed to install as they depend on the srvadmin-hapi RPM. Perform the following steps: 1 Navigate to the srvadmin/linux/custom/* directory that you previously were at. 2 Run the following command to see which Server Administrator packages were previously successfully installed. rpm –qa | grep srvadmin The query displays a list of all installed Server Administrator packages.
Degradation of Functionality When Server Administrator Instrumentation Service is Started After Server Administrator is installed, the Server Administrator Instrumentation Service will do a run-time check of the OpenIPMI device driver whenever it is started. The Server Administrator Instrumentation Service is started whenever you run either the srvadmin-services.sh start or srvadmin-services.
Prerequisites for Installing Managed System Software • You must be logged in as root. • The running kernel must have loadable module support enabled. • Your /opt directory must have at least 250 MB of free space, and your /tmp and /var directories must each have at least 20 MB of free space. If you choose to use a non-default directory for the installation, then that directory must also have at least 250 MB of free space.
3 When you have mounted the CD, you can navigate to it with cd /mnt/cdrom/srvadmin/linux/ 4 Get a listing of the directories with ls. The directories on the CD that pertain to Red Hat Enterprise Linux are the following: srvadmin/linux srvadmin/linux/custom srvadmin/linux/RPMS srvadmin/linux/supportscripts Express Install Use the provided shell script to perform the express installation in silent and unattended mode.
Custom Install Managed system software provides two custom installation paths. One is RPM-based, with pre-configured custom directories, and the other is shell script-based. Using Pre-configured Custom Directories to Perform the Custom Installation See Table 7-1 for details about using the RPMs to perform a custom installation using pre-configured custom directories. Table 7-1.
5 Type the following command. rpm -ihv srvadmin-base/*.rpm add-openipmi-RHEL4/srvadmin-ipmi*.rpm add-storageservices/*.rpm NOTE: This command is for the RedHat Enterprise Linux (Version 4) operating system. Apply the operating system specific srvadmin-ipmi RPM corresponding to your system. Server Administrator services do not start automatically.
5 To install the Storage Management Service components, type the following command. sh srvadmin-install.sh --storage (these are long options) or sh srvadmin-install.sh -s (these are short options) NOTE: Long options can be combined with short options, and vice-versa. NOTE: Just before the Server Administrator RPMs are installed, the srvadmin-install.sh shell script automatically calls the srvadmin-openipmi.
6 Choose c to copy, i to install, r to reset and start over, or q to quit. • If you choose c, you are prompted to enter the absolute destination path. • If you choose i, a message states that the RPMs will be installed in the /opt/dell/srvadmin directory. You can then choose y to change, or to use the default installation path. When the installation is completed, the script will have an option for starting the services.
Creating and Distributing the Express Unattended Installation Package The Express Install unattended installation option uses the /srvadmin/linux/supportscripts and the /srvadmin/linux/RPMS subdirectories of the Dell PowerEdge Installation and Server Management CD as the unattended installation package. RPM accesses the Dell PowerEdge Installation and Server Management CD to install all required Server Administrator components on selected remote systems.
Upgrading From Previous Versions If your system is running Dell OpenManage software prior to version 4.2, uninstall the current version before attempting to install the new version. Upgrading From Version 4.3 or Later For Dell OpenManage software versions 4.3 and later, you can upgrade your system using RPM commands or the srvadmin-install.sh shell script. Ensure that all installed components are upgraded when you perform either procedure. NOTE: Use of the install script, srvadmin-install.
To upgrade all the previously installed packages using individual RPMs, perform the following steps: a Query the rpm database for all installed srvadmin packages by typing: rpm -qa | grep srvadmin The query displays a list of all installed packages, including any existing or older versions. For example: srvadmin-omilcore-4.3.0-1.386.rpm srvadmin-hapi-4.3.0-1.386.rpm srvadmin-deng-4.3.0-1.386.rpm srvadmin-isvc-4.3.0-1.386.rpm ...
Reattempt to upgrade the srvadmin-hapi RPM and any other RPMs that failed to upgrade as they depend on the srvadmin-hapi RPM. Perform the following steps: 1 Navigate back to the previous directory that you were at. 2 Run the following commands to see which Server Administrator packages were previously successfully upgraded. rpm -qa | grep srvadmin The query displays a list of all installed Server Administrator packages. Those that have already been upgraded will display the new version number.
Using the srvadmin-install Shell Script 1 Log on as root to the system running Red Hat Enterprise Linux that requires the upgrade. 2 Insert the Dell PowerEdge Installation and Server Management CD into the CD drive on your system. If the CD does not mount automatically, type mount /dev/cdrom /mnt/cdrom.
Uninstalling Managed System Software You can uninstall managed system software from the Red Hat Enterprise Linux or SUSE Linux Enterprise Server command line. Additionally, you can perform an unattended uninstallation on multiple systems simultaneously. Prerequisites for Uninstalling Managed System Software You must be logged in as root.
Managed System Software Installation Using Third-Party Deployment Software You can use third-party deployment software, such as Altiris Deployment Solution, to install managed system software onto supported Dell servers. To distribute and install managed system software using Altiris, start your Altiris application and import OpenManage_Jobs.bin located on the Dell PowerEdge Installation and Server Management CD at \srvadmin\support\Altiris. Specify a job folder into which you want to import it.
Installing Managed System Software on Supported Linux Operating Systems
Using Microsoft® Active Directory® Controlling Access to Your Network If you use Active Directory service software, you can configure it to control access to your network. Dell has modified the Active Directory database to support remote management authentication and authorization. Dell OpenManage™ IT Assistant and Dell OpenManage Server Administrator, as well as Dell™ remote access controllers, can now interface with Active Directory.
Overview of the Active Directory Schema Extensions Dell created Classes, or groups of objects, that can be configured by the user to meet their unique needs. New Classes in the schema include an Association, a Product, and a Privilege class. An Association object links the users or groups to a given set of privileges and to systems (Product Objects) in your network.
Figure 8-1. Typical Setup for Active Directory Objects Association Object User(s) Group(s) Privilege Object Dell Product(s) RAC Privilege Object RAC Device Object Server Administrator Privilege Object Server Administrator Application Object IT Assistant Privilege Object IT Assistant Application Object In addition, you can set up Active Directory objects in a single domain or in multiple domains.
Figure 8-2. Setting Up Active Directory Objects in a Single Domain AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 RAC1 RAC2 To set up the objects for the single domain scenario, perform the following tasks: 1 Create two Association Objects. 2 Create two RAC Product Objects, RAC1 and RAC2, to represent the two DRAC 4 cards. 3 Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (Administrator) and Priv2 has Login privileges. 4 Group User1 and User2 into Group1.
Figure 8-3. Setting Up RAC Active Directory Objects in Multiple Domains Domain1 Domain2 AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 RAC1 RAC2 To set up the objects for this multiple domain scenario, perform the following tasks: 1 Ensure that the domain forest function is in Native or Windows 2003 mode. 2 Create two Association Objects, AO1 (of Universal scope) and AO2, in any domain. The figure shows the objects in Domain2.
For Server Administrator or IT Assistant, on the other hand, the users in a single Association can be in separate domains without needing to be added to a universal group. The following is a very similar example to show how Server Administrator or IT Assistant systems in separate domains affect the setup of directory objects. Instead of RAC devices, you’ll have two systems running Server Administrator (Server Administrator Products sys1 and sys2). Sys1 and sys2 are in different domains.
6 Add User1 and User2 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both sys1 and Group1 as Products in AO1. 7 Add User3 as a Member in Association Object 2 (AO2), Priv2 as a Privilege object in AO2, and Group1 as a Product in AO2. Note that neither of the Association objects needs to be of Universal scope in this case.
To use the LDIF files, see the instructions in the readme that is in the LDIF files directory. To use the Dell Schema Extender to extend the Active Directory Schema, perform the steps in "Using the Dell Schema Extender." You can copy and run the Schema Extender or LDIF files from any location. Using the Dell Schema Extender NOTICE: The Dell Schema Extender uses the SchemaExtenderOem.ini file.
Table 8-2. dellRacDevice Class OID 1.2.840.113556.1.8000.1280.1.1.1.1 Description This class represents the Dell RAC device. The RAC Device must be configured as dellRacDevice in Active Directory. This configuration enables the DRAC 4 to send LDAP queries to Active Directory. Class Type Structural Class SuperClasses dellProduct Attributes dellSchemaVersion dellRacType Table 8-3. dellAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.1.1.
Table 8-5. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.4 Description This class is used as a container Class for the Dell Privileges (Authorization Rights). Class Type Structural Class SuperClasses User Attributes dellRAC4Privileges dellRAC3Privileges dellOmsaAuxClass dellItaAuxClass Table 8-6. OID 1.2.840.113556.1.8000.1280.1.1.1.5 Description This is the main class from which all Dell products are derived.
Table 8-8. dellOmsa2AuxClass Class OID 1.2.840.113556.1.8000.1280.1.2.1.1 Description This class is used to define the privileges (Authorization Rights) for Server Administrator. Class Type Auxiliary Class SuperClasses None Attributes dellOmsaIsReadOnlyUser dellOmsaIsReadWriteUser dellOmsaIsAdminUser Table 8-9. dellOmsaApplication Class OID 1.2.840.113556.1.8000.1280.1.2.1.2 Description This class represents the Server Administrator application.
Table 8-11. dellItaApplication Class OID 1.2.840.113556.1.8000.1280.1.3.1.2 Description This class represents the IT Assistant application. IT Assistant must be configured as dellItaApplication in Active Directory. This configuration enables IT Assistant to send LDAP queries to Active Directory. Class Type Structural Class SuperClasses dellProduct Attributes dellAssociationMembers Table 8-12.
Table 8-13. RAC-specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellIsLoginUser 1.2.840.113556.1.8000.1280.1.1.2.3 TRUE TRUE if the User has Login rights on the device. Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) dellIsCardConfigAdmin 1.2.840.113556.1.8000.1280.1.1.2.4 TRUE TRUE if the User has Card Configuration rights on Boolean (LDAPTYPE_BOOLEAN the device. 1.3.6.1.4.1.1466.115.121.1.
Table 8-13. Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellSchemaVersion 1.2.840.113556.1.8000.1280.1.1.2.12 TRUE The Current Schema Version is used to update the schema. Case Ignore String (LDAPTYPE_CASEIGNORESTRING 1.2.840.113556.1.4.905) dellRacType 1.2.840.113556.1.8000.1280.1.1.2.13 This attribute is the Current Rac Type for the dellRacDevice object and the backward link to the dellAssociationObjectMembers forward link.
Active Directory Users and Computers Snap-In Installing the Dell Extension to the Active Directory Users and Computers Snap-In When you extend the schema in Active Directory, you must also extend the Active Directory Users and Computers snap-in so that the administrator can manage Products, Users and User Groups, Associations, and Privileges. You only need to extend the snap-in once, even if you have added more than one schema extension.
Creating a Product Object NOTE: Server Administrator and IT Assistant users must use Universal-type Product Groups to span domains with their product objects. NOTE: When adding Universal-type Product Groups from separate domains, you have to create an Association object with Universal scope. The default Association objects created by the Dell Schema Extender utility are domain Local Groups and will not work with Universal-type Product Groups from other domains.
Creating an Association Object The Association Object is derived from a Group and must contain a group Type. The Association Scope specifies the Security Group Type for the Association Object. When you create an Association Object, you must choose the Association Scope that applies to the type of objects you intend to add. Selecting Universal, for example, means that Association Objects are only available when the Active Directory Domain is functioning in Native Mode or above.
To add Products: 1 Select the Products tab and click Add. 2 Type the system, device, or group name and click OK. 3 In the Properties window, click Apply and then OK. Enabling SSL on a Domain Controller (RAC Only) If you plan to use Microsoft Enterprise Root CA to automatically assign all your domain controllers SSL certificates, you must perform the following steps to enable SSL on each domain controller. 1 Install a Microsoft Enterprise Root CA on a Domain Controller.
11 Locate and right-click the root CA certificate, select All Tasks, and click Export. 12 In the Certificate Export Wizard, click Next and select No do not export the private key. 13 Click Next and select Base-64 encoded X.509 (.cer) as the format. 14 Click Next and save the certificate to a location of your choice. You will need to upload this certificate to the DRAC 4. To do this, go to the DRAC 4 Web-based interface→ Configuration tab→ Active Directory page.
Configuring Active Directory Using CLI on Systems Running Server Administrator You can use the omconfig preferences dirservice command to configure the Active Directory service. The productoem.ini file is modified to reflect these changes. If the adproductname is not present in the productoem.ini file, a default name will be assigned.
Configuring the DRAC 4 Using the Web-Based Interface 1 Log in to the Web-based interface using the default user, root, and its password. 2 Click the Configuration tab and select the Active Directory. 3 Select the Enable Active Directory check box. 4 Type the DRAC 4 Name. This name must be the same as the common name of the RAC object you created in your Domain Controller (see "Installing the Dell Extension to the Active Directory Users and Computers Snap-In"). 5 Type the Root Domain Name.
Configuring the DRAC 4 Active Directory Settings Using the racadm CLI Using the following commands to configure the DRAC 4 Active Directory feature using the racadm CLI instead of the Web-based interface.
Prerequisite Checker Command Line Operation of the Prerequisite Checker You can run the prerequisite check silently by executing runprereqchecks.exe /s from the \windows\PreReqChecker directory. After running the prerequisite check, an HTML file will be created in the %Temp% directory. The file is named omprereq.htm, and it contains the results of the prerequisite check. The Temp directory is not usually X:\Temp, but X:\Documents and Settings\username\Local Settings\Temp.
Table 9-1. Return Codes While Running the Prerequisite Check Silently (continued) Return Code Description -3 The user does not have Administrator privileges. The Prerequisite Checker will not run. -4 Not an implemented return code. -5 The user failed to change the working directory to %TEMP%. The Prerequisite Checker will not run. -6 The destination directory does not exist. The Prerequisite Checker will not run. -7 An internal error has occurred. The Prerequisite Checker will not run.
Frequently Asked Questions General Is the Dell™ PowerEdge™ Installation and Server Management CD a bootable CD? Yes, the CD is bootable. It boots into the Dell OpenManage™ Server Assistant operating system setup mode by default. After installing managed system software, if an operating system was previously installed, you will be given the option to boot from the operating system. It is recommended that you eject the CD to avoid booting into Server Assistant setup mode.
Microsoft® Windows® How do I fix a faulty installation of Server Administrator? You can fix a faulty installation by forcing a reinstall and then performing an uninstall of Server Administrator. To force a reinstall: • Find out the version of Server Administrator that was previously installed. • Download the installation package for that version from the Dell Support website at support.dell.com. • Locate SysMgmt.msi from the srvadmin\windows\SystemsManagement directory and enter the following command a
What is an MSP service pack file? Should I upgrade my Dell OpenManage 4.3 version with the MSP file? A Microsoft Service Pack (MSP) file stores only the differences between an old version and a new version. It is much smaller in size than the upgrade file. You can either use the MSP file or the new MSI file to upgrade your Dell OpenManage 4.3. Using the MSP file is a good idea as it is more efficient. NOTE: You can upgrade from Dell OpenManage software version 4.3 to 5.
How do I perform an unattended operating system installation with the Installation and Server Management CD? You can install a Windows operating system on many systems using identical settings, which allows consistent configurations across all systems. To use this feature, it is necessary that the target Dell PowerEdge systems be configured identically, with the same hardware and operating system components. Any difference in configuration makes the replication feature unusable.
What is the best way to use the Prerequisite Checker information? The Prerequisite Checker is available for Windows. See the readme file \srvadmin\windows\PreReqChecker\readme.txt on the Dell PowerEdge Installation and Server Management CD for detailed information about how to use the Prerequisite Checker. In the Prerequisite Checker screen, I get the message "An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly.
Table 10-1.
3 Insert the Red Hat Enterprise Linux or SUSE Linux Enterprise Server installation CD and follow the instructions to complete the installation. Reboot the system to complete the installation. 4 When the installation is completed on the first system, copy the files from the /root/replication directory to a diskette. 5 For each subsequent unattended installation, insert the disk containing the replication files into the diskette drive and boot the system. The installation interview will be done automatically.
What are the names of all the Dell OpenManage features under Red Hat Enterprise Linux or SUSE Linux Enterprise Server? The following table lists the names of all Dell OpenManage features and their corresponding init script names under Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems: Table 10-2.
What do the directories under srvadmin/linux/custom contain? The following table lists the names of the directories in the srvadmin/linux/custom directory. Table 10-3. Names of the Directories Under the srvadmin/linux/custom Directory Name of RPM Description Other Server Administrator RPMs required srvadmin-base — This is the core code for Server Administrator.
Table 10-3. Names of the Directories Under the srvadmin/linux/custom Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-odf Server Administrator Online Diagnostic Common Components — Systems management online diagnostics framework. srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore NOTE: The srvadmin-odf RPM, though installed, will not be functional as Diagnostics is no longer available through Server Administrator.
Table 10-3. Names of the Directories Under the srvadmin/linux/custom Directory (continued) Name of RPM Description srvadmin-racvnc RAC VNC Remote Service and Remote Services Server Agent. Other Server Administrator RPMs required srvadmin-omilcore and srvadminracser add-RAC4 — Software for remote management of fourth generation Remote Access Controllers. For example: DRAC 4. srvadmin-rac4components Remote Access Card Data Populator — Remote Access Controller components.
Table 10-3. Names of the Directories Under the srvadmin/linux/custom Directory (continued) Name of RPM Description Other Server Administrator RPMs required add-openipmi-RHEL3 — Provides OpenIPMI support for Red Hat Enterprise Linux (version 3) dkms Dynamic Kernel Module Support Framework — This package contains the framework for the Dynamic Kernel Module Support (DKMS) method for installing module RPMS as originally developed by Dell Computer Corporation. openipmi Openipmi XX.Y.
What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems after Server Administrator is started? The daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems depend on what has been installed and what is enabled to run. The following table displays the daemons that typically run for a full install: Table 10-4.
What kernel modules are loaded when Server Administrator is started? This is dependent on the type of systems instrumentation. The following table displays the kernel modules loaded when Server Administrator is started. Table 10-5.
Glossary The following list defines technical terms, abbreviations, and acronyms used in your system documents. attribute bootable diskette As it relates to an attribute is a piece of information related to a component. Attributes can be combined to form groups. If an attribute is defined as read-write, it may be defined by a management application. You can start your system from a diskette.
cm directory Abbreviation for centimeter(s). Novell® ConsoleOne® is a Java-based foundation for graphical utilities that manage and administer network resources from different locations and platforms. ConsoleOne provides a single point of control for all Novell and external products. Directories help keep related files organized on a disk in a hierarchical, "inverted tree" structure. Each disk has a "root" directory; for example, a C:\> prompt normally indicates that you are at the root directory of hard
expansion-card connector format A connector on the system's system board or riser board for plugging in an expansion card. To prepare a hard drive or diskette for storing files. An unconditional format deletes all data stored on the disk. extended memory RAM above 1 MB. Most software that can use it, such as the Microsoft® Windows® operating system, requires that extended memory be under the control of an XMM. FSMO Abbreviation for Flexible Single Master Operation.
HBA I/O Abbreviation for host bus adapter. A PCI adapter card that resides in the system whose only function is to convert data commands from PCI-bus format to storage interconnect format (examples: SCSI, Fibre Channel) and communicate directly with hard drives, tape drives, CD drives, or other storage devices. Abbreviation for input/output. The keyboard is an input device, and a printer is an output device. In general, I/O activity can be differentiated from computational activity.
ISV LRA Abbreviation for independent software vendor. Abbreviation for local response agent. ITE managed system Abbreviation for information technology equipment. A managed system is any system that is monitored and managed using Dell OpenManage™ Server Administrator. Systems running Server Administrator can be managed locally or remotely through a supported Web browser. See remote management system. Java A cross-platform programming language developed by Sun Microsystems.
microprocessor name The primary computational chip inside the system that controls the interpretation and execution of arithmetic and logic functions. Software written for one microprocessor must usually be revised to run on another microprocessor. CPU is a synonym for microprocessor. The name of an object or variable is the exact string that identifies it in an SNMP Management Information Base (MIB) file or in a CIM Management Object File (MOF). NDS Abbreviation for Novell Directory Service.
online access service peripheral device A service that typically provides access to the Internet, e-mail, bulletin boards, chat rooms, and file libraries. An internal or external device—such as a printer, a disk drive, or a keyboard—connected to a system. PAM physical memory array Acronym for Pluggable Authentication Modules. PAM allows system administrators to set an authentication policy without having to recompile authentication programs.
PPP read-only file Abbreviation for Point-to-Point Protocol. A read-only file is one that you are prohibited from editing or deleting. A file can have read-only status if: program diskette set The set of diskettes from which you can perform a complete installation of an operating system or application program. When you reconfigure a program, you often need its program diskette set.
ROM secure port server Acronym for read-only memory. Your system contains some programs essential to its operation in ROM code. Unlike RAM, a ROM chip retains its contents even after you turn off your system. Examples of code in ROM include the program that initiates your system's boot routine and the POST. An application that makes Web pages available for viewing by Web browsers using the HTTPS protocol. See Web server. RPM Abbreviation for Red Hat® Package Manager.
SIMM SVGA Acronym for single in-line memory module. A small circuit board containing DRAM chips that connects to the system board. Abbreviation for super video graphics array. VGA and SVGA are video standards for video adapters with greater resolution and color display capabilities than previous standards. SMTP To display a program at a specific resolution, you must install the appropriate video drivers and your monitor must support the resolution.
system diskette termination System diskette is a synonym for bootable diskette. Some devices (such as the last device at each end of a SCSI cable) must be terminated to prevent reflections and spurious signals in the cable. When such devices are connected in a series, you may need to enable or disable the termination on these devices by changing jumper or switch settings on the devices or by changing settings in the configuration software for the devices.
time-out URL A specified period of system inactivity that must occur before an energy conservation feature is activated. Abbreviation for Uniform Resource Locator (formerly Universal Resource Locator). tpi USB Abbreviation for tracks per inch. Abbreviation for Universal Serial Bus. A USB connector provides a single connection point for multiple USB-compliant devices, such as mice, keyboards, printers, and computer speakers.
VGA feature connector video mode On some systems with a built-in VGA video adapter, a VGA feature connector allows you to add an enhancement adapter, such as a video accelerator, to your system. A VGA feature connector can also be called a VGA pass-through connector. Video adapters normally support multiple text and graphics display modes. Character-based software displays in text modes that can be defined as x columns by y rows of characters.
VNC Windows NT Acronym for Virtual Network Computing. In a VNC system, servers provide applications, data, and the desktop environment, all of which may be accessed through the Internet. High-performance server and workstation operating system software developed by Microsoft that is intended for technical, engineering, and financial applications. VRAM write-protected Acronym for video random-access memory.
Index A Association Scope, 135 C access read-only, 28 write, 28 ATA, 15 CA, 51, 137 Certificate, 139 access control, 27 attribute, 157 authentication, 19, 29, 120 authorization, 120 accounts, 35 Active Directory, 19, 27, 29, 36, 38, 120, 125, 133, 138 object identifiers, 119 objects, 121 schema, 125 schema extender utility, 125-126 schema extensions, 119 ADDLOCAL, 68, 89-90 administrator, 28 Administrator Pack, 133 Administrator privileges, 28, 77 agent, 45 SNMP, 39 B Baseboard Management Controlle
Index command line, 90 Dell organizational unit, 125 domain, 35-36 command line interface, 16, 29 Dell PowerEdge Documentation CD, 11 domain controller, 136-137 Common Information Model, 16, 33, 75 Dell PowerEdge Installation and Server Management CD, 11, 14, 73, 143 configuration, 45 console, 11, 13, 16 controller ERA/MC, 17 ERA/O, 17 crash, 14 Dell PowerEdge Server Update Utility CD, 11, 15 Dell PowerEdge Service and Diagnostic Utilities CD, 11, 15 DRAC, 16, 133, 137 DRAC 4, 137, 139, 150
G ISV, 64, 68, 86, 93, 110-111 Globally Unique Identifier (GUID), 90 IT Assistant, 11-12, 124, 143, 148 group privileges, 28 GUID, 84 H help, 17 J Java Secure Socket Extension, 29 JSSE, 29 hot spares, 15 HTTP, 20-21, 25-26 K HTTPS, 20, 22, 24-27, 29 kernel precompiled, 98 I management station, 9, 11-13, 33, 42, 55, 58, 61 Management Station Services, 107, 148 MIB, 16, 43 Microsoft Active Directory, 19, 27, 29, 36, 38, 133 Software Installer, 83 Windows Installer Engine, 58 Windows Server 2003, 1
Index O Q RMCP, 20 oem.
server proxy, 34 SOL, 13 U SOL Proxy, 13 UDP, 21 Server Administrator, 14, 16, 124, 150 Diagnostics, 11 Services, 107, 148 SSH, 21, 23 SSL, 29, 125, 136 unattended installation, 63, 85, 146, 148 SSL encryption, 19 unattended uninstallation, 93 Server Assistant, 12 standard action, 83 universal groups, 135 Server Update Utility, 15 storage management, 11, 28 update packages, 17 session timeout, 50 setup custom, 33, 58 express, 33, 58 Storage Management Service, 15, 148 updates, 15 software,
Index W wakeup, 12 Web certificates, 51 Windows Installer Engine, 87 Installer Service, 83 Windows Management Instrumentation, 33, 75 Windows Server 2003, 145 WMI, 33, 39, 75 write access, 28 X X.
