Dell OpenManage Server Administrator Version 6.
Notes and Cautions 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. ___________________ Information in this document is subject to change without notice. © 2011 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . Dell OpenManage Systems Management Software . . . . . . . . . . . . . . . . . . . . . . . . . 12 Dell Systems Management Tools and Documentation DVD . . . . . . . . . . . . . . . . 12 . . . . . . . . . . . . . 15 Dell Server Updates DVD . Dell Management Console DVD . . . . . . . . . . 15 . . . . . . . . . . . 16 . . . . . . . . . . . .
3 Setup and Administration Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Requirements . . . . . . . . . . . . . . . . Supported Operating Systems and Web Browsers . . . . . . . . . . System Requirements . 25 26 . . . . . 28 . . . . . . . . . . . . . . . . . 29 Viewing Localized Versions of the Web-Based Interface . . . . . . . Configuring the SNMP Agent . . . . . . . . 30 . . . . . . . . . 30 . . . . . . . . . . . . . 30 . . . . . . . . . .
Installing Managed System Software on Microsoft Windows Operating Systems . . . . . . . . . . . . . . . Overview . . . 55 . . . . . . . . . . . . . . . . . . . . . . . . 55 . . . . 55 . . . . . 56 . . . . . . . . . . . 57 . . . . . . . . . . . . . . . . . 57 Unattended and Scripted Silent Installation Installation Procedures Prerequisite Checker Remote Enablement Requirements Installing WinRM . Certificate Authority - Signed/Self-Signed Certificate . . . . . . . . . . . . . . . . . . . . .
Windows Installer Logging . . . . . . . . . . . . . . . Performing an Unattended Installation of Managed System Software . . . . . . . . . . . . . . . 73 Creating and Distributing the Typical Unattended Installation Package . . . . . . . . . . 73 . . . . . . . . . 75 . . . . . . . . . . . 76 Creating and Distributing Custom Unattended Installation Packages Specifying Log File Locations . Unattended Installation Features . . . . . . . . . . 76 . . . . . . . . . . . . . 79 . . . . . . . . .
Installing Managed System Software on Supported Linux Operating Systems . . . . . . . . . . . . . . . Software License Agreement . . 91 . . . . . . . . . . . . . . 93 Server Administrator Device Drivers Dynamic Kernel Support . . . . . . . . . . . 93 . . . . . . . . . . . . . . . . 93 Determining the Running Kernel . . . . . . . . . . Dynamic Kernel Support Prerequisites Using Dynamic Kernel Support After Server Administrator Installation . . . . . . . . . 94 . . . . . . .
Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems . . . . . . . . . . . . . . . . 110 Winbind Configuration for openwsman and sfcb for SUSE Linux Enterprise Server Operating Systems . . . . . . . . . . . . . . . . 111 . . . . . . . . . 112 Workaround for the Libssl Issue Uninstalling Managed System Software . . . . . . . Uninstalling Managed System Software Using the Uninstall Script . . . . . . . . . . . . .
Configuring the SNMP Agent on Systems Running VMware ESXi 4/ESXi 4.1 . . . . . . . . . . . . . . . Configuring Your System to Send Traps to a Management Station Using the vSphere CLI. 9 Using Microsoft Active Directory Controlling Access to Your Network 122 . . . . . 125 . . . . . . . . 133 . . . . . . . . . 134 . . . . . . . . . . . . 139 Adding Users and Privileges to Active Directory . . . . . . . . 140 . . . . . . . . . . Configuring Your Systems or Devices 143 . . . . . . . . . . . .
A Dell OpenManage Linux Installer Packages . . . . . . . . . . . . . . . . . . . . . Index 10 . . . . . 169 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Introduction This guide contains information to help you install Dell OpenManage Server Administrator on managed systems. A managed system has supported instrumentation agents installed that allow the system to be discovered and polled for status through Server Administrator. Server Administrator provides easy-to-use management and administration of local and remote systems through a comprehensive set of integrated management services.
• Dell OpenManage on VMware ESXi • Using Microsoft Active Directory • Prerequisite Checker • Frequently Asked Questions NOTE: If you install management station and managed system software on the same system, install identical software versions to avoid system conflicts.
The following applications comprise the Dell management station software that you can install using the Dell Systems Management Tools and Documentation DVD: • Active Directory Snap-In • BMC Utilities • DRAC Tools For information about installing these applications, see the Dell OpenManage Management Station Software Installation Guide available on the Dell Systems Management Tools and Documentation DVD or at support.dell.com/support/edocs/software/omswrels/index.htm.
Dell OpenManage Server Administrator Functionality Dell OpenManage Server Administrator provides a comprehensive set of integrated management services designed for system administrators to manage systems locally and remotely on a network. Server Administrator is the sole installation on the managed system and is accessible both locally and remotely from the Server Administrator Home page. Remotely monitored systems may be accessed by dial-in, LAN, or wireless connections.
Dell Server Updates DVD The Dell Server Updates DVD is a part of the Dell OpenManage subscription service kit along with the Dell Systems Management Tools and Documentation DVD. The Dell Server Updates DVD is available only to those customers who have subscribed to the subscription service. The Dell Server Updates DVD contains Dell Update Packages (DUPs) and Dell OpenManage Server Update Utility (SUU).
Other Documents You Might Need In addition to this guide, you can access the following guides available on the Dell Systems Management Tools and Documentation DVD or at support.dell.com/manuals. On the Manuals page, click Software Systems Management. Click on the appropriate product link on the right-side to access the documents. 16 • The Dell Unified Server Configurator User’s Guide provides information on using Unified Server Configurator.
• The Dell OpenManage Server Administrator Messages Reference Guide lists the messages that are displayed in the Server Administrator home page Alert log, or on your operating system’s event viewer. This guide explains the text, severity, and cause of each alert message that Server Administrator issues.
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. Additionally, Dell Enterprise Training and Certification is available; see www.dell.com/training for more information. This service might not be offered in all locations.
Dell OpenManage Security 2 Security Features 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.
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.
Server Administrator grants read-only access to users logged in with User privileges; read and write access to users logged in with Power User privileges; and read, write, and administrator access to users logged in with Administrator privileges. See Table 2-1. Table 2-1. 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.
Table 2-3 defines the user privilege level abbreviations used in Table 2-2. Table 2-3. Legend for Server Administrator User Privilege Levels U User P Power User A Administrator 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.
Encryption Access to Server Administrator is enabled over a secure HTTPS connection using secure socket layer (SSL) technology to ensure and protect the identity of the system being managed. Java Secure Socket Extension (JSSE) is used by supported Windows, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server operating systems to protect the user credentials and other sensitive data that is transmitted over the socket connection when a user accesses the Server Administrator.
Dell OpenManage Security
Setup and Administration 3 Before You Begin • Read the Installation Requirements to ensure that your system meets or exceeds the minimum requirements. • Read the applicable Dell OpenManage readme files and the Dell Systems Software Support Matrix located at support.dell.com/support/edocs/software/omswrels/index.htm. These files contain the latest information about software, firmware, and driver versions, in addition to information about known issues.
NOTE: The Dell OpenManage installer offers Multilingual User Interface support on Microsoft Windows Storage Server 2003 R2, Microsoft Windows Storage Server 2003 R2, Express x64 Edition with Unified Storage, Microsoft Windows Storage Server 2003 R2, Workgroup x64 Edition with Unified Storage, and Windows Server 2008 (x86 and x64) R2 operating systems.
• The Server Administrator Remote Access Controller service requires that a remote access controller (RAC) be installed on the system to be managed. See the relevant Dell Remote Access Controller User’s Guide for complete software and hardware requirements NOTE: The RAC software is installed as part of the Typical Setup installation option, when installing managed system software, provided that the managed system meets all of the RAC installation prerequisites.
Table 3-1 shows the availability of the systems management standards for each supported operating system. Table 3-1. Availability of Systems Management Protocol by Operating Systems Operating System SNMP CIM/WMI Supported Microsoft Windows operating systems. Available from the operating system installation media. Always installed Supported Red Hat Install the SNMP package provided Enterprise Linux operating with the operating system. systems. Available.
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.
Configuring a Supported Web Browser For a list of supported Web browsers, see "Supported Operating Systems and Web Browsers." NOTE: Ensure that the Web browser is configured to bypass the proxy server for local addresses. 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.
the appropriate section below for your operating system. For additional guidelines, 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.
To enable a system running the Windows Server 2003 operating system to receive SNMP packets from a remote host, perform the following steps: 1 Open the Computer Management window. 2 Expand the Computer Management icon in the window, if necessary. 3 Expand the Services and Applications icon and click Services. 4 Scroll down the list of services until you find SNMP Service, right-click SNMP Service, and then click Properties. The SNMP Service Properties window appears. 5 Click the Security tab.
c To change a community name, select a community name in the Accepted Community Names list and click Edit. The SNMP Service Configuration window appears. d Edit the community name of the management station in the Community Name text box, and click OK. The SNMP Service Properties window appears. 6 Click OK to save the changes. Enabling SNMP Set Operations Enable SNMP Set operations on the system running Dell OpenManage software, to change Dell OpenManage software attributes using IT Assistant.
Administrator SNMP Configuration page under Preferences or the Server Administrator command line interface (CLI) to enable or disable SNMP Set Operations. For more information on enabling or disabling SNMP Set operations in Server Administrator, see the Dell OpenManage Server Administrator User’s Guide or the Dell OpenManage Server Administrator Command Line Interface User's Guide.
Configuring the SNMP Agent on Systems Running Supported Red Hat Enterprise Linux Operating Systems Server Administrator uses the SNMP services provided by the ucd-snmp or net-snmp agent. You can configure the SNMP agent to change the community name, enable Set operations, and send traps to a management station. To configure your SNMP agent for proper interaction with management applications such as IT Assistant, perform the procedures described in the following sections.
The second change is to modify the default access line to give read-only access to the entire MIB tree for the public community. Server Administrator looks for the following line: access notConfigGroup "" any noauth exact systemview none none If Server Administrator encounters this line, it modifies the line as follows: access notConfigGroup "" any noauth exact all none none These changes to the default SNMP agent configuration give read-only access to the entire MIB tree for the public community.
To change the SNMP community name used for retrieving management information from a system running Server Administrator, edit the SNMP agent configuration file, /etc/snmp/snmpd.conf, and perform the following steps: 1 Find the line that reads: com2sec publicsec default public or com2sec notConfigUser default public 2 Edit this line, replacing public with the new SNMP community name.
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.
To configure your system running Server Administrator to send traps to a management station, edit the /etc/snmp/snmpd.
3 Select the Security Level. The selected Security Level is indicated by an asterisk. NOTE: Press for more information about the firewall security levels. The default SNMP port number is 161. If you are using the X Windows GUI, pressing may not provide information about firewall security levels on newer versions of the Red Hat Enterprise Linux operating system. a To disable the firewall, select No firewall or Disabled and go to step 7.
NOTE: On SUSE Linux Enterprise Server (version 10), the SNMP agent configuration file is located at /etc/snmp/snmpd.conf. NOTE: See your operating system documentation for additional details about SNMP configuration. 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.
To enable SNMP access from a specific remote host 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 or copy this line, replacing 127.0.0.1 with the remote host IP address.
To change the default SNMP community name used for retrieving management information from 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 replacing public with the new SNMP community name. When edited, the new line should read: rocommunity community_name 127.0.0.
Configuring Your System to Send Traps to a Management Station Server Administrator generates SNMP traps in response to changes in the status of sensors and other monitored parameters. One or more trap destinations must be configured on the system running Server Administrator for SNMP traps to be sent to a management station. To configure your system running Server Administrator to send traps to a management station, edit the SNMP agent configuration file, /etc/snmpd.conf or /etc/snmp/snmpd.
3 To add a preselected e-mail recipient, type the e-mail address of your designated service contact in the Mail To: field, and click Apply Changes. NOTE: Clicking Email in any window sends an e-mail message with an attached HTML file of the window to the designated e-mail address. 4 To change the home page appearance, select an alternative value in the skin or scheme fields and click Apply Changes.
• The SMTP Server name and DNS Suffix for SMTP Server fields specify your organization's Simple Mail Transfer Protocol (SMTP) and domain name server (DNS) suffix. To enable Server Administrator to send e-mails, you must type the IP address and DNS suffix for the SMTP server for your organization in the appropriate fields. NOTE: For security reasons, your organization might not allow e-mails to be sent through the SMTP server to outside accounts.
Best Practices for X.509 Certificate Management To ensure that the security of your system is not compromised while using server administrator, you should keep in mind the following: • Unique host name - All systems that have server administrator installed should have unique host names. • Change 'localhost' to unique - All systems with host name set to 'localhost' should be changed to a unique host name.
Setup and Administration
4 Deployment Scenarios for Server Administrator You can install Dell OpenManage Server Administrator in the following ways: • Install the Server Administrator Web Server on any system (Dell PowerEdge system, laptop, or desktop) and the Server Instrumentation on another supported Dell PowerEdge system In this method, the Server Administrator Web Server performs the function of a central Web Server and you can use it to monitor a number of managed systems.
Table 4-1. Deployment Scenarios (continued) You want to Select View the status of local and remote storage attached to a managed system and obtain storage management information in an integrated graphical view. Storage Management. Remotely access an inoperable system, receive alert notifications when a system is down, and remotely restart a system. Remote Access Controller.
Table 4-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed NOTE: If you want to remotely manage multiple systems running on Windows and Linux operating systems, it is recommended that you install the Server Administrator Web Sever on a Windows operating system. Server Server Instrumentation Administrator CLI + Instrumentation Service Install Server Instrumentation to use your system as the managed system.
Table 4-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Storage Management Server Administrator Storage Management Install the Storage Management to implement hardware RAID solutions and configure the storage components attached to your system. For more information on the Storage Management, see the Dell OpenManage Server Administrator Storage Management User’s Guide in the docs directory or on support.dell.
Table 4-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Remote Access Controller Server Administrator CLI + Instrumentation Service + iDRAC or DRAC 5, or DRAC 4 (depending on the type of your Dell PowerEdge system) Install Remote Access Service to receive e-mail alerts for warnings or errors related to voltages, temperatures, and fan speeds.
Table 4-2. Managed System Software Components (continued) Component What is Installed Deployment Scenario Systems on Which to be Installed Broadcom SNMP Agent Broadcom SNMP Agent Install this SNMP agent to enable Server Administrator to obtain information about NICs. This SNMP agent helps identify the NICs. Only on Dell PowerEdge systems on which Server Instrumentation is installed and which are running on the Microsoft Windows operating system.
Installing Managed System Software on Microsoft Windows Operating Systems 5 Overview This section contains the procedure to install managed system software on systems running Microsoft Windows operating systems. On Microsoft Windows operating systems, an autorun utility appears when you insert the Dell Systems Management Tools and Documentation DVD. This utility allows you to choose the systems management software you want to install on your system.
Installation Procedures Prerequisite Checker NOTE: 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. For more information about installing SNMP, see the installation instructions for the operating system you are running on your system. The setup program (located at \SYSMGMT\srvadmin\windows) starts the Prerequisite Checker program.
An error message describes a condition that prevents the software feature from being installed. You must resolve the condition causing the error before proceeding with the installation of the software feature. If you do not resolve the issue, the software feature is not installed. Use the RunPreReqChecks.exe /s command (at \SYSMGMT\srvadmin\windows\PreReqChecker) to run the prerequisite check silently. For more information, see "Prerequisite Checker.
Using a Certificate Signed by the CA 1 Requesting a Valid CA Signed Certificate 2 Creating the HTTPS Listener With the Valid CA Signed Certificate Requesting a Valid CA Signed Certificate 1 Click Start Run. 2 Type mmc and click OK. 3 Click File Add/Remove Snap-in. 4 Select the certificate and shift it to the right side. 5 In the new dialog box, select Computer Account, click Next, and then click Finish. 6 Click OK. 7 Expand Certificates from the newly-added tree.
Creating a Certificate 1 Download IIS Resource Kit from microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73b628-ade629c89499&displaylang. 2 Run iis60rkt.exe. 3 Click Next. 4 Select I Agree in the End-User License Agreement screen and click Next. 5 Click Next. 6 In the Select Type screen, select Custom and click Next. 7 Click Next. 8 In the Select Features screen, select SelfSSL 1.0 and click Next. 9 Click Next. 10 Click Finish. The SelfSSl is installed.
7 Select Local Computer and click Finish. 8 Click Close. 9 Click OK. 10 In the Console screen, expand Certificates (Local Computer) in the left navigation pane. 11 Expand Personal. 12 Select Certificates. 13 In the right-hand pane, double-click the required certificate. The Certificate screen displays. 14 Click Details tab. 15 Select Thumbprint. Copy the thumbprint to the clipboard. You can use this parameter while creating the HTTPS listener. 16 Click OK.
Configuring User Authorization for WinRM and WMI Servers To provide access rights to WinRM and WMI services, users must be explicitly added with the appropriate access levels. NOTE: To configure user authorization - For WinRM and WMI Servers, you must login with administrator privileges . - For Windows Server 2008 operating system flavours, you must login with built-in administrator privileges NOTE: The administrator is configured by default. WinRM: 1 Click Start and click Run.
7 Click Add and add the required users or groups (local/domain) to the list. 8 Provide the appropriate permission(s) to the respective users and click OK. 9 Click OK. 10 Close the Windows Management Infrastructure (WMI) screen. Configuring the Windows Firewall for WinRM 1 Open the Control Panel. 2 Click Windows Firewall. 3 Click the Exceptions tab. 4 Select the Windows Remote Management check box. If you do not see the check box, click the Add Program button to add Windows Remote Management.
Installing and Upgrading Server Administrator This section explains how to install the Server Administrator using two installation options: • Using the setup program at \SYSMGMT\srvadmin\windows on the Dell Systems Management Tools and Documentation DVD to install Server Administrator and other managed system software. • Using the unattended installation method through the Windows Installer Engine msiexec.
Typical Installation When you launch the Server Administrator installation from the Prerequisite Checker and select the Typical Setup option, the setup program installs the following managed system software features: • Server Administrator Web Server • Server Instrumentation • Remote Access Controller • Intel SNMP Agent • Broadcom SNMP Agent.
4 Select Dell OpenManage Server Administrator from the autorun menu and click Install. If the autorun program does not start automatically, go to the SYSMGMT\srvadmin\windows directory on the DVD, and run the setup.exe file. 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 are displayed. Resolve all error and warning situations, if any.
NOTE: You can cancel the installation process by clicking Cancel. The installation rolls back the changes that you made. If you click Cancel after a certain point in the installation process, the installation may not roll back properly, leaving the system with an incomplete installation. See "System Recovery on Failed Installation." 10 Click Install to install the selected software features.
Option 2: After installing Citrix, type the following command: msiexec.exe /fa SysMgmt.msi Upgrading Managed System Software The Dell OpenManage installer provides an Upgrade option for upgrading Server Administrator and other managed system software. The setup program runs the Prerequisite Checker, which uses your system's PCI bus to search for installed hardware, such as controller cards.
Red Hat Enterprise Linux 5 Update 4 to Red Hat Enterprise Linux 5 Update 5), upgrade to the latest OpenManage software; all user settings are preserved. NOTE: Uninstalling OpenManage software deletes its user settings. Re-install OpenManage software and apply the user settings. • If you have installed Server Administrator Web Server version 6.5, ensure that you install Server Instrumentation version 6.5 on your managed system.
Modify If you want to add/remove Server Administrator components: 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. 5 Select the Modify option and click Next. The Custom Setup dialog box appears.
• Yes, reboot my system now. • No, I will reboot my system later. NOTE: If you run the installer from another system and try to add a component using the Modify option, the installer may display an error. A corrupt source on the system that you run the installer from may have caused the error. You can verify this by checking the following registry entry: HKLM\Software\Classes\Installer\Products\\sourcelist\lastusedsource.
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.
Failed Updates MSI patches and updates provided by vendors must be applied to the original vendor MSI packages provided. If you intentionally or accidentally repackage an MSI package, or make changes to it directly, patches and updates might fail. MSI packages must not be repackaged; doing so changes the feature 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.
Once activated, you can find the log files that are generated in your %TEMP% directory. Some log files generated in this directory are: • Managed System Installation – • SysMgmt.log Management Station Installation – MgmtSt.log These particular log files are created by default if the Prerequisite Checker user interface (UI) is running.
NOTE: After an unattended installation is complete, in order to use the command line interface (CLI) feature of Server Administrator, you must open a new console window and execute CLI commands from there. Executing CLI commands from the same console window in which Server Administrator was installed does not work. You can make the DVD image available to the remote system by either distributing the entire contents of the media, or by mapping a drive from the target system to the location of the DVD image.
Distributing the Entire DVD as the Typical Unattended Installation Package 1 Distribute the entire image of the Dell Systems Management Tools and Documentation DVD to your target systems. 2 Configure your ISV distribution software to execute the msiexec.exe /i DVD Drive\SYSMGMT\srvadmin\windows\SystemsManagement\ SysMgmt.msi /qb command from the DVD image. The program executes to install Server Administrator on each remote system. 3 Reboot each remote system to enable Server Administrator.
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\windows\SystemsManagement directory in the DVD. 1 Configure your ISV distribution software to execute the batch script once your installation package has been distributed.
Optional Command Line Settings Table 5-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 5-1. Command Line Settings for MSI Installer Setting Result This command installs or configures a product. /i
Table 5-1. Command Line Settings for MSI Installer (continued) Setting 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 REINSTALL, and REMOVE CLI parameters in upper case, as they are case-sensitive. 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.
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. This command runs the installation for Dell OpenManage Systems Management and reinstall only the Broadcom agent, in an unattended but not silent mode.
MSI Return Code An application event log entry is recorded in the SysMgmt.log file. Table 5-3 shows some of the error codes returned by the msiexec.exe Windows Installer Engine. Table 5-3. Windows Installer Return Codes Error Code Value Description ERROR_SUCCESS 0 The action is completed successfully. ERROR_INVALID_PARAMETER 87 One of the parameters was invalid. ERROR_INSTALL_USEREXIT 1602 The user canceled the installation.
relevant informational, warning, or error messages detected during checking are displayed. 2 Click the Install, Modify, Repair, or Remove Server Administrator option. The Welcome to the Install Wizard for Dell OpenManage Server Administrator screen appears. 3 Click Next. The Program Maintenance dialog box appears. This dialog enables you to modify, repair, or remove the program. 4 Select the Remove option and click Next. The Remove the Program dialog box appears. 5 Click Remove.
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 Managed System Software on Microsoft Windows Operating Systems
Installing Dell OpenManage Software On Microsoft Windows Server 2008 Core and Microsoft Hyper-V Server 6 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.
• Intel and Broadcom agents are selected for a default install only if the corresponding devices are detected on the system. If the corresponding devices are not found, prerequisite checker generates a warning message. • DNS or WINS server running on your system can cause a warning condition for RAC software. See the relevant section in Server Administrator readme for more information. • Do not install managed system and management station RAC components on the same system.
To install the localized version of the managed system software, type msiexec /I SysMgmt.msi TRANSFORMS= .mst in the command prompt. Replace .mst with the appropriate language file: • 1031.mst (German) • 1034.mst (Spanish) • 1036.mst (French) • 1041.mst (Japanese) • 2052.mst (Simplified Chinese) NOTE: See "Command Line Settings for MSI Installer," for more information on optional, command line settings for the MSI installer.
Installing Managed System Software on Supported Linux Operating Systems 7 The Dell OpenManage installer supports both 32-bit and 64-bit architecture. The following table explains the operating system installation matrix for Dell OpenManage. Table 7-1.
inventory data to management station applications like ITA. If required, srvadmincm package can be installed from appropriate subfolders under SYSMGMT/srvadmin/linux/RPMS/supportRPMS/srvadmin from the Dell Systems Management Tools and Documentation DVD. Since srvadmin-cm RPM requires 32bit version of zlib and compat-libstdc++ libraries, ensure that these libraries are installed on the system.
Software License Agreement The software license for the Red Hat Enterprise Linux and SUSE Linux Enterprise Server version of the Dell OpenManage software is located on the Dell Systems Management Tools and Documentation DVD. Read the license.txt file. By installing or copying any of the files on the Dell-provided media, you are agreeing to the terms found in this file. This file is also copied to the root of the software tree where you choose to install the Dell OpenManage software.
To use DKS, identify which kernel is running on the managed system, and check the DKS prerequisites. Determining the Running Kernel 1 Log in as root. 2 Type the following command at a console and press : uname -r The system displays a message identifying the running kernel. Dynamic Kernel Support Prerequisites For managed system software to use DKS, the following dependencies must be met before starting Server Administrator. • The running kernel must have loadable module support enabled.
Server Administrator builds a device driver for the kernel running on the system the first time that Server Administrator starts after the kernel is loaded. By default, Server Administrator starts during system startup.
5 Start Server Administrator on system B. Server Administrator detects that the device driver you copied to the /var/omsa/dks/ directory supports the running kernel and uses that device driver. NOTE: When you have uninstalled Server Administrator from system B, the /var/omsa/dks//*. files that you copied to system B are not removed. You must remove the files if they are no longer needed.
device driver is not found, the Server Administrator Instrumentation Service degrades itself so that it does not provide any of its IPMI-based information or functionality. Primarily, this means that it does not provide any probe data (for example, fans, temperatures, and voltage probe data). Installing Managed System Software This section explains how to install managed system software using the following installation options: • Using the srvadmin-install.
• In case of Red Hat Enterprise Linux 6, install the wsman and sblim packages from the operating system DVD. To install these packages: a In the Package selection screen, select Basic Server. b Select Customize now and click Next. c Select the System Management group d From the sub-category, select the Web-based Enterprise Management Optional Packages option.
To review the software before you install it, follow this procedure: 1 Load the Dell Systems Management Tools and Documentation DVD into your system's DVD drive. 2 Mount the DVD, if required. 3 When you have mounted the DVD, navigate to: /SYSMGMT/srvadmin/linux/ The installation script and RPM folder are available under the linux directory. Express Install Use the provided shell script to perform the express installation. NOTE: On the Red Hat Enterprise Linux 5.
NOTE: The 32-bit srvadmin-cm RPM is not installed when OpenManage is installed on a 64-bit operating system. If required, the srvadmin-cm package can be installed from the appropriate subfolders under SYSMGMT/srvadmin/linux/RPMS/supportRPMS/srvadmin from the Dell Systems Management Tools and Documentation DVD. Inventory Collector utility carried as part of srvadmin-cm rpm feeds software inventory data to Dell Management Station applications like ITA.
For example, if you are running Red Hat Enterprise Linux version 5, you can customize the installation by adding the RPMs from the following directories: SYSMGMT/srvadmin/linux/custom/RHEL5 Storage Management component packages /add-StorageManagement/ for Red Hat Enterprise Linux SYSMGMT/srvadmin/linux/custom/RHEL5 Server Administrator Web Server /SAWebServer/ component packages for Red Hat Enterprise Linux SYSMGMT/srvadmin/linux/custom/RHEL5 Server Instrumentation packages for Red /Server-Instr
The following is an example of custom RPMs-based installation of Server Administrator, including the installation of the Remote Enablement feature and the Storage Management Service components. NOTE: On the Red Hat Enterprise Linux 5.x operating system, DVDs are automounted 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.
Using the Shell Script to Perform the Custom Installation You can run the Server Administrator Custom Install script in an interactive mode. The basic usage of the script is: srvadmin-install.sh [OPTION]... Server Administrator Custom Installation Utility This utility runs in interactive mode if you do not specify any options, and it runs silently if you provide one or more options. The options are: [-x|--express] installs all components (including RAC, if available) any other options passed are ignored.
Using the Shell Script to Perform the Installation in Interactive Mode This installation procedure uses the srvadmin-install.sh to prompt you for the installation of specific components through the installation. 1 Log in as root to the system running the supported 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 Mount the DVD, if required.
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. Server Administrator services do not start automatically. 6 Start Server Administrator services after the installation by using the command: sh srvadmin-services start NOTE: After installing Server Administrator, log out and then log in again to access the Server Administrator Command Line Interface (CLI).
Dependent RPMs for Remote Enablement If you choose to install the Remote Enablement feature, you have to install certain dependent RPMs and configure these RPMs before installing the feature. The dependent RPMs are available on the Dell Systems Management Tools and Documentation DVD at srvadmin\linux\RPMS\supportRPMS\opensourcecomponents\\.
5 Check for the required dependencies for the openwsman and sfcbd RPMs listed in Table 7-3. Table 7-3.
NOTE: Install the libwsman and openwsman client RPMs simultaneously as they have cyclic dependency. rpm -ivh libwsman1-x.x.x.rpm openwsman-clientx.x.x.rpm rpm -ivh openwsman-server-x.x.x.rpm Post-Installation Configuration for Remote Enablement This section details the steps to configure the dependent RPMs if you have installed the Remote Enablement feature. The post-installation configuration script is available at /opt/dell/srvadmin/etc/ on the server file system.
Reusing an Existing Certificate If you have a self-signed or CA-signed certificate, you can use the same certificate for the openwsman server by updating the ssl_cert_file and ssl_key_file values, grouped under [server] tag, in /etc/openwsman/openwsman.conf with your existing certificate values. Configuring CRL for the openwsman Client You need to configure the Certificate Revocation List (CRL) used by Server Administrator Web Server.
Winbind Configuration for openwsman and sfcb for Red Hat Enterprise Linux Operating Systems Follow the instructions mentioned below to configure openwsman and sfcb on 32-bit OMI installation. In case of a 64-bit installation, replace "lib" with "lib64". 1 Take a backup of the following files: • /etc/pam.d/openwsman • /etc/pam.d/sfcb • /etc/pam.d/system-auth 2 Replace the content of /etc/pam.d/openwsman and /etc/pam.d/sfcb with: auth required pam_stack.
account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_krb5.so account [default=bad success=ok user_unknown= ignore] /lib/security/$ISA/pam_winbind.so account required /lib/security/$ISA/pam_permit.so password requisite /lib/security/$ISA/pam_cracklib.so retry=3 password sufficient /lib/security/$ISA/pam_unix.so nullok use_authtok md5 shadow password sufficient /lib/security/$ISA/pam_krb5.so use_authtok password sufficient /lib/security/$ISA/pam_winbind.
auth include common-auth auth required /lib/security/pam_nologin.so account include common-account 3 Replace the content of /etc/pam.d/common-auth with: auth required pam_env.so auth sufficient pam_unix2.so debug auth sufficient pam_winbind.so use_first_pass debug 4 Replace the content of /etc/pam.d/common-account with: account sufficient pam_unix2.so account sufficient pam_winbind.
Uninstalling Managed System Software To uninstall Managed System Software, you must be logged in as root. Uninstalling Managed System Software Using the Uninstall Script An uninstallation script is installed when you install Server Administrator. You can execute the script by typing srvadmin-uninstall.sh and then pressing . Uninstalling Managed System Software Using the RPM Command The individual components of Dell OpenManage can be uninstalled without uninstalling all of Dell OpenManage.
NOTE: If you have more than one Supplemental Pack, (either the Linux Supplemental Pack from Citrix or other third party applications) you can install them in any order, although it is recommended that you install the Dell OpenManage Supplemental Pack last. d • After completing the Dell OpenManage Supplemental Pack installation (2-5 minutes, depending on the speed of your system), you are prompted to install other Supplemental Packs. If not, select Skip and press Enter.
could make any potential issue debugging effort difficult or impossible. A future Supplemental Pack release supports removal of the Dell OpenManage Supplemental Pack. If the XenServer image is upgraded to a newer XenServer update or release, the Dell OpenManage Supplemental Pack must be re-installed since the new XenServer image is placed on a different partition than the original. In this case, follow the same installation instructions as before.
Installing Managed System Software on Supported Linux Operating Systems
8 Dell OpenManage on VMware ESXi VMware ESXi is factory-installed on some Dell systems. For a list of these systems, see the latest Dell Systems Software Support Matrix at support.dell.com/support/edocs/software/omswrels/index.htm. You can use Server Administrator Web Server version 6.5 to access VMware ESXi 4.0 and VMware ESXi 4.1 systems. Dell OpenManage on VMware ESXi 4.0 and ESXi 4.1 Dell OpenManage Server Administrator is available as a .zip file to be installed on systems running on VMware ESXi 4.
vihostupdate.pl --server -i -b NOTE: The .pl extension is not required if you are using vSphere CLI on Linux. 5 Enter the root username and password of the ESXi host when prompted. The command output displays a successful or a failed update. In case of a failed update, see "Troubleshooting". 6 Restart the ESXi host system.
You must install the Server Administrator Web Server separately on a management station. For information on installing the Server Administrator Web Server, see "Installing Managed System Software on Microsoft Windows Operating Systems" and "Installing Managed System Software on Supported Linux Operating Systems". After installing Server Administrator, you have to enable Server Administrator Services.
Enabling Server Administrator Services on the Managed System The Server Administrator Web Server communicates with the VMware ESXi system through the Server Administrator Common Interface Model (CIM) provider. The Server Administrator CIM provider is an OEM provider on the VMware ESXi system. CIM OEM providers are disabled by default on VMware ESXi. You must enable the CIM OEM providers on the VMware ESXi 4.0/ESXi 4.1 system before accessing it using Server Administrator Web Server.
Enabling CIM OEM Providers Using vSphere CLI (for VMware ESXi 4.0/ESXi 4.1) 1 If you are using vSphere CLI on Microsoft Windows, navigate to the directory in which you have installed the vSphere CLI utilities. If you are using vSphere CLI on Linux, you can execute the command in step 2 from any directory. 2 Execute the following command: vicfg-advcfg.pl --server --username --password --set 1 UserVars.CIMOEMProvidersEnabled NOTE: For ESXi 4.
3 For the changes to take effect without restarting the system, use the Restart Management Agents option in the Direct Console User Interface (DCUI) on the local console of the VMware ESXi system. If the changes are not effective and you cannot connect to the VMware ESXi host using Server Administrator, restart the VMware ESXi host system. Uninstalling the existing OpenManage VIB The following command can be used to uninstall the existing OpenManage VIB: vihostupdate.
3 Navigate to the directory in which the vSphere CLI is installed. The default location on Linux is /usr/bin and on Windows is C:\Program Files\VMware\VMware vSphere CLI\bin. 4 Configure the SNMP setting using the following command: vicfg-snmp.
Dell OpenManage on VMware ESXi
9 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.
Overview of the Active Directory Schema Extensions Dell created Classes, or groups of objects, that can be configured by the user to meet their unique needs. New Classes in the schema include an Association, a Product, and a Privilege class. An Association object links the users or groups to a given set of privileges and to systems (Product Objects) in your network.
Figure 9-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.
For example, you have two DRAC 4 cards (RAC1 and RAC2) and three existing Active Directory users (user1, user2, and user3). You want to give user1 and user2 an Administrator privilege on both DRAC 4 cards and give user3 a Login privilege on the RAC2 card. Figure 9-2 shows how you set up the Active Directory objects in this scenario. Figure 9-2.
4 Group User1 and User2 into Group1. 5 Add Group1 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both RAC1 and RAC2 as RAC Products in AO1. 6 Add User3 as Members in Association Object 2 (AO2), Priv2 as Privilege Objects in AO2, and RAC2 as RAC Products in AO2. See "Adding Users and Privileges to Active Directory" for detailed instructions. Figure 9-3 shows how to setup the Active Directory objects in multiple domains for RAC.
To set up the objects for this multiple domain scenario, perform the following tasks: 1 Ensure that the domain forest function is in Native or Windows 2003 mode. 2 Create two Association Objects, AO1 (of Universal scope) and AO2, in any domain. The figure shows the objects in Domain2. 3 Create two RAC Device Objects, RAC1 and RAC2, to represent the two remote systems. 4 Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (Administrator) and Priv2 has Login privileges.
Figure 9-4. Setting Up Server Administrator Active Directory Objects in Multiple Domains Domain 1 Domain 2 AO1 Group1 User1 User2 AO2 Priv1 User3 Priv2 sys1 Group1 sys2 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.
6 Add User1 and User2 as Members in Association Object 1 (AO1), Priv1 as Privilege Objects in AO1, and both sys1 and Group1 as Products in AO1. 7 Add User3 as a Member in Association Object 2 (AO2), Priv2 as a Privilege object in AO2, and Group1 as a Product in AO2. Note that neither of the Association objects needs to be of Universal scope in this case.
adsupport=true adproductname=omsaApp 3 Restart the DSM SA Connection Service after saving the omsaoem.ini file. 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.
Table 9-1 list the folder names and . Table 9-1. Folder Names and Installation Types Folder Name Installation Type ITA7 IT Assistant version 7.0 or later OMSA Dell OpenManage Server Administrator Remote_Management RAC 4, RAC 5, CMC, and iDRAC on xx0x modular systems Remote_Management_Advanced iDRAC on xx1x systems NOTE: Only iDRAC6 is supported on xx1x systems. To use the LDIF files, see the instructions in the readme that is in the LDIF files directory.
For more information on class definitions for DRAC, see the Dell Remote Access Controller 4 User’s Guide and Dell Remote Access Controller 5 User’s Guide. For more information on class definitions for iDRAC, see the Integrated Dell Remote Access Controller User's Guide. Table 9-2. Class Definitions for Classes Added to the Active Directory Schema Class Name Assigned Object Identification Number Class Type (OID) dellAssociationObject 1.2.840.113556.1.8000.1280.1.1.1.2 Structural Class dellPrivileges 1.
Table 9-4. dellPrivileges Class (continued) OID 1.2.840.113556.1.8000.1280.1.1.1.4 SuperClasses User Attributes dellRAC4Privileges dellRAC3Privileges dellOmsaAuxClass dellItaAuxClass Table 9-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 9-6. dellOmsa2AuxClass Class OID 1.2.840.113556.1.8000.1280.1.2.1.
Table 9-7. dellOmsaApplication Class OID 1.2.840.113556.1.8000.1280.1.2.1.2 Description This class represents the Server Administrator application. Server Administrator must be configured as dellOmsaApplication in Active Directory. This configuration enables the Server Administrator application to send LDAP queries to Active Directory. Class Type Structural Class SuperClasses dellProduct Attributes dellAssociationMembers Table 9-8. dellIta7AuxClass Class OID 1.2.840.113556.1.8000.1280.1.3.1.
Table 9-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 9-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.
For 64-bit Windows operating systems, the Snap-in installer is located under :\SYSMGMT\ManagementStation\support\ OMActiveDirectory_SnapIn64. NOTE: You must install the Administrator Pack on each management station that is managing the new Active Directory objects. The installation is described in the following section, "Opening the Active Directory Users and Computers Snap-In." If you do not install the Administrator Pack, then you cannot view the new object in the container.
Creating a Product Object NOTE: Server Administrator and IT Assistant users must use Universal-type Product Groups to span domains with their product objects. NOTE: When adding Universal-type Product Groups from separate domains, you have to create an Association object with Universal scope. The default Association objects created by the Dell Schema Extender utility are domain Local Groups and does not work with Universal-type Product Groups from other domains.
Creating an Association Object The Association Object is derived from a Group and must contain a group Type. The Association Scope specifies the Security Group Type for the Association Object. When you create an Association Object, you must choose the Association Scope that applies to the type of objects you intend to add. Selecting Universal, for example, means that Association Objects are only available when the Active Directory Domain is functioning in Native Mode or above.
Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to a system. NOTE: You can add only one Privilege Object to an association object. To add a privilege: 1 Select the Privileges Object tab and click Add. 2 Type the Privilege Object name or browse for one and click OK. Click the Products tab to add one or more systems or devices to the association.
name, where system name is the name of the system running Server Administrator, and software-product name refers to the name of the software product defined in omprv32.ini (that is, computerName-omsa). NOTE: This command is applicable only on systems running the Windows operating system. NOTE: Restart the Server Administrator service after you have configured Active Directory. Table 9-13 shows the valid parameters for the command. Table 9-13.
10 Prerequisite Checker Command Line Operation of the Prerequisite Checker You can run the prerequisite check silently by executing runprereqchecks.exe /s from the SYSMGMT\srvadmin\windows\PreReqChecker directory on the Dell Systems Management Tools and Documentation DVD. After running the prerequisite check, an HTML file (omprereq.htm) is created in the %Temp% directory. This file contains the results of the prerequisite check.
Table 10-1. Return Codes While Running the Prerequisite Check Silently (continued) Return Code Description 3 An error condition, or conditions, is associated with the software. It is required that you resolve the conditions causing the error before proceeding with the installation of that software. If you do not resolve the issues, the software is not installed. -1 A Microsoft Windows Script Host (WSH) error. The Prerequisite Checker does not run. -2 The operating system is not supported.
Table 10-2.
Prerequisite Checker
Frequently Asked Questions 11 General How do I install Dell OpenManage Server Administrator with only the CLI features? By choosing not to install the Server Administrator Web Server, you get CLI features only. What ports do Dell OpenManage applications use? The default port used by Server Administrator is 1311. The default ports used by Dell OpenManage IT Assistant are 2607 (for the connection service) and 2606 (for the network monitoring service). These ports are configurable.
• Find out the version of Server Administrator that was previously installed. • Download the installation package for that version from support.dell.com. • 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.
When launching the Dell OpenManage Installer, an error message may display, stating a failure to load a specific library, a denial of access, or an initialization error. An example of installation failure during Dell OpenManage Install is "failed to load OMIL32.DLL." What do I do? This is most likely due to insufficient COM permissions on the system. See the following article to remedy this situation: support.installshield.com/kb/view.
When I run Dell OpenManage Installer, I see unreadable characters on the Prerequisite check information screen. When you run Dell OpenManage Install in English, German, French, or Spanish and get unreadable characters on the Prerequisite Check Information screen, ensure that your browser encoding has the default character set. Resetting your browser encoding to use the default character set resolves the problem.
I downloaded the Server Administrator files for Windows from the Dell Support website and copied it to my own media. When I tried to launch the SysMgmt.msi file, it failed. What is wrong? MSI requires all installers to specify the MEDIAPACKAGEPATH property if the MSI file does not reside on the root of the DVD. This property is set to SYSMGMT\srvadmin\windows\SystemsManagement for the managed system software MSI package. If you decide to make your own DVD you must ensure that the DVD layout stays the same.
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.txt on the Dell Systems Management Tools and Documentation DVD, for detailed information about how to use the Prerequisite Checker. In the Prerequisite Checker screen, I get the message "An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly.
Is the time shown during installation/uninstallation by Windows Installer Services is accurate? No. During installation/uninstallation, the Windows Installer Service may display the time remaining for the current task to complete. This is only an approximation by the Windows Installer Engine based on varying factors. Can I launch my installation without running the Prerequisite Checker? How do I do that? Yes, you can.
What are the names of all the Dell OpenManage features under Windows? The following table lists the names of all Dell OpenManage features and their corresponding names in Windows. Table 11-1.
I manually installed my Red Hat Enterprise Linux 4 - x86_64 operating system and can see RPM dependencies when trying to install Server Administrator. Where can I find these dependent RPM files? For Red Hat Enterprise Linux, the dependent RPM files are on the Red Hat Enterprise Linux installation media. All other RPMs are available in the /SYSMGMT/srvadmin/linux/RPMS/supportRPMS\opensourcecomponents directory.
NOTE: If you are using later versions of supported Linux operating systems and the RPM files available in the directory SYSMGMT/srvadmin/linux/RPMS/supportRPMS on the DVD are incompatible, use the latest RPMs from your operating system media. Where can I find the source packages for Open Source RPMs? Source packages for Open Source RPMs are available on an orderable DVD image.
error: %preun(srvadmin-NAME-X.Y.Z-N.i386) scriptlet failed, exit status 1 In this case, NAME is a feature name, for example omacore. X.Y.Z-N is the version and build number of the feature. Some possible solutions to rectify this problem: 1 Attempt to uninstall again. For example, use the following command: rpm -e srvadmin-NAME-X.Y.Z-N.i386 2 Delete the "upgrade.relocation=bad" line if present in the /etc/omreg.cfg file and attempt to uninstall again.
Table 11-2.
Table 11-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 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadminidraccomponents Integrated Dell Remote Access Card Data Populator Remote Access Controller components. srvadmin-omilcore, srvadmin-deng, srvadmin-hapi, and srvadmin-racser srvadminidracadm iDRAC Command Interface — The command srvadmin-omilcore line user interface to the Integrated Dell Remote Access Controller.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required add-RAC5 — Software for remote management of fifth generation Remote Access Controllers. For example: DRAC 5. srvadmin-rac5- Remote Access Card Data Populator, DRAC 5 srvadmin-omilcore, components and Remote Access Controller components, srvadmin-deng, and DRAC 5.
Table 11-3. Names of the Directories Under the srvadmin/linux/custom/ Directory (continued) Name of RPM Description Other Server Administrator RPMs required srvadmin-jre Server Administrator Sun Java Runtime Environment — Systems management managed node Java runtime. srvadmin-omilcore, srvadmin-deng, and srvadmin-omacore srvadminomauth Provides the authentication files. srvadmin-omilcore srvadminomcommon Provides the common framework required by Server Administrator.
Table 11-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.
What are the additional components that can be installed on a system that already has Server Administrator installed? There are a few additional components that can be installed on a system that already has Server Administrator installed. For example, you can install Online Diagnostics on a system that has previously been installed with managed system software.
What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems after Server Administrator is started? The daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems depend on what has been installed and what is enabled to run. The following table displays the daemons that typically run for a full install: Table 11-4.
What kernel modules are loaded when Server Administrator is started? This is dependent on the type of systems instrumentation. The following table displays the kernel modules loaded when Server Administrator is started. Table 11-5.
A Dell OpenManage Linux Installer Packages This appendix lists the Dell OpenManage Linux installer packages. Table A-1. Meta RPMs RPM Description Dependant packages Required for OpenManage 6.2 6.3 6.4 6.
Table A-1. Meta RPMs (continued) RPM Description srvadmin- Meta package for storageser installing the vices Server Administrator Storage Services feature Dependant packages Required for srvadminstorage srvadminsmcommon srvadmin-cm srvadminmegalib (only for 32-bit install) srvadmin-fsa (Removed in 6.3) srvadminstorelib srvadminstoragepopulator* srvadminsysfsutils *- obsolete in OM6.
Table A-1. Meta RPMs (continued) RPM Description Dependant packages Required for OpenManage 6.2 6.3 6.4 6.5 srvadmin- Meta rpm for srvadminrac5 RAC5 components omilcore srvadminracdrsc5 srvadminracadm5 srvadminracdrsc* srvadmin-raccomponents * - 6.
Table A-2. Server Instrumentation and SNMP monitoring (continued) RPM Description OM Dependant packages Required for OpenManage 6.2 6.3 6.4 6.
Table A-3. Packages needed for local management that are used by GUI and CLI components RPM Description OM Dependant packages Required for srvadminCommon omcommon framework / libraries for GUI/CLI srvadminomilcore srvadminomacore Provides plugins that act as interface between back end and GUI/CLI. Also provides OM CLI tools. srvadminomhip srvadminxmlsup OpenManage 6.2 6.3 6.4 6.
Table A-3. Packages needed for local management that are used by GUI and CLI components (continued) RPM Description OM Dependant packages srvadmincm Change srvadminManagement omacore NOTE: On a inventory collector. Feeds s/w scripted inventory data to install, srvadmin-cm management is installed on station 32bit operating applications like systems only. ITA Required for OpenManage 6.2 S/W Y inventory & updates using ITA 6.3 6.4 6.
Table A-4. Server Administrator web server (GUI) for local and remote management RPM srvadminomauth Description Dependant packages Provides NA authentication files for GUI Required for OpenManage 6.2 a 6.3 6.4 6.5 Server Administrator GUI O N N N openwsma Openwsman n-client client libraries None Server Administrator GUI to manage remote nodes using WSMAN Y Y Y Yb libwsman1 Openwsman libraries used by client and server components None Openwsman support library Y Y Y Yb a.
Table A-5. Server Administrator Remote Enablement (Standard Agent) (continued) RPM Description sblim-sfcb >= 1.3.7 sblim-sfcc >= 2.2.1 openwsmanclient >= 2.2.3.9 openwsmanserver >= 2.2.3.9 libwsman1 >= 2.2.3.9 libcmpiCppI mpl0 >= 2.0.
Table A-5. Server Administrator Remote Enablement (Standard Agent) (continued) RPM sblim-sfcc Description OM Dependant packages Small Footprint CIM None Client Library (sfcc) Runtime Libraries *N/A on VmWare ESX libcmpiCpp Provides helper library None Impl0 to implement CMPI C++ plugins into SFCB Required for OepnManage 6.2 6.3 6.4 6.
Table A-6. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description srvadminstoragepopulator OM Dependant Required for packages OpenManage 6.2 6.3 6.4 6.5 Y Y Oa N Storage Instrumentation Y Y Y Y Low-level srvadminStorage libraries to omilcore Instrumentation discover and srvadmin-deng monitor storage srvadmin-isvc srvadminstorage srvadminstorelib LSI utility libraries for storage management srvadminstoreliblibpci PCI utilities for None Kernel.
Table A-6. Storage Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM srvadminmegalib Description OM Dependant Required for packages LSI utility None libraries for storage management of PERC 4 controllers. OpenManage 6.2 6.3 6.4 6.5 Storage Instrumentation of PERC 4 controllers Y Y Y Y *N/A for 64-bit OMSA installation, and VmWare ESX.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins RPM Description srvadminracsvc RAC services to manage DRAC 4 OM Dependant packages Required for srvadminomilcore DRAC 4 Y Instrumentation Y DRAC 4 Y Instrumentation and SNMP monitoring Oa N N srvadminRAC Data populator srvadminrac4for DRAC 4 omilcore components srvadmin-hapi srvadmin-deng OpenManage 6.2 6.3 6.4 6.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description OM Dependant packages Required for srvadminomilcore srvadmin-deng srvadminomcommon srvadminomacore srvadmin-rac5components DRAC 5 management using Server Administrator GUI/CLI OpenManage 6.2 6.3 6.4 6.
Table A-7. RAC Instrumentation, SNMP Monitoring, GUI and CLI Plugins (continued) RPM Description OM Dependant packages Required for OpenManage 6.2 6.3 6.4 6.5 srvadminrac4populator- RAC Data populator srvadmin-hapi DRAC 4 N Y for DRAC 4 Instrumentation srvadmin-deng srvadminargtable2 Library for parsing GNU style command line argument.
Table A-8. Enable Software inventory and updates using IT Assistant RPM Description OM Dependant packages srvadmin-cm Change Management srvadmininventory collector. omacore Feeds s/w inventory data to management station applications like ITA Required for OpenManage 6.2 6.3 6.4 6.
Dell OpenManage Linux Installer Packages
Index A B access read-only, 21 write, 21 batch script, 76 BIOS, 14 access control, 20 Active Directory, 19-20, 23, 30, 126, 132, 139, 143 object identifiers, 125 objects, 127 schema, 133 schema extender utility, 133-134 schema extensions, 125 C ADDLOCAL, 79 Certification Authority, 46 administrator, 20 CIM, 16, 27, 31 Administrator Pack, 140 Citrix, 66 Administrator privileges, 21 CLI, 17, 22, 79, 149 agent, 39 SNMP, 30 command line, 80 alert log, 17 CA, 46 certificate, 59 certificates Web,
Dell, 55, 125 G Dell base OID, 125 Globally Unique Identifier (GUID), 80 Dell organizational unit, 133 Dell Remote Access Controller, 127 group privileges, 20 GUID, 72 dellIta7AuxClass, 137 dellItaApplication, 137 dellOmsaApplication, 137 dellProduct, 136 dependency check, 113 distribution software, 84 DKS, 94 prerequisites, 94 DRAC, 140, 143 DRAC 4, 160 DRAC 5 controller, 17 H help, 18 hot spares, 14 HTTPS, 23 I INI file, 71 inoperable system, 17 installation unattended, 73 Instrumentation, 21 E
L O LDAP, 137 oem.
software, 27 racadm, 19 LDIF, 133 srvadmin-install, 104 RBAC, 20 SCSI, 14 readme, 17, 25 secure socket layer, 23 read-only access, 21 security administration, 20 Red Hat Enterprise Linux, 35, 39, 157 Security Group Type, 142 REINSTALL, 79-80 remote access, 12 remote access controller, 27 remote enablement installing WinRM, 57 requirements, 57 remote system, 75 REMOVE, 79 Server Administrator, 16, 130, 159 Services, 156 session timeout, 45 setup express, 27 Simple Network Management Protocol, 16,
storage management, 21 Storage Management Service, 156 SysMgmt.msi, 153 systems management protocol, 27 Windows Installer Engine, 75 Installer Service, 71 Windows Management Instrumentation, 27 WMI, 27, 31 write access, 21 T TCP/IP, 26 time-out, 19 tools ISV, 74 X X.
Index
