Dell™ OpenManage™ Installation and Security User’s Guide
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. ___________________ Information in this document is subject to change without notice. © 2008 Dell Inc. All rights reserved.
Contents 1 Introduction . Overview . . . . . . . . . . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . . . . . . . . . 11 Systems Management Software Overview . . . . Dell OpenManage Systems Management Software . . 13 . . . . . . . 13 . . . . . . . . . . . . . 14 Dell Systems Management Tools and Documentation DVD . . . . . . . . . Dell Server Updates DVD . Dell OpenManage Systems Management Software Components . . . . . . . . . . . Deployment Software . . . . . . . 14 . . .
Security Management RBAC . . . . . . . . . . . . . . . . . . 37 . . . . . . . . . . . . . . . . . . . . . . . . 37 Microsoft Active Directory . . . . . . . . . . . . . Authentication Protocols for Linux Operating Systems . . . . . . . . . 3 Setup and Administration Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements . . . . . . . . . . . . . . . . Supported Operating Systems and Web Browsers . . . . . . . . . .
Secure Port Server and Security Setup . . . . . . . . . X.509 Certificate Management . 4 60 . . . . . . . . . . 62 Using Unified Server Configurator to Install an Operating System . . . . . . . Overview . . . . 63 . . . . . . . . . . . . . . . . . . . . . . . . 63 Starting the Unified Server Configurator . . . . . . . . Updating the Unified Server Configurator . Installing the Operating System . 5 64 . . . . . . . . . . . . 64 . 67 . . . . . . . . . . . . . . . . . . . . . . . .
Enabling CIM Discovery and Security in IT Assistant . . . . . . . . . . . . . . . Installing SNMP . . . . . . . 70 . . . . . . . . . . . . . . . . . . 70 Installing, Upgrading, and Uninstalling Management Station Software on Systems Running Supported Windows Operating Systems . . . . . . . . . . . . . Installing and Upgrading the Management Station Software . . . . . . . . . . . . . . 70 . . . . 71 . . . . . . . . . 72 . . . . . . . . . . . . . . . . . 72 Typical and Custom Installations .
Installing Managed System Software on Microsoft Windows Operating Systems . 93 Overview . . . . . . . . . . . . . . . . . . . . . . . . . Dell Systems Management Tools and Documentation DVD . . . . . . . . . . . . . . . . 93 . . . . 94 . . . . . . . . . . . . . . . . . . . . 94 Unattended and Scripted Silent Installation Before You Begin 93 Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 . . . . . . . . . . . . . . . 95 Supported Operating System .
Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server . . Introduction . 119 . . . . . . . . . . . . . . . . . . . . . . 119 Installing Managed System and Management Station Software . . . . . . . . . . . . . . . . Running PreReqChecker In CLI Mode . . . . 120 . . . . . . 120 Installing Management Station Software in CLI Mode . . . . . . . . . . . . . . . . Installing Managed System Software In CLI Mode . . . . . . . . . . . . . . 9 . . . .
Using Dell OpenManage with VMware® ESX Server™ Software . . . . . . . . . . Using Dell OpenManage with Citrix® XenServer Dell Edition™ . . . . . . . . . . . . . . 148 . . . . . . . . . 148 Managed System Software Installation Using Third-Party Deployment Software . . . . . . . 10 Using Microsoft Active Directory Controlling Access to Your Network 149 149 . . . . . . . . 156 . . . . . . . . . 157 . . . . . . . . . . . . 162 Using the Dell Schema Extender .
12 Frequently Asked Questions General . . . . . . . . . . 173 . . . . . . . . . . . . . . . . . . . . . . . . 173 Microsoft® Windows® . . . . . . . . . . . . . . . . Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server . . . . . . . . . . . . . . . . . . . . 177 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
Systems Management Software Overview Dell OpenManage systems management software is a suite of applications for your Dell systems. This software enables you to manage your systems with proactive monitoring, diagnosis, notification, and remote access. Each system managed by the Dell OpenManage systems management software is called a managed system. You can manage a managed system either locally or remotely.
Dell OpenManage Systems Management Software The Dell OpenManage systems management software kit is available in the form of the Dell Systems Management Tools and Documentation DVD.
Dell Server Updates DVD The Dell Server Updates DVD contains the Server Update Utility (SUU), an application for identifying and applying firmware, BIOS, and driver updates to your system. The Dell Server Updates DVD is available only as part of the Subscription Service Kit. Dell OpenManage Systems Management Software Components Deployment Software From Dell OpenManage version 6.0.
Management Station Software Dell Remote Access Controller Console The Dell Remote Access Controller (DRAC) console is a management station software designed to provide remote management capabilities for your Dell systems.
• Support that is independent of the system's power or operating state • Text console redirection for system setup, text-based utilities, and operating system consoles • Access to Red Hat Enterprise Linux and SUSE Linux Enterprise Server serial console interfaces using SOL • IPMItool: The ipmitool program provides a simple command-line interface to BMC and features the ability to read the sensor data repository (SDR) and print sensor values, display the contents of the System Event Log (SEL), print F
Remote Access Controller Service The Remote Access Controller service provides the following features: • Remote access to an unresponsive system, allowing you to shut down, restart, and get the system up and running as quickly as possible • Alert notification when a system is down • System crash logs that record the probable cause of system crashes and saves the most recent crash screen NOTE: The Server Administrator Remote Access Controller service and Remote Access Controller management console cann
Diagnostics Dell Online Diagnostics is a suite of diagnostic programs, or test modules, that run locally on your system. Using Online Diagnostics, you can select the appropriate diagnostics tests to run on the hardware that Online Diagnostics discovers on your system. Drivers The Extraction Utility enables you to view and create Dell software driver and diagnostic floppy disks.
• 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 Systems Software Support Matrix provides information about the various Dell systems, the operating systems supported by these systems, and the Dell OpenManage components that can be installed on these systems.
• The Dell OpenManage IT Assistant User’s Guide has information about installing, configuring, and using IT Assistant. IT Assistant provides a central point of access to monitor and manage systems on a local area network (LAN) or wide area network (WAN). By allowing an administrator a comprehensive view across the enterprise, IT Assistant can increase system uptime, automate repetitive tasks, and prevent interruption in critical business operations.
• The Dell OpenManage Server Update Utility User's Guide provides information on using the Dell OpesnManage Server Update Utility. • The software kit (DVD) contain readme files for applications found on the media. Obtaining Technical Assistance If at any time you do not understand a procedure described in this guide, or if your product does not perform as expected, different types of help are available. For more information, see "Getting Help" in your system's Hardware Owner’s Manual.
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®. • Support for Network Information Services (NIS), Winbind, Kerberos, and Lightweight Directory Access Protocol (LDAP) authentication protocols for Linux operating systems.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable Dell OpenManage Baseboard Management Controller - PowerEdge™ x8xx systems 623 RMCP UDP PowerE None dge x8xx In/Out IPMI access No through LAN systems only Dell OpenManage Baseboard Management Utility 623 Telnet TCP 1.x None In/Out Accepts Yes incoming Telnet connections 623 RMCP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable 4995 HTTPS TCP 2.0 128-bit SSL In/Out Web GUI Yes 1024 DCOM 65535 (Dynamically assigned) TCP/ 2.0 UDP None In/Out Viewing of Port range client can be management restricted. data Dell OpenManage Client Instrumentation 20 HTTP TCP 7.x and FTP None In/Out Flash BIOS No communicat ion 21 HTTP TCP 7.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level Configurable Dell OpenManage IT Assistant For information on Dell OpenManage IT Assistant UDP/TCP Ports default location, see the Dell OpenManage IT Assistant User’s Guide. Dell OpenManage Server Administrator 22 SSH TCP 2.0 128-bit In/Out Remote Yes Server Administrat or Command Line (for IT Assistant).
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 135 RPC TCP/ 2.0 UDP None In/Out Remote No Server Administrat or Command Line (for IT Assistant). Remote software update feature (for Windows operating systems). 139 NetBIOS TCP 2.0 None In/Out Remote No Server Administrat or Command Line (for IT Assistant). Remote Software Update (for Windows operating systems). 161 SNMP UDP 1.x, 2.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol 445 NetBIOS TCP 2.0 None In/Out Remote No software updates to Server Administrat or (for Windows operating systems) 1311 HTTPS TCP 1.x 128-bit SSL In/Out Web GUI Yes 11487 Proprietary UDP 1.x None In Remote Flash BIOS update initiation from IT Assistant Yes 11489 Proprietary TCP 1.x None In Remote Yes Flash BIOS update file transfer from IT Assistant 1024 65535 DCOM TCP/ 2.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 21 FTP TCP 1.0 None In/Out Firmware No update through FTP and certificate upload/downl oad 23 Telnet TCP 1.0 None In/Out Optional No Telnet-based CLI management 25 SMTP TCP 1.0 None In/Out Optional email alert messages No 68 DHCP UDP 1.2 None In/Out DHCP assigned IP address No 69 TFTP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 443 HTTPS TCP 3.2 5869 Configurable 128-bit SSL In/Out Remote No racadm CLI utility Proprietar TCP 1.0 y None In/Out Remote No racadm CLI utility 5900 VNC TCP 1.0 56 bit DES In/Out Video redirection Yes 5900 VNC TCP 3.2 128-bit RC In/Out Video redirection Yes 5981 VNC TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 53 DNS UDP 1.20 None In/Out Dynamic No Domain name server (DNS) registration of the host name assigned within DRAC 68 DHCP UDP 1.0 None In/Out DHCP assigned IP address No 69 TFTP UDP 1.0 None In/Out Firmware update through Trivial FTP No 80 HTTP TCP 1.0 None In/Out Web GUI Yes redirected to HTTPS 161 SNMP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 636 LDAPS TCP 1.0 128-bit SSL In/Out Optional No Active Directory Services (ADS) authenticati on 3269 LDAPS TCP 1.0 128-bit SSL In/Out Optional No ADS authenticati on 3668 Proprietar TCP 1.0 y None In/Out CD/diskette Yes virtual media service 5869 Proprietar TCP 1.0 y None In/Out Remote racadm No 5900 Proprietar TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 53 DNS UDP 1.0 None In/Out Dynamic No DNS registration of host name assigned within DRAC 68 DHCP UDP 1.0 None In/Out DHCP assigned IP address No 69 TFTP UDP 1.0 None In/Out Firmware update through Trivial FTP No 80 HTTP TCP 1.0 None In/Out Web GUI Yes redirected to HTTPS 161 SNMP UDP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 636 LDAPS TCP 1.0 128-bit SSL In/Out Optional No ADS authenticati on 3269 LDAPS TCP 1.0 128-bit SSL In/Out Optional No ADS authenticati on 22 SSHv2 TCP 1.30 128-bit SSL In/Out Optional Yes Secure Shell (SSH) CLI management 23 Telnet TCP 1.0 None In/Out Optional Yes Telnet CLI management 25 SMTP TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol Port Version Maximum Direction Usage Type Encryption Level 80 HTTP TCP 1.0 None In/Out Web GUI Yes redirected to HTTPS 161 SNMP UDP 1.0 None In/Out SNMP query No management 162 SNMP UDP 1.0 None Out SNMP trap event 443 HTTPS TCP 1.0 128-bit SSL In/Out Web No management GUI and remote racadm CLI utility 623 RMCP/R UDP 1.0 MCP+ 128-bit SSL In/Out IPMI over LAN 636 LDAPS TCP 1.
Table 2-1. Dell OpenManage UDP/TCP Ports Default Locations (continued) Port # Protocol 5901 Port Version Maximum Direction Usage Type Encryption Level Configurable TCP 1.0 128-bit SSL In Console Yes Redirection: keyboard/mo use Digital KVM 2068 Proprietary TCP 1.0 128-bit SSL In/Out Video No Redirection — Keyboard/M ouse 3668 Proprietary TCP 1.0 None In/Out Virtual Media No 8192 Proprietary TCP 1.0 None In/Out Video redirection to client viewer No NOTE: CIM ports are dynamic.
Security Management Dell provides security and access administration through role-based access control (RBAC), authentication, and encryption, or through Active Directory (or through Winbind, Kerberos, LDAP, or NIS on Linux operating systems) for both the Web-based and command line interfaces. RBAC RBAC manages security by determining the operations that can be executed by users in specific roles.
Table 2-2. User Privileges User Privileges Access Type Admin Write Read User X Power User Administrator X X X X X Admin access allows you to shut down the managed system. Write access allows you to modify or set the values on the managed system. Read access allows you to view the data reported by Server Administrator. Read access does not allow you to change or set the values on the managed system.
Authentication The Server Administrator authentication scheme ensures that the 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. This authentication scheme ensures that all Server Administrator functions, whether accessed through the Server Administrator home page or CLI, are properly authenticated.
remote management authentication and authorization. IT Assistant, Server Administrator, and Dell Remote Access Controllers can interface with Active Directory to add and control users and privileges from one central database. For information about using Active Directory, see "Using Microsoft Active Directory." Authentication Protocols for Linux Operating Systems Dell OpenManage applications (version 5.
Setup and Administration 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 document contains compatibility information about Dell™ OpenManage™ software installation and operation on various hardware platforms (systems) running supported Microsoft® Windows®, Red Hat® Enterprise Linux®, and SUSE® Linux Enterprise Server operating systems.
System Requirements Dell OpenManage Server Administrator software must be installed on each system to be managed. You can then manage each system running Server Administrator locally or remotely through a supported Web browser.
Supported Systems Management Protocol Standards A supported systems management protocol must be installed on the managed system before installing your management station or managed system software. On supported Windows operating systems, Dell OpenManage software supports: Common Information Model/Windows Management Instrumentation (CIM/WMI) and Simple Network Management Protocol (SNMP).
Viewing Localized Versions of the Web-Based Interface Use Regional and Language Options in the Windows Control Panel to view localized versions of the Web-based interface, on systems running Windows operating systems. Assigning User Privileges To ensure critical system component security, you must properly assign user privileges to all Dell OpenManage software users before installing the Dell OpenManage software.
5 Double-click the icon representing the user that you just created. 6 Click the Member of tab. 7 Click Add. 8 Select the appropriate group and click Add. 9 Click OK, and then click OK again. New users can log into the Dell OpenManage software with the user privileges for their assigned group and domain. Creating Users for Supported Red Hat Enterprise Linux and SUSE Linux Enterprise Server Operating Systems Administrator access privileges are assigned to the user logged in as root.
Creating Users With Power User Privileges 1 Run the following command from the command line: useradd -d home-directory -g root username NOTE: You must set root as the primary group. 2 Type passwd username and press . 3 When prompted, enter a password for the new user. The new user can now log into Dell OpenManage software with Power User group privileges. Microsoft Active Directory If you use Active Directory service software, you can configure it to control access to your network.
see the Securing an SNMP Environment article, dated May 2003, in the Dell Power Solutions magazine. This magazine is also available at www.dell.com/powersolutions. NOTE: For IT Assistant to retrieve systems management information from a system running Server Administrator, the community name used by IT Assistant must match a community name on the system running Server Administrator.
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.
4 Scroll down the list of services to SNMP Service, right-click SNMP Service, and click Properties. The SNMP Service Properties window appears. 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 the management station (the default is public) in the Community Name text box and click Add. The SNMP Service Properties window appears.
5 Click the Security tab to change the access rights for a community. 6 Select a community name in the Accepted Community Names list, and then click Edit. The SNMP Service Configuration window appears. 7 Set the Community Rights to READ WRITE or READ CREATE, and click OK. The SNMP Service Properties window appears. 8 Click OK to save the changes. NOTE: In Dell OpenManage Server Administrator version 5.3 and later, SNMP Set Operations are disabled by default in Server Administrator.
5 Click the Traps tab to add a community for traps or to add a trap destination for a trap community. a To add a community for traps, type the community name in the Community Name box and click Add to list, which is located next to the Community Name box. b To add a trap destination for a trap community, select the community name from the Community Name drop-down box and click Add under the Trap Destinations box. The SNMP Service Configuration window appears. c Type the trap destination and click Add.
Server Administrator SNMP Agent Install Actions If Server Administrator detects the default SNMP configuration during installation, it attempts to modify the SNMP agent configuration to give read-only access to the entire MIB tree for the public community. Server Administrator modifies the /etc/snmp/snmpd.conf SNMP agent configuration file in two ways. The first change is to create a view to the entire MIB tree by adding the following line if it does not exist: view all included .
Changing the SNMP Community Name Configuring the SNMP community names determines which systems are able to manage your system through SNMP. The SNMP community name used by systems management applications must match an SNMP community name configured on the Server Administrator software system, so the systems management applications can retrieve management information from Server Administrator.
To enable SNMP Set operations on the system running Server Administrator, edit the /etc/snmp/snmpd.conf SNMP agent configuration file and perform the following steps: 1 Find the line that reads: access publicgroup "" any noauth exact all none none or access notConfigGroup "" any noauth exact all none none 2 Edit this line, replacing the first none with all.
Firewall Configuration on Systems Running Supported Red Hat Enterprise Linux Operating Systems If you enable firewall security when installing Red Hat Enterprise Linux, the SNMP port on all external network interfaces is closed by default. To enable SNMP management applications such as IT Assistant to discover and retrieve information from Server Administrator, the SNMP port on at least one external network interface must be open.
5 Select whether to open an entire network interface or just the SNMP port on all network interfaces. a To open an entire network interface, select one of the Trusted Devices and press the spacebar. An asterisk in the box to the left of the device name indicates that the entire interface will be opened. b To open the SNMP port on all network interfaces, select Other ports and type snmp:udp. 6 Select OK and press . The Firewall Configuration screen appears. 7 Select OK and press .
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. Since the 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.
To enable SNMP access from all remote hosts to a system running Server Administrator, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.conf, and perform the following steps: 1 Find the line that reads: rocommunity public 127.0.0.1 2 Edit this line by removing 127.0.0.1. When edited, the new line should read: rocommunity public 3 To enable SNMP configuration changes, restart the SNMP agent by typing: /etc/init.
Enabling SNMP Set Operations Enable SNMP Set operations on the system running Server Administrator in order to change Server Administrator attributes using IT Assistant. To enable remote shutdown of a system from IT Assistant, enable SNMP Set operations. NOTE: Rebooting your system for change management functionality does not require SNMP Set operations. To enable SNMP Set operations on the system running Server Administrator, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.
Secure Port Server and Security Setup This section contains the following topics: • Setting User and Server Preferences • X.509 Certificate Management Setting User and Server Preferences You can set user and secure port server preferences for Server Administrator and IT Assistant from the respective Preferences Web page. Click General Settings and click either the User tab or Web Server tab. NOTE: You must be logged in with Administrator privileges to set or reset user or server preferences.
• The HTTPS Port field specifies the secure port for Server Administrator. The default secure port for Server Administrator is 1311. NOTE: Changing the port number to an invalid or in-use port number may prevent other applications or browsers from accessing Server Administrator on the managed system. • The IP Address to Bind to field specifies the IP address(es) for the managed system that Server Administrator binds to when starting a session.
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).
Using Unified Server Configurator to Install an Operating System Overview From Dell OpenManage version 6.0.1 onwards, apart from the Dell Systems Build and Update Utility (SBUU), you can also use the Dell™ Unified Server Configurator (USC) to install an operating system. For information on installing an operating system using SBUU, see "Using Systems Build and Update Tools to Install an Operating System".
Updating the Unified Server Configurator You can update to the next version of the USC using the Platform Update wizard. It is recommended that you run the Platform Update wizard on a regular basis to access updates as they become available. For more information on updating the USC, see the Dell Unified Server Configurator User’s Guide. NOTE: In Version 1.0 of the USC, the only available updates are for the USC, diagnostics, and drivers.
6 Insert the OS installation media and click Next. The USC verifies that the installation media is appropriate for the operating system you selected. If the inserted installation media does not match the operating system selection, it will be ejected. 7 Click Finish to reboot the system and continue with the OS installation. Upon reboot, the system boots to the OS installation media.
Using Unified Server Configurator to Install an Operating System
Using Systems Build and Update Tools to Install an Operating System Overview The Dell™ Systems Build and Update Utility provides a streamlined and time-saving installation procedure by guiding you through an easy-to-follow, step-by-step process to install the Microsoft® Windows®, Red Hat® Enterprise Linux®, and SUSE® Linux Enterprise Server operating systems. Systems Build and Update Utility is used to install operating systems for systems being installed as managed systems.
Installing Your Operating System Perform the following steps to determine if an operating system has been installed on your system: 1 Ensure that the keyboard, mouse, and monitor are connected to your system, and turn on your system. 2 Read and accept the software license agreement to continue. If a message stating that bootable drives do not exist or that an operating system was not found appears, then an operating system has not been installed on your system.
Installing Management Station Software Overview The Dell Systems Management Tools and Documentation DVD provides a setup program to install, upgrade, and uninstall Dell™ OpenManage™ management station software on your system. The management station applications include DRAC Tools, the BMC Utilities, the Microsoft Active Directory® Snap-in Utility, and Dell OpenManage IT Assistant.
Management Station Requirements Microsoft Software Installer (MSI) version 3.1 or later is required on your system. Dell OpenManage software detects the MSI version on your system. If the version is lower than 3.1, the Prerequisite Checker prompts you to upgrade to MSI version 3.1. IT Assistant Database Requirements For informationon IT Assistant database requirements, see the Dell OpenManage IT Assistant User’s Guide.
Prerequisite Checker The setup program runs the Prerequisite Checker, which examines the prerequisites for software features without launching the actual installation. The Prerequisite Checker displays a status window that provides information about your system’s hardware and software that might affect the installation and operation of the software features. The Prerequisite Checker displays three types of messages: informational, warning, and error messages.
Typical and Custom Installations The management station installer provides two setup options: Typical Setup and Custom Setup. The setup program runs the Prerequisite Checker and provides information about your system’s hardware and software that might affect installation and operation of features. Perform the following steps to install management station software on your system: 1 Launch the management station installation. 2 Click Install, Modify, Repair or Remove Management Station and click Next.
Installing Management Station On Microsoft Windows operating systems, perform the following steps: NOTE: IT Assistant requires a default instance of a database to be installed on the system. IT Assistant cannot use a named instance of a 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 and .NET 2.
7 Select I accept the terms in the license agreement and click Next. The Setup Type dialog box appears. 8 Select Custom and click Next. The Custom Setup dialog box appears. To select a specific management station software application, click the drop-down arrow beside the listed feature and select to either install or not to install the application. A selected feature has a hard drive icon next to it. A deselected feature has a red X next to it.
Upgrade The Dell OpenManage installer provides an Upgrade option for upgrading IT Assistant and other management station software. When you insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive, select Dell OpenManage Management Station from the autorun menu, and click Install. The Prerequisite Checker program checks your system.
3 Click Next. The Installing Dell OpenManage Management Station screen appears. Messages provide the status and progress of the software features being installed or upgraded. When the selected features are installed or upgraded, the Install Wizard Completed dialog box appears. 4 Click Finish to leave the management station installation. Modify 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Management Station and click Change.
Repair 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Management Station and click Change. The Welcome to the Install Wizard for Dell OpenManage Management Station dialog box appears. 4 Click Next. The Program Maintenance dialog box appears. 5 Select the Repair option and click Next. The Ready to Repair the Program dialog box appears. 6 Click Install to install the selected software features.
An installation cannot be rolled back once it has successfully completed. A transacted installation is intended as a safety net that protects the system during a given installation session. If you want to remove an installed application, for example, you should uninstall that application. When upgrading from Dell OpenManage software version 4.3 to version 5.x, an error will roll back the system to its previous state.
Creating and Distributing the Typical Unattended Installation Package The Typical Setup unattended installation option uses the Dell Systems Management Tools and Documentation DVD as the unattended installation package. The msiexec.exe /i MgmtSt.msi /qb command accesses the DVD to accept the software license agreement and install all required management station software products on selected remote systems. The msiexec.exe /i MgmtSt.
3 Configure your ISV distribution software to distribute and execute the script created in step 2. 4 Distribute this script to the target systems by using your ISV software distribution tools. The msiexec.exe /i MgmtSt.msi /qb command installs management station on each remote system. NOTE: IT Assistant requires a supported database to be installed before IT Assistant can be installed. See DVD drive:\SYSMGMT\ManagementStation\Windows\ManagementStat ion\support\ to find the sample batch file and the necessar
Also, put the batch script in the windows directory on the system hard drive. See “Customization Parameters” for additional details and available feature identification. 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 SYSMGMT\ManagementStation\windows\ManagementStation on the Dell Systems Management Tools and Documentation DVD.
Table 6-1. Command Line Settings for MSI Installer Setting Result Installs or configures a product. /i management station software. Uninstalls a product. /x management station software. /q[n|b|r|f] Sets the User Interface (UI) level. /q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI.
Table 6-1. Setting Command Line Settings for MSI Installer (continued) Result /f[p|o|e|d|c|a| Repairs a product. u|m|s|v] /fp – This option reinstalls a product only if a file is /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.
Uninstalling Management Station Software You can uninstall the management station software by using your operating system. Additionally, you can perform unattended uninstallations on multiple systems. Uninstall Management Station Software Using the Dell-provided Media To uninstall the management station software using the DVD, perform the following steps: 1 Insert the DVD into your system's DVD drive. Navigate to the SYSMGMT\ManagementStation\windows directory on the DVD and double-click the setup.
Uninstalling Management Station Software Features Using Add/Remove Programs To uninstall the management station software features using Windows, perform the following steps: 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Management Station and click Remove. The Add or Remove Programs question box appears. 4 Click Yes to confirm uninstallation of management station. The Uninstall Summary screen appears.
Unattended Uninstall Command Line Settings Table 6-1 shows the unattended uninstallation command line settings available for unattended uninstallation. Type the optional settings on the command line after msiexec.exe /x MgmtSt.msi with a space between each setting. For example, running msiexec.exe /x MgmtSt.msi /qb runs the unattended uninstallation and displays the unattended installation status while it is running. Running msiexec.exe /x MgmtSt.
Table 6-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.
You can also choose to install, reinstall, and uninstall features with one execution of the msiexec.exe program. An example is msiexec.exe /i MgmtSt.msi ADDLOCAL=ADS REINSTALL= RACMS REMOVE=BMC /qb This command runs the installation for management station and simultaneously installs Active Directory Snap-in Utility, reinstalls Remote Access Controller management station, and uninstalls the Baseboard Management Controller utility. This execution will be in an unattended and verbose mode.
Other Known Issues for Microsoft Installations • Directories might be left behind during an uninstall for reasons such as sharing violations or open user interface connections. It is recommended that you close all open interface sessions before you perform an uninstallation. Manually remove directories left behind in the default installation directory or the user-specified installation directory. You might also have to manually remove the registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Dell Computer Cor
3 Navigate to the SYSMGMT/ManagementStation/linux/bmc directory and install the BMC software using the rpm commands specific to the operating system: • For systems running Red Hat Enterprise Linux, use osabmcutil*RHEL-*.rpm, for example, rpm -ivh osabmcutil*-RHEL*.rpm. • For systems running SUSE Linux Enterprise Server, use osabmcutil*-SUSE-*.rpm, for example, rpm -ivh osabmcutil*-SUSE-*.rpm.
3 Navigate to the SYSMGMT/ManagementStation/linux/bmc directory and upgrade the BMC software using the rpm commands specific to the operating system: • For systems running Red Hat Enterprise Linux, use osabmcutil*RHEL-*.rpm, for example, rpm -Uvh osabmcutil*-RHEL*.rpm. • For systems running SUSE Linux Enterprise Server, use osabmcutil*-SUSE-*.rpm, for example, rpm -Uvh osabmcutil*-SUSE-*.rpm.
To uninstall the DRAC Tools feature, perform the following steps: 1 Log on as root to the system where you want to install the management station features. 2 Use the rpm query command to determine which version of the DRAC Tools is installed. Use the rpm -qa | grep mgmtst-racadm command. 3 Verify the package version to be uninstalled and uninstall the feature by using the rpm -e `rpm -qa | grep mgmtst-racadm` command.
Installing Managed System Software on Microsoft Windows Operating Systems Overview The Dell Systems Management Tools and Documentation DVD provides a setup program to install and uninstall managed system software components on your managed systems. You can install these software components on multiple systems through an unattended installation across a network.
Unattended and Scripted Silent Installation You can use the Dell Systems Management Tools and Documentation DVD to perform an unattended and scripted silent installation of the managed system software on systems running supported Windows operating systems. Additionally, you can install and uninstall the features from the command line on systems running supported Windows operating systems.
NOTE: When Multilingual User Interface (MUI) is set to non-Unicode languages like Simplified Chinese or Japanese, set the system locale to Simplified Chinese or Japanese. This enables the Prerequisite Checker messages to be displayed. This is because any non-Unicode application will run only when the system locale (also called Language for non-Unicode Programs on XP) is set to match the application's language.
NOTE: The RAC software is installed as part of the Typical Setup and Custom Setup installation options when installing managed system software from the Dell Systems Management Tools and Documentation DVD, provided that the managed system meets all of the RAC installation prerequisites. See "Remote Access Controller Service" and the Dell Remote Access Controller Installation and Setup Guide or the Dell Embedded Remote Access/MC Controller User's Guide for complete software and hardware requirements.
When you launch Server Administrator, it first determines if the Windows Server 2003 R2 IPMI driver is enabled. If the driver is enabled, Server Administrator uses the Windows Server 2003 R2 IPMI driver to provide its IPMI-based functionality. If the Windows Server 2003 R2 IPMI driver is not enabled, Server Administrator uses its own internal IPMI support to provide its IPMI-based functionality.
Installation Procedures This section explains how to install and uninstall Server Administrator on a system that is running a supported Windows operating system. Prerequisites for Installing Server Administrator You must have Administrator privileges. If you want to use supporting agents for the Simple Network Management Protocol (SNMP), you must install the operating system support for the SNMP standard before or after you install Server Administrator.
install the software using the Custom installation. For example, if an Intel network interface card (NIC) is not detected on the system, you will see the following message: An Intel(R) NIC was not detected on this system. This will disable the "Typical" installation of the Intel(R) SNMP Agent. Use the "Custom" installation setup type later during installation to select this feature if you have an Intel(R) NIC installed.
NOTE: During installation of Server Administrator on supported Windows systems, if an Out of Memory error message displays, you must exit the installation and free up memory. Close other applications or perform any other task that will free up memory, before re-attempting Server Administrator installation. Typical and Custom Installations The Dell OpenManage installer features a Typical Setup option and a Custom Setup option for installing Server Administrator and other managed system software.
Custom Installation The sections that follow show how to install 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 on which you want to install the system management software. 2 Close all open applications and disable any virus-scanning software.
A selected feature has a hard drive icon depicted next to it. A deselected feature has a red X depicted next to it. By default, if the Prerequisite Checker finds a software feature with no supporting hardware, the checker deselects them. To accept the default directory path to install managed system software, click Next. Otherwise, click Change and navigate to the directory where you want to install your managed system software, and click OK. You will return to the Custom Setup dialog box.
Option 1: 1 Uninstall Server Administrator. 2 Install Citrix. 3 Reinstall Server Administrator. Option 2: After installing Citrix, type the following command: msiexec.exe /fa SysMgmt.msi Modify 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Server Administrator and click Change. The Welcome to the Install Wizard for Dell OpenManage Server Administrator dialog box appears. 4 Click Next. The Program Maintenance dialog box appears.
When the selected features are installed, the Install Wizard Completed dialog box appears. 9 Click Finish to exit the Server Administrator installation. If you are prompted to reboot your system, you must do so to make the installed managed system software services available for use. If you are prompted to reboot your system, select a reboot option: • Yes, reboot my system now. • No, I will reboot my system later. Repair 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs.
System Recovery on Failed Installation The Microsoft Software Installer (MSI) provides the ability to return a system to its fully working condition after a failed installation. MSI does this by maintaining an undo operation for every Standard Action it performs during an install, upgrade, or uninstall. This operation includes restoration of deleted or overwritten files, registry keys, and other resources.
structure and GUIDs, which break any provided patches or updates. When it is necessary to make any changes to a vendor-provided MSI package, a .mst transform file should always be used to do so. Windows Installer Logging Windows includes a registry-activated logging service to help diagnose Windows Installer issues. To enable this logging service during a silent install, open the registry editor and create the following path and keys: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Window s\Installer Reg_SZ
These particular log files are created by default if the Prerequisite Checker user interface (UI) is running. Performing an Unattended Installation of Managed System Software The Dell OpenManage installer features a Typical Setup option and a Custom Setup option for the unattended installation procedure. Unattended installation enables you simultaneously to install Server Administrator on multiple systems.
You can accomplish this task by directly sharing the DVD or by copying the entire DVD 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. This script should execute msiexec.exe /i Mapped Drive\SYSMGMT\srvadmin\windows\ SystemsManagement\SysMgmt.msi /qb after the drive has been mapped. 3 Configure your ISV distribution software to distribute and execute the script created in step 2.
An example is msiexec.exe /i SysMgmt.msi ADDLOCAL= SA,IWS,BRCM /qb. (See "Customization Parameters" for more details and available feature identifications.) 3 Place the batch script in the windows directory on the system hard drive. Distributing Custom Unattended Installation Packages NOTE: The SysMgmt.msi installation package for Server Administrator used in the Custom Setup unattended installation (see "Creating and Distributing Custom Unattended Installation Packages") is located in the SYSMGMT\srvadmin
Optional Command Line Settings Table 7-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 7-1. Command Line Settings for MSI Installer Setting Result This command installs or configures a product. /i
Table 7-1. Setting Command Line Settings for MSI Installer (continued) Result /f[p|o|e|d|c|a|u This command repairs a product. |m|s|v] 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.
Customization Parameters NOTE: Type the ADDLOCAL, REINSTALL, and REMOVE CLI parameters in upper case, as they are case-sensitive. ADDLOCAL, REINSTALL, and REMOVE customization CLI parameters provide a way to customize the exact software features to install, reinstall, or uninstall when running silently or unattended. With the customization parameters, you can selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package.
This command runs the installation for Dell OpenManage Systems Management, and installs only the Broadcom agent, in an unattended but not silent mode. You can include the REINSTALL customization parameter on the command line and assign the feature ID (or IDs) of the software feature that you would like to reinstall. An example is msiexec.exe /i SysMgmt.msi REINSTALL=BRCM /qb.
MSI Return Code An application event log entry is recorded in the SysMgmt.log file. Table 7-3 shows some of the error codes returned by the msiexec.exe Windows Installer Engine. Table 7-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.
Uninstalling Managed System Software Using Dell-provided Media 1 Insert the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. If the setup program does not start automatically, run the setup.exe in the SYSMGMT\srvadmin\windows directory on the DVD. The Dell OpenManage Server Administrator prerequisite status screen appears and runs the prerequisite checks for the managed system. Any relevant informational, warning, or error messages detected during checking are displayed.
Uninstalling Managed System Software Features Using the Operating System 1 Navigate to the Windows Control Panel. 2 Double-click Add/Remove Programs. 3 Click Dell OpenManage Server Administrator and click Remove. The Add or Remove Programs dialog box appears. 4 Click Yes to confirm uninstallation of Server Administrator. The Dell OpenManage Server Administrator screen appears and provides the status and progress of the software features being uninstalled.
Distributing the Unattended Uninstallation Package The Dell Systems Management Tools and Documentation DVD is pre-configured to act as the unattended uninstallation package. To distribute the package to one or more systems, perform the following steps: 1 Configure your ISV distribution software to execute the msiexec.exe /x DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb command, if you are using the DVD, after the unattended uninstallation package has been distributed.
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 at SYSMGMT\srvadmin\support\Altiris on the Dell Systems Management Tools and Documentation DVD. Specify a job folder into which to import OpenManage_Jobs.bin.
Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server Introduction The Server Core installation option of the Microsoft® Windows Server® 2008 and Hyper-V™ Server operating system provides a minimal environment for running specific server roles that reduces the maintenance and management requirements and the attack surface for those server roles.
Installing Managed System and Management Station Software This section provides instructions on installing managed system and management station software on Windows Server 2008 Core or Hyper-V Server operating system, in the CLI mode. Running PreReqChecker In CLI Mode Run the PreReqChecker before you install Dell OpenManage software. See "Prerequisite Checker" for more information on running Prerequisite Checker in the CLI mode.
NOTE: If you encounter a return value of 2 or 3, it is recommended that you inspect the omprereq.htm file in the windows temporary folder %TEMP%. To find %TEMP%, run the echo %TEMP% command. NOTE: omprereq.htm is an html file. Transfer this file to another computer with a browser installed to read this file. Common causes for a return value of 2 from the prerequisite checker: • One of your storage controllers or drivers has outdated firmware or driver. See firmwaredriverversions_.
• Running managed system prereqchecker on the Windows Vista® operating system. Vista is not supported for managed system software. • Running the x64 edition of Windows 2008 Core, since some of the components are disabled from being installed. Ensure that any error or warning situation is corrected before you proceed to install OpenManage software components.
Installing Managed System Software In CLI Mode 1 Ensure that all errors or warnings that PreReqChecker detects are corrected before you install managed system components. 2 Launch the MSI file from the command prompt using the command msiexec /i SysMgmt.msi The MSI file SysMgmt.msi is located at SYSMGMT\srvadmin\windows\SystemsManagement on the Dell Systems Management Tools and Documentation DVD. To install the localized version of the managed system software, type msiexec /I SysMgmt.
Installing Dell OpenManage Software On Windows Server 2008
Installing Managed System Software on Supported Linux Operating Systems Overview The Dell™ OpenManage™ installer provides installation scripts and RPM packages to install and uninstall Dell OpenManage Server Administrator and other managed system software components on your managed system. Additionally, you can install Server Administrator on multiple systems through an unattended installation across a network. The first installation method uses the custom install script srvadmin-install.sh.
Unattended and Scripted Silent Installation You can use the Dell Systems Management Tools and Documentation DVD to perform an unattended and scripted silent installation of managed systems software through the command line (using RPM packages) on systems running supported Red Hat® Enterprise Linux® and SUSE® Linux Enterprise Server operating systems. Before You Begin • Read the installation requirements to ensure that your system meets or exceeds the minimum requirements.
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 512 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 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. You can install Server Administrator using scripts from the Dell Systems Management Tools and Documentation DVD, or through RPM.
If you see the following message during Server Administrator Device Drivers startup, then Server Administrator has attempted to use its DKS feature, but was unable to use the feature because certain prerequisites were not met: Building using DKS... [FAILED] where is dcdbas or dell_rbu NOTE: Server Administrator logs messages to the /var/log/messages log file. To use DKS, identify which kernel is running on the managed system, and check the DKS prerequisites.
Using Dynamic Kernel Support After Server Administrator Installation To enable Server Administrator to support a kernel that is not supported by a precompiled device driver and is loaded after Server Administrator has been installed, perform the following steps: Ensure that the DKS prerequisites are met on the system to be managed and boot the new kernel on the system.
4 Copy any dcdbas.* or dell_rbu.* files in the /lib/modules//kernel/drivers/firmware directory on system A to the /var/omsa/dks/ directory on system B, where is the kernel name returned by typing uname -r in step 3. NOTE: The /lib/modules//kernel/drivers/firmware directory may contain one or more of the following files: dcdbas.* or dell_rbu.* NOTE: You might have to create the /var/omsa/dks/ directory on system B. For example, if the kernel name is 1.2.
Determining if the Running Kernel is Tainted After Server Administrator services have been started, perform the following steps on Red Hat Enterprise Linux Update releases to determine if the kernel has been tainted: 1 Log in as root.
This requirement is checked and enforced by Server Administrator at three instances. Two of the instances are during installation, while the third is a run-time step. The instances are: • During custom installation of Server Administrator using the srvadmin-install.sh shell script. • During installation of Server Administrator using RPM. • At run-time when the Server Administrator Instrumentation Service is started.
During installation of Server Administrator using RPM, the srvadmin-hapi RPM will check if a sufficient version of the OpenIPMI device driver is currently installed on the system. If a sufficient version is not found, the srvadmin-hapi RPM will fail to install and will display an error message stating that you must install/upgrade the OpenIPMI device driver. In such a case, RPMs that depend on the srvadmin-hapi RPM will also fail to install.
Additionally, during the installation of the srvadmin-hapi RPM using RPM, if a required version of the OpenIPMI RPM is currently installed on the system, but OpenIPMI driver modules have not been built and installed for the given version of the OpenIPMI driver (because the kernel-source RPM is required but is not currently installed,) the srvadmin-hapi RPM will fail to install and will display an error message.
To account for a user uninstalling or replacing a sufficient version of the OpenIPMI device driver after Server Administrator has been installed, the Server Administrator Instrumentation Service checks the OpenIPMI device driver version whenever it is started. If a sufficient version of the OpenIPMI device driver is not found, the Server Administrator Instrumentation Service will degrade itself so that it does not provide any of its IPMI-based information or functionality.
Prerequisites for Installing Managed System Software • You must be logged in as root. • The running kernel must have loadable module support enabled. • The /opt directory must have at least 250 MB of free space, and the /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.
SYSMGMT/srvadmin/linux/RPMS/supportRPMS/ to locate the appropriate RPM files for your Linux operating system. Install applicable RPMs with rpm -ivh before installing managed system software. Installing Managed System Software Using Dell-Provided Media The Dell OpenManage installer uses RPMs to install each component. The media (DVD) is divided into subdirectories to enable easy Custom Installs.
1 Log on as root to the system running the supported Red Hat Enterprise Linux or SUSE Linux Enterprise Server operating system where you want to install the managed system components. 2 Insert the Dell Systems Management Tools and Documentation DVD into the DVD drive. 3 If necessary, use the command line to mount the DVD using a command such as: mount /dev/dvdrom /mnt/dvdrom 4 Navigate to the SYSMGMT/srvadmin/linux/supportscripts if you are using the DVD. 5 Run the srvadmin-install.
Using Pre-configured Custom Directories to Perform the Custom installation See Table 9-1 for details about using the RPMs to perform a custom installation using pre-configured custom directories. Table 9-1.
The following is an example of custom RPMs-based installation of Server Administrator, including the installation of the Storage Management Service components. NOTE: On the Red Hat Enterprise Linux 5 operating system, DVDs are auto-mounted with the -noexec mount option. This option does not allow you to run any executable from the DVD. You need to manually mount the DVD and then run executables.
The options are: [-x|--express] installs all components including RAC. Any other options passed will be ignored. [-b|--base] installs Base components. [-s|--storage] installs Storage components, including Base. [-r|--rac] installs applicable RAC components, including Base. [-w|--web] installs Web Server components, including Base. [-u|--update] updates applicable components in upgrade of prior versions (same as -x for upgrade). [-h|--help] displays help text.
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.
5 Execute the script with the sh srvadmin-install.sh command, which displays a list of component options. If any of the components are already installed, then those components are listed separately with a check mark next to them. The Server Administrator custom installation options are displayed. 6 Press to copy, to install, to reset and start over, or to quit. • If you press , you are prompted to enter the absolute destination path.
The unattended installation package is distributed to the remote systems using a software distribution tool from an ISV. After the package is distributed, RPM installs the software. The custom unattended installation package is located in the directory you created as detailed in the section "Using the Shell Script to Perform the Custom Installation in Interactive Mode." This directory contains all the RPMs for the managed system software components for distribution.
Distributing the Express-Install subdirectory as the Express Unattended Installation Package 1 Distribute the SYSMGMT/srvadmin/linux/supportscripts and the SYSMGMT/srvadmin/linux/RPMS subdirectories of the Dell Systems Management Tools and Documentation DVD. 2 Configure your ISV software distribution software to execute sh srvadmin-install.sh -x from the supportscripts subdirectory. When the ISV software runs, it executes the RPMs to install Server Administrator on each remote system.
Distributing Unattended Installation Packages The custom unattended installation package is located in the directory you created in the preceding step 6 of the custom installation (see "Custom Install"). This directory contains all of the RPMs for the managed system software components to distribute. 1 Configure your ISV software distribution software to execute rpm –i *.rpm after the unattended installation package has been distributed.
Using Dell OpenManage with VMware® ESX Server™ Software NOTE: Dell OpenManage installation with VMware ESX Server software requires special steps. These steps vary depending on the Dell OpenManage version and ESX Server version; only a limited number of combinations are supported. See the VMware Systems Compatibility Guide located in the Resource Center at www.dell.com/vmware to determine the versions of ESX Server software compatible with this release of Dell OpenManage.
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 Integrated Dell Remote Access Controllers (iDRAC), Dell Remote Access Controllers (DRAC), can now interface with Active Directory.
Dell extension is: dell Dell base OID is: 1.2.840.113556.1.8000.1280 Dell LinkID range is:12070 to 12079 The Active Directory OID database maintained by Microsoft can be viewed at msdn.microsoft.com/certification/ADAcctInfo.asp by entering our extension, dell. 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.
Figure 10-1. Typical Setup for Active Directory Objects Association Object User(s) Group(s) Privilege Object RAC Privilege Object Server Administrator Privilege Object IT Assistant Privilege Object Dell Product(s) RAC Device Object Server Administrator Application Object IT Assistant Application Object In addition, you can set up Active Directory objects in a single domain or in multiple domains.
Figure 10-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 10-3 shows how to setup the Active Directory objects in multiple domains for RAC. In this scenario, you have two DRAC 4 cards (RAC1 and RAC2) and three existing Active Directory users (User1, User2, and User3). User1 is in Domain1, but User2 and User3 are in Domain2. You want to give User1 and User2 Administrator privileges on both the RAC1 and the RAC2 card and give User3 a Login privilege on the RAC2 card. Figure 10-3.
5 Group User1 and User2 into Group1. The group scope of Group1 must be Universal. 6 Add Group1 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both RAC1 and RAC2 as Products in AO1. 7 Add User3 as Members in Association Object 2 (AO2), Priv2 as Privilege Objects in AO2, and RAC2 as a Product in AO2. 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.
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 and AO2, in any domain. The figure shows the objects in Domain1. 3 Create two Server Administrator Products, sys1 and sys2, to represent the two systems. Sys1 is in Domain1 and sys2 is in Domain2.
Extending the Active Directory Schema RAC, Server Administrator, and IT Assistant schema extensions are available. You only need to extend the schema for software or hardware that you are using. Each extension must be applied individually to receive the benefit of its software-specific settings. Extending your Active Directory schema will add schema classes and attributes, example privileges and association objects, and a Dell organizational unit to the schema.
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 CAUTION: The Dell Schema Extender uses the SchemaExtenderOem.ini file.
Table 10-2. Class Definitions for Classes Added to the Active Directory Schema (continued) Class Name Assigned Object Identification Number Class Type (OID) dellOmsa2AuxClass 1.2.840.113556.1.8000.1280.1.2.1.1 Auxiliary Class dellOmsaApplication 1.2.840.113556.1.8000.1280.1.2.1.2 Structural Class dellIta7AuxClass 1.2.840.113556.1.8000.1280.1.3.1.1 Auxiliary Class dellItaApplication 1.2.840.113556.1.8000.1280.1.3.1.2 Structural Class Table 10-3. dellAssociationObject Class OID 1.2.840.113556.
Table 10-5. dellProduct Class 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. Class Type Structural Class SuperClasses Computer Attributes dellAssociationMembers Table 10-6. 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.
Table 10-8. dellIta7AuxClass Class OID 1.2.840.113556.1.8000.1280.1.3.1.1 Description This class is used to define the privileges (Authorization Rights) for IT Assistant. Class Type Auxiliary Class SuperClasses None Attributes dellItaIsReadOnlyUser dellItaIsReadWriteUser dellItaIsAdminUser Table 10-9. dellItaApplication Class OID 1.2.840.113556.1.8000.1280.1.3.1.2 Description This class represents the IT Assistant application.
Table 10-10. General Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellPrivilegeMember 1.2.840.113556.1.8000.1280.1.1.2.1 FALSE List of dellPrivilege Objects that belong Distinguished Name to this Attribute. (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) dellProductMembers 1.2.840.113556.1.8000.1280.1.1.2.2 FALSE List of dellRacDevices Objects that Distinguished Name belong to this role.
Table 10-12. IT Assistant-Specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellItaIsReadWriteUser 1.2.840.113556.1.8000.1280.1.3.2.1 TRUE TRUE if the User has Read-Write rights in IT Assistant Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) dellItaIsAdminUser 1.2.840.113556.1.8000.1280.1.3.2.2 TRUE if the User has Administrator rights in IT Assistant Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.
Opening the Active Directory Users and Computers Snap-In NOTE: On Windows 2000 Server, you can extend the schema but will not able to install the Dell extension to the snap-in. In order to manage the extended schema on the domain controllers running Windows 2000, perform the following steps: Connecting to a Windows 2000 Server Domain Controller from Another Domain Controller 1 Click Start→ Admin Tools→ Active Directory Users and Computers.
To open the Active Directory Users and Computers snap-in, perform the following steps: 1 If you are on the domain controller, click Start→ Admin Tools→ Active Directory Users and Computers. If you are not on the domain controller, you must have the appropriate Microsoft administrator pack installed on your local system. To install this administrator pack, click Start→ Run, type MMC and press Enter. The Microsoft Management Console (MMC) window appears. 2 Click File in the Console 1 window.
3 Type in a name for the new object. This name must match the Active Directory product name as discussed in "Configuring Active Directory Using CLI on Systems Running Server Administrator", or for a RAC device, the name that you will type in step 4 of "Configuring Your Systems or Devices", or for IT Assistant, the name discussed in "Configuring Active Directory on Systems Running IT Assistant." 4 Select the appropriate Product Object. 5 Click OK.
3 Select a RAC, Server Administrator, or IT Assistant object, depending on which you have installed. The New Object window appears. 4 Type in a name for the new object. 5 Select Association Object. 6 Select the scope for the Association Object. 7 Click OK. Adding Objects to an Association Object By using the Association Object Properties window, you can associate users or user groups, privilege objects, systems, RAC devices, and system or device groups.
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. Configuring Your Systems or Devices For instructions on how to configure your Server Administrator or IT Assistant systems using CLI commands, see "Configuring Active Directory Using CLI on Systems Running Server Administrator" and "Configuring Active Directory on Systems Running IT Assistant.
Table 10-13 shows the valid parameters for the command. Table 10-13. Active Directory Service Configuration Parameters name=value pair Description prodname= Specifies the software product to which you want to apply the Active Directory configuration changes. Prodname refers to the name of the product defined in omprv32.ini. For Server Administrator, it is omsa. enable= true: Enables Active Directory service authentication support.
Prerequisite Checker Command Line Operation of the Prerequisite Checker You can run the prerequisite check silently by executing runprereqchecks.exe /s from the SYSMGMT\ManagementStation\windows\PreReqChecker or SYSMGMT\srvadmin\windows\PreReqChecker directory on the Dell Systems Management Tools and Documentation DVD. 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.
Table 11-1. Return Codes While Running the Prerequisite Check Silently 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 you proceed with the installation of the software.
Table 11-2. Feature IDs for the Management Station Feature ID Description ADS Microsoft Active Directory® Snap-in Utility ITA Dell OpenManage™ IT Assistant BMC Baseboard Management Controller Management Utility RACMS Remote Access Controller Table 11-3.
Prerequisite Checker
Frequently Asked Questions General Where can I find the quick installation instructions? The Quick Installation Guide comes as a small brochure with the DVD kit. Also, you can find the guide on the Dell Support website at support.dell.com and on the Dell Systems Management Tools and Documentation DVD at docs directory. How do I install Dell OpenManage Server Administrator with only the CLI features? By choosing not to install the Server Administrator Web server, you will get CLI features only.
• Locate SysMgmt.msi from the SYSMGMT\srvadmin\windows\SystemsManagement directory and enter the following command at the command prompt to force a reinstall. msiexec /i SysMgmt.msi REINSTALL=ALL REINSTALLMODE=vomus • Select Custom Setup and choose all the features that were originally installed. If you are not sure which features were installed, select all of them and perform the installation.
you must ensure that the DVD layout stays the same. The SysMgmt.msi file must be located in the SYSMGMT \srvadmin\windows\SystemsManagement. For more detailed information, go to http://msdn.microsoft.com and search for: MEDIAPACKAGEPATH Property. What is the best way to use the Prerequisite Checker information? The Prerequisite Checker is available for Windows. See the readme file at SYSMGMT\srvadmin\windows\PreReqChecker\readme.
Can I launch my installation without running the Prerequisite Checker? How do I do that? Yes, you can. For example, you can run the MSI of the managed system software, directly from the SYSMGMT\srvadmin\Windows\SystemsManagement. In general, it is not a good idea to bypass the prerequisite information as there could be important information that you would not know otherwise.
Table 12-1. Dell OpenManage Features Under Windows (continued) Feature Name in Windows Management Station Services IT Assistant DSM IT Assistant Network Monitor DSM IT Assistant Connection Service DSM IT Assistant Common Services Baseboard Management Controller (BMC) DSM BMU SOL Proxy Red Hat® Enterprise Linux® or SUSE® Linux Enterprise Server I manually installed my Red Hat Enterprise Linux 4 - x86_64 operating system and am seeing RPM dependencies when trying to install Server Administrator.
Why is the Prerequisite Checker not available under Red Hat Enterprise Linux and SUSE Linux Enterprise Server? The Prerequisite Checker is built into the omilcore RPM package. The checker uses a combination of RPM dependency checks and Dell hardware checks.
What do the directories under srvadmin/linux/custom/ contain? The following table lists the names of the directories in the SYSMGMT/srvadmin/linux/custom/ directory. Table 12-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 12-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-isvc Server Administrator Instrumentation Service — srvadmin-omilcore, Server Administrator provides a suite of srvadmin-deng, and systems management information for keeping srvadmin-hapi supported systems on your network healthy.
Table 12-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminomhip Server Administrator Instrumentation Service srvadmin-omilcore, Integration Layer — Provides Instrumentation srvadmin-deng, CLI.
Table 12-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required add-RAC4 — Software for remote management of fourth generation Remote Access Controllers. For example: DRAC 4. srvadmin-rac4- Remote Access Card Data Populator — components Remote Access Controller components.
Table 12-3.
Table 12-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description srvadmin-ipmi This RPM is used to address the RPM dependency of srvadmin-hapi package. Other Server Administrator RPMs required openipmi XX.Y.
Table 12-4. Daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server once Server Administrator is started (continued) Daemon Name Name in Red Hat Enterprise Linux and SUSE Linux Enterprise Server racvnc DRAC III virtual network daemon racsrvc DRAC III VNC X server 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.
Frequently Asked Questions
Glossary The following list defines technical terms, abbreviations, and acronyms used in your system documents. attribute 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. beep code A diagnostic message in the form of a pattern of beeps from your system's speaker.
bus An information pathway between the components of a system. Your system contains an expansion bus that allows the microprocessor to communicate with controllers for all the various peripheral devices connected to the system. Your system also contains an address bus and a data bus for communications between the microprocessor and RAM. CA Abbreviation for certification authority. CIM Acronym for Common Information Model, which is a model for describing management information from the DMTF.
device driver A program that allows the operating system or some other program to interface correctly with a peripheral device, such as a printer. Some device drivers—such as network drivers—must be loaded from the config.sys file (with a device= statement) or as memory-resident programs (usually, from the autoexec.bat file). Others—such as video drivers—must load when you start the program for which they were designed.
DRAC III/XT Acronym for Dell Remote Access Controller III/XT. DRAM Acronym for dynamic random-access memory. A system's RAM is usually made up entirely of DRAM chips. Because DRAM chips cannot store an electrical charge indefinitely, your system continually refreshes each DRAM chip in the system. ERA Abbreviation for embedded remote access. ERA/MC Abbreviation for embedded remote access modular computer. See modular system. ERA/O Abbreviation for embedded remote access option.
FAT Acronym for file allocation table. FAT and FAT32 are file systems that are defined as follows: • FAT — The operating system maintains a table to keep track of the status of various segments of disk space used for file storage. • FAT32 — A derivative of the FAT file system. FAT32 supports smaller cluster sizes than FAT, thus providing more efficient space allocation on FAT32 drives.
GPG Abbreviation for GNU Privacy Guard. GUI Acronym for graphical user interface. GUID Acronym for Globally Unique Identifier. h Abbreviation for hexadecimal. A base-16 numbering system, often used in programming to identify addresses in the system's RAM and I/O memory addresses for devices. The sequence of decimal numbers from 0 through 16, for example, is expressed in hexadecimal notation as: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F, 10. In text, hexadecimal numbers are often followed by h.
ICU Abbreviation for ISA Configuration Utility. ID Abbreviation for identification. iDRAC Acronym for Integrated Dell Remote Access Controller IDE Abbreviation for Integrated Drive Electronics. IDE is a computer system interface, used primarily for hard drives and CDs. I/O 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.
IRQ Abbreviation for interrupt request. A signal that data is about to be sent to or received by a peripheral device travels by an IRQ line to the microprocessor. Each peripheral connection must be assigned an IRQ number. For example, the first serial port in your system (COM1) is assigned to IRQ4 by default. Two devices can share the same IRQ assignment, but you cannot operate both devices simultaneously. ISV Abbreviation for independent software vendor.
LDIF Abbreviation for Lightweight Directory Interchange Format. local bus On a system with local-bus expansion capability, certain peripheral devices (such as the video adapter circuitry) can be designed to run much faster than they would with a traditional expansion bus. Some local-bus designs allow peripherals to run at the same speed and with the same width data path as the system's microprocessor. LRA Abbreviation for local response agent.
memory address A specific location, usually expressed as a hexadecimal number, in the system's RAM. MIB Acronym for management information base. The MIB is used to send detailed status or commands from or to an SNMP-managed device. microprocessor 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.
MPEG Acronym for Motion Picture Experts Group. MPEG is a digital video file format. ms Abbreviation for millisecond(s). name 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. NIC Acronym for network interface card. NIS Abbreviation for Network Information Services. NIS is a network naming and administration system for smaller networks.
NTLM Abbreviation for Windows NT LAN Manager. NTLM is the security protocol for the Windows NT operating system. NTLM is now known as Integrated Windows Authentication. OID Abbreviation for object identifier. An implementation-specific integer or pointer that uniquely identifies an object. online access service A service that typically provides access to the Internet, e-mail, bulletin boards, chat rooms, and file libraries. PAM Acronym for Pluggable Authentication Modules.
PCI Abbreviation for Peripheral Component Interconnect. The predominant 32-bit or 64-bit local-bus standard developed by Intel Corporation. PERC Acronym for Expandable RAID controller. peripheral device An internal or external device—such as a printer, a disk drive, or a keyboard— connected to a system. physical memory array The physical memory array is the entire physical memory of a system.
ppm Abbreviation for pages per minute. PPP Abbreviation for Point-to-Point Protocol. 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.
RBAC Abbreviation for role-based access control. read-only file A read-only file is one that you are prohibited from editing or deleting. A file can have read-only status if: • Its read-only attribute is enabled. • It resides on a physically write-protected diskette or on a diskette in a write-protected drive. • It is located on a network in a directory to which the system administrator has assigned read-only rights to you.
RPM Abbreviation for Red Hat® Package Manager. SAN Acronym for storage area network. SAS Acronym for serial attached SCSI. SCA Abbreviation for single connector attachment. schema A collection of class definitions that describes managed objects in a particular environment. A CIM schema is a collection of class definitions used to represent managed objects that are common to every management environment, which is why CIM is called the Common Information Model.
settings Settings are conditions of a manageable object help to determine what happens when a certain value is detected in a component. For example, a user can set the upper critical threshold of a temperature probe to 75 degrees Celsius. If the probe reaches that temperature, the setting results in an alert being sent to the management system so that user intervention can be taken. Some settings, when reached, can trigger a system shutdown or other response that can prevent damage to the system.
SRAM Abbreviation for static random-access memory. Because SRAM chips do not require continual refreshing, they are substantially faster than DRAM chips. SSL Abbreviation for secure socket layer. state Refers to the condition of an object that can have more than one condition. For example, an object may be in the "not ready" state. status Refers to the health or functioning of an object. For example, a temperature probe can have the status normal if the probe is measuring acceptable temperatures.
system board As the main circuit board, the system board usually contains most of your system's integral components, such as the following: • Microprocessor • RAM • Controllers for standard peripheral devices, such as the keyboard • Various ROM chips Frequently used synonyms for system board are motherboard and logic board. system configuration information Data stored in memory that tells a system what hardware is installed and how the system should be configured for operation.
TCP/IP Abbreviation for Transmission Control Protocol/Internet Protocol. A system for transferring information over a computer network containing dissimilar systems, such as systems running Windows and UNIX. termination 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.
time-out A specified period of system inactivity that must occur before an energy conservation feature is activated. tpi Abbreviation for tracks per inch. TSR Abbreviation for terminate-and-stay-resident. A TSR program runs "in the background." Most TSR programs implement a predefined key combination (sometimes referred to as a hot key) that allows you to activate the TSR program's interface while running another program.
USB 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. USB devices can also be connected and disconnected while the system is running. utility A program used to manage system resources —memory, disk drives, or printers. utility partition A bootable partition on the hard drive that provides utilities and diagnostics for your hardware and software.
video adapter The logical circuitry that provides—in combination with the monitor—your system's video capabilities. A video adapter may support more or fewer features than a specific monitor offers. Typically, a video adapter comes with video drivers for displaying popular application programs and operating systems in a variety of video modes. On some systems, a video adapter is integrated into the system board. Also available are many video adapter cards that plug into an expansion-card connector.
virtual memory A method for increasing addressable RAM by using the hard drive. For example, in a system with 16 MB of RAM and 16 MB of virtual memory set up on the hard drive, the operating system would manage the system as though it had 32 MB of physical RAM. virus A self-starting program designed to inconvenience you. Virus programs have been known to corrupt the files stored on a hard drive or to replicate themselves until a computer system or network runs out of memory.
Web server An application that makes Web pages available for viewing by Web browsers using the HTTP protocol. Winbind A program that allows users in a heterogeneous network to log in using workstations that have either UNIX or Windows operating systems. The program makes workstations using UNIX functional in Windows domains, by making Windows appear like UNIX to each UNIX workstation. win.ini file A start-up file for the Windows operating system. When you start Windows, it consults the win.
XMM Abbreviation for extended memory manager, a utility that allows application programs and operating systems to use extended memory in accordance with the XMS. XMS Abbreviation for eXtended Memory Specification. X Window System The graphical user interface used in the Red Hat® Enterprise Linux® and SUSE® Linux Enterprise Server environments. ZIF Acronym for zero insertion force.
Index A ATA, 17 access read-only, 37 write, 37 attribute, 187 authentication, 23, 39, 150 authorization, 150 access control, 37 Active Directory, 23, 37, 39, 44, 46, 150, 155, 162, 167-168 object identifiers, 149 objects, 151 schema, 156 schema extender utility, 156-157 schema extensions, 149 ADDLOCAL, 86, 112 administrator, 37 Administrator Pack, 162 Administrator privileges, 37, 98 agent, 54 SNMP, 46 agents, 16 AGP, 187 alert log, 19 Altiris, 118, 148 ASCII, 187 B Baseboard Management Controller, 15,
certificates Web, 62 certification, 21 Certification Authority, 62 chip, 188 CI/O, 188 CIM, 19, 36, 43, 47, 96 CIM protocol, 88 Citrix, 102 D DAT, 189 data redundancy, 17 dB, 189 DCOM, 25, 28 Dell, 94, 150 Dell base OID, 150 Dell organizational unit, 156 CLI, 19, 39, 112, 173 Dell Remote Access Controller, 151 cm, 188 Dell Support website, 18 command line, 113 dellIta7AuxClass, 160 command line interface, 19, 39 dellItaApplication, 160 Common Information Model, 19, 43, 96 dellOmsaApplication, 159
DRAC III, 20, 178 XT, 20 hot spares, 17 DRAC III/XT, 20 HTTPS, 25, 28-31, 33, 35, 39 HTTP, 25, 29, 31, 33, 35 Dynamic Kernel Support, 128 E I INI file, 105 encryption, 37 inoperable system, 20 ERA, 20 ERA/MC, 20 ERA/O, 20 installation management station, 72, 76 unattended, 78, 80, 107 ESX Server, 148 Instrumentation, 38 express setup, 42, 72 instrumentation service, 178 Extraction Utility, 18 integrated NIC, 15 F Intelligent Platform Management Interface, 15 fault logging, 15 IPMI, 15 s
LDAPS, 32, 34-35 LDIF script file, 156 msiexec.exe, 71, 80-81, 85, 87, 99, 103, 107-108 LinkID, 150 N logs, 17 Net BIOS, 27 network adapters, 14 M managed system, 11-12, 43 management information base, 19, 51 NIC, 15 NMP, 27, 33, 35 notification, 12 management object format, 19 management objects, 19 management station, 11-12, 15, 43, 50, 69, 72, 76 O oem.
Prerequisite Checker, 69, 100, 169, 175 prerequisite status, 73 privilege object, 166 privileges administrator, 98 group, 37 Red Hat Enterprise Linux, 14, 16, 41, 43, 45, 51, 55, 69, 89, 126-127, 147, 177 REINSTALL, 86-87, 112-113 remote access, 12 remote access controller, 42 remote access service, 17 prodname, 168 remote system, 108 product object, 150 REMOVE, 87, 112 protocol systems management, 43 REMOVE CLI, 86 proxy server, 43 repository, 18 restoration, 105 RMC, 24 Q RMCP, 24 Quick Instal
agent configuration file, 54 alerting, 15 community name, 48, 53 net-snmp, 137 packets, 48 port, 55 services, 51 Set operations, 49, 53 traps, 50 ucd-snmp, 137 srvadmin-install, 142 SCSI, 17 secure socket layer, 39 security, 44 security administration, 37 Security Group Type, 165 SEL, 15 sensor status, 15 serial console, 16 socket connection, 39 serial port, 15 SOL, 16 serial-over-LAN proxy, 15 SOL Proxy, 15 server proxy, 43 SSH, 26 Server Administrator, 16, 19, 154, 178 Services, 140, 176 SSL enc
Telnet, 29-30, 32, 34 V test modules, 18 VMware, 148 TFTP, 29, 31, 33-34 VNC, 30, 210 time-out, 23 tools ISV, 108 W training, 21 Web certificates, 62 U Windows Installer Engine, 108 Installer Service, 105 unattended installation, 78, 107 unattended uninstallation, 116 universal groups, 166 update packages, 20 Windows Management Instrumentation, 43, 96 WMI, 43, 47, 96 write access, 37 updates, 18 upgrade, 75 X user, 37 X.
Index
