Dell Server Installation Manual
Dell Server Installation Manual

Dell Server Installation Manual

Hide thumbs Also See for Server:
Table of Contents

Advertisement

Quick Links

Server Administrator
Version 7.2 Installation Guide

Advertisement

Table of Contents
loading

Summary of Contents for Dell Server

  • Page 1 Server Administrator Version 7.2 Installation Guide...
  • Page 2: Notes, Cautions, And Warnings

    CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2012 Dell Inc. All Rights Reserved. Trademarks used in this text: Dell , the Dell logo, Dell Boomi , Dell Precision...
  • Page 3: Table Of Contents

    ....28 Winbind Configuration For openwsman And sfcb For Red Hat Enterprise Linux Operating Systems .....29 Winbind Configuration For openwsman And sfcb For SUSE Linux Enterprise Server Operating System ...........................29 Workaround For The Libssl Issue 3 Installing Managed System Software On Microsoft Windows Operating Systems ..31 ....................31...
  • Page 4 Software License Agreement ..........................46 RPM For Individual Components ............................50 OpenIPMI Device Driver ....50 Degradation Of Functionality When The Server Administrator Instrumentation Service Is Started ........................51 Installing Managed System Software .................51 Prerequisites For Installing Managed System Software ..............52 Installing Managed System Software Using The Provided Media ....................55...
  • Page 5 I get a misleading warning or error message during systems management installation.......82 I am getting the following error message while launching systems management Install: ..83 Do I need to uninstall previous versions of Server Administrator before installing Citrix Metaframe?
  • Page 6 Red Hat Enterprise Linux or SUSE Linux Enterprise Server ..................86 After installing Server Administrator, I cannot log in. I see the following message when I try to install Server Administrator on a guest Linux operating ................................86 system. I manually installed my Red Hat Enterprise Linux 4 64-bit operating system and can see RPM ....86...
  • Page 7: Linux Installer Packages

    What happens if I install the RPM package on an unsupported system or on an unsupported ............................93 operating system? What daemons run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems ......................93 after Server Administrator is started? ............94...
  • Page 9: Introduction

    DRAC5 using SNMP and does not display few of the DRAC5 information on Server Administrator GUI and CLI. • Added support for granular install options for the latest release of Server Administrator 7.2 on systems running Linux . For more information, see Linux Installer Packages.
  • Page 10: Server Administrator Components On A Managed System

    Systems Management Tools and Documentation • Server Update Utility • Management Station Software Installation Guide . NOTE: For more information on these DVDs, see Server Administrator Components On A Managed System The setup program provides the following options: • Custom Setup • Typical Setup The custom setup option enables you to select the software components you want to install.
  • Page 11 CIM Provider systems management tasks. list of supported systems, Systems Software Install Remote Enablement see the on one system and Server Support Matrix . Administrator Web Server on another system. You can use the system with the Server Administrator to...
  • Page 12: Security Features

    (LDAP) authentication protocols for Linux operating systems. • Role-based authority that allows specific privileges to be configured for each user. NOTE: Applicable only for systems running Red Hat Enterprise Linux, SUSE Linux Enterprise Server, or VMware ESX/ESXi. • User ID and password configuration through the web-based interface or the command line interface (CLI), in most cases.
  • Page 13 Server Administrator Command Line Interface Guide documents the complete command line interface for • Server Administrator, including an explanation of CLI commands to view system status, access logs, create reports, configure various component parameters, and set critical thresholds. Remote Access Controller 5 User’s Guide provides complete information about installing and configuring a •...
  • Page 15: Preinstallation Setup

    NOTE: To use supporting agents for the Simple Network Management Protocol (SNMP), install the operating system support for the SNMP standard before or after you install Server Administrator. For more information about installing SNMP, see the installation instructions for the operating system you are running on the system.
  • Page 16 If the corresponding devices are not found, prerequisite checker generates a warning message. • Domain Name System (DNS) or Windows Internet Name Service (WINS) server running on the system can cause a warning condition for RAC software. See the relevant section in Server Administrator readme for more information.
  • Page 17 \\Control\\Session Manager\\PendingFileRenameOperations indicates that a reboot is pending. • Running the 64-bit version of Windows Server 2008 Core, since certain components are disabled from being installed. Ensure that any error or warning is corrected before you proceed to install systems management software components.
  • Page 18: Installation Requirements

    To view the localized versions of the web interface on Windows, in the Control Panel select Regional and Language Options. System Requirements Install Server Administrator on each system to be managed. You can manage each system running Server Administrator locally or remotely through a supported web browser. Managed System Requirements •...
  • Page 19 NOTE: Systems Management software detects the MSI version on the system. If the version is lower than 3.1, the prerequisite checker prompts you to upgrade to MSI version 3.1. After upgrading the MSI to version 3.1, reboot the system to install other software applications such as Microsoft SQL Server. Related Links:...
  • Page 20: Digital Certificates

    Digital Certificates All Server Administrator packages for Microsoft are digitally signed with a certificate that helps guarantee the integrity of the installation packages. If these packages are repackaged, edited, or manipulated in other ways, the digital signature is invalidated. This manipulation results in an unsupported installation package and the prerequisite checker does not allow you to install the software.
  • Page 21: Configuring Snmp Agents

    509 Certificate Management Setting User And Server Preferences You can set user and secure port server preferences for Server Administrator from the Preferences web page. Click General Settings and click either the User tab or Web Server tab. Setting User Preferences To set up user preferences: NOTE: Log in with administrator privileges to set or reset user or server preferences.
  • Page 22 Specifies the organization's Simple Mail Transfer Protocol (SMTP) and Domain Name name and DNS Server (DNS) suffix. To enable Server Administrator to send e-mails, you must type the IP Suffix for SMTP address and DNS suffix for the SMTP server for the organization in the appropriate fields.
  • Page 23: X.509 Certificate Management

    Authority (CA). Authorized CAs include Verisign, Entrust, and Thawte. NOTE: Log in with administrator privileges to perform certificate management. You can manage X.509 certificates for Server Administrator from the Preferences page. Click General Settings, select the Web Server tab, and click X.509 Certificate.
  • Page 24: Installing Winrm

    Installing WinRM On Windows Server 2008 R2, Windows Server 2008 R2 SP1, Windows 7, Windows 8 and Windows Server 2012, WinRM 2.0 is installed by default. On Windows Server 2008, WinRM 1.1 is installed by default. Certificate Authority Signed Self-Signed Certificate You need a certificate signed by a CA or a self‑signed certificate (generated using the SelfSSL tool) to install and...
  • Page 25 WinRM To configure user authorization for WinRM servers: Click Start → Run. Type winrm configsddl and click OK. If you are using WinRM 2.0, type winrm configsddl default. Click Add and add the required users or groups (local/domain) to the list. Provide the appropriate permission(s) to the respective users and click OK.
  • Page 26: Dependent Rpms For Remote Enablement

    If the binaries are installed, uninstall these binaries. Check for the required dependencies for the openwsman and sfcbd RPMs listed in the following table. Table 5. Required Dependencies Packages Red Hat Enterprise Server SUSE Linux Enterprise Server Openwsman OpenSSL LibOpenSSL...
  • Page 27: Post-Installation Configuration For Remote Enablement

    Creating A New Certificate You can create a new server certificate for WSMAN by executing the owsmangencert.sh script located at /etc/ openwsman. This script is provided by the openwsman RPM. Follow the steps in the wizard to create the server certificate.
  • Page 28: Winbind Configuration For Openwsman And Sfcb For Red Hat Enterprise Linux Operating Systems

    NOTE: For more information on chkconfig and its usage, see the operating system documentation. The managed system is configured and is ready to be used by the 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.
  • Page 29: Winbind Configuration For Openwsman And Sfcb For Suse Linux Enterprise Server Operating System

    Winbind Configuration For openwsman And sfcb For SUSE Linux Enterprise Server Operating System 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. Back up the following files: –...
  • Page 31: Installing Managed System Software On Microsoft Windows Operating Systems

    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. Using this method reduces the Server Administrator footprint on the managed systems.
  • Page 32: Installer Location

    SNMP stop. If the third party services are stopped, manually restart these services. NOTE: For Blade systems, you must install Server Administrator on each server module installed in the chassis. NOTE: During installation of Server Administrator on supported Windows systems, if an Out of Memory error message is displayed, you must exit the installation and free up memory.
  • Page 33 During a Typical installation, individual management station services that do not meet the specific hardware and software requirement for that service are not installed on the managed systems. For example, the Server Administrator Remote Access Controller service software module is not installed during a Typical installation unless the managed system has a remote access controller installed on it.
  • Page 34 Citrix remaps all the hard drive letters when installed. For example, if you install Server Administrator on drive C: and then install Citrix, it may change the drive letter C: to M:. Server Administrator may not work properly because of the remapping.
  • Page 35 The msiexec.exe /i <SysMgmt or SysMgmtx64>.msi /qb command accesses the DVD to accept the software license agreement and installs all the required Server Administrator features on selected remote systems. These features are installed on the remote systems based on the system's hardware configuration.
  • Page 36 Use the ISV distribution software to distribute the custom unattended installation package to the remote systems. The batch script installs Server Administrator along with specified features on each remote system. The batch script installs Server Administrator along with specified features on each remote system.
  • Page 37 For example, you can choose to install Server Administrator, but not Remote Access Controller service on a specific group of servers, and choose to install Server Administrator, but not Storage Management Service, on another group of servers.
  • Page 38: System Recovery On Failed Installation

    You can also choose to install, reinstall, and uninstall features with one execution of the msiexec.exe program. For example, msiexec.exe /i SysMgmt.msi REMOVE=BRCM /qb This command runs the installation for managed system software, and uninstalls the Broadcom agent. This execution is in an unattended but not silent mode.
  • Page 39: Upgrading Managed System Software

    The following procedures show how to upgrade Server Administrator and other managed system software. Upgrading Guidelines • You can upgrade to the latest version of Server Administrator from any of the previous three versions. For example, upgrade to Server Administrator 7.2 is supported only for Server Administrator versions 6.5 and later. •...
  • Page 40: Modify

    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 Server Administrator prerequisite status screen is displayed and runs the prerequisite checks for the managed station. Any relevant informational, warning, or error messages are displayed. Resolve all error and warning situations, if any.
  • Page 41: Repair

    Click Install to install the selected software features. The Installing Server Administrator screen is displayed and provides the status and progress of the software features being installed. When the selected features are installed, the Install Wizard Completed dialog box is displayed.
  • Page 42: Uninstalling Managed System Software Features Using The Operating System

    The Add or Remove Programs dialog box is displayed. Click Yes to confirm uninstallation of Server Administrator. The Server Administrator screen is displayed and provides the status and progress of the software features being uninstalled. If you are prompted to reboot the system, select from the following reboot options: •...
  • Page 43 package is distributed to the remote systems using a software distribution tool from an ISV. When the package is distributed, the uninstallation script executes to uninstall the software. Distributing The Unattended Uninstallation Package Systems Management Tools and Documentation DVD is pre‑configured to act as the unattended uninstallation package.
  • Page 45: Installing Managed System Software On Supported Linux And Vmware Esx

    Management. The installation scripts and RPM packages specific to supported Linux and VMware ESX operating systems are provided to install and uninstall the Server Administrator and other managed system software components. These installation Systems scripts and RPMs are located in the SYSMGMT/srvadmin/linux/supportscripts directory available in the...
  • Page 46: Software License Agreement

    Linux scripts, install Server Administrator locally or across a network on single or multiple systems. The second install method uses the Server Administrator RPM packages provided in the custom directories and the Linux rpm command. Write Linux scripts that install Server Administrator locally or across a network on single or multiple systems.
  • Page 47 Prerequisite Service Names Command Line Options for srvadmin- install.sh srvadmin-rac- components srvadmin-xmlsup dsm_sa_datamgrd Server PE Server, OS -g or --agent Instrumentation Only srvadmin-hapi dsm_sa_eventmgrd srvadmin-omilcore dsm_sa_shrsvcd srvadmin-deng srvadmin-isvc srvadmin-omcommon srvadmin-cm (applicable for x32 bit only) srvadmin-omacs srvadmin-ominst srvadmin-rac- components srvadmin-xmlsup...
  • Page 48 Prerequisite Service Names Command Line Options for srvadmin- install.sh srvadmin-xmlsup dsm_sa_datamgrd OS Logging Option PE Server, OS -l or --oslog srvadmin-hapi dsm_sa_eventmgrd srvadmin-omilcore dsm_sa_shrsvcd srvadmin-deng srvadmin-isvc srvadmin-omcommon srvadmin-oslog srvadmin-cm (applicable for x32 bit only) srvadmin-omacs srvadmin-ominst srvadmin-rac- components srvadmin-xmlsup dsm_sa_datamgrd...
  • Page 49 Plugin Component -> installed if DRAC4 srvadmin-hapi dsm_sa_eventmgrd Remote access core card is available in srvadmin-argtable2 dsm_sa_snmpd components, Server the server. DRAC5 srvadmin-omilcore dsm_sa_shrsvcd Instrumentation agent is installed for srvadmin-deng 9G and 10G servers. iDRAC agent is srvadmin-deng-snmp installed for 11G and...
  • Page 50: Openipmi Device Driver

    NOTE: To manage the server, select either Server Administrator Web Server or one of the Management Interfaces – CLI, SNMP or OS LOG along with Server Instrumentation (SI) or Server Administrator Storage Management Service (OMSS). NOTE: Command line options for [-t] and [-g] cannot be used without a management interface. These options need to be combined with management interface options such as [-w], [-i], [-z], [-l], or [-m].
  • Page 51: Installing Managed System Software

    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 degrades itself so that it does not provide any of the IPMI-based information or functionality.
  • Page 52: Installing Managed System Software Using The Provided Media

    Installing The wsman And sblim Packages In Package selection, select Basic Server. Select Customize now and click Next. Select System Management group. From the sub-category, select Web-based Enterprise Management → Optional Packages option. The default selected packages are: openwsman-client, sblim-sfcb, sblim-wbemcli, and wsmancli Deselect the sblim-wbemcli package from the above list.
  • Page 53 Where <OS> is the supported operating system and <arch> is 32-bit (i386) or 64-bit (x86_64). NOTE: In case of SUSE Linux Enterprise Server version 10 and 11: 32-bit rpm packages are provided for upgrade from the previous 32-bit installs only. If you do not have an existing installation, then you cannot install a 32-bit version of the software.
  • Page 54 Linux Installer Packages Custom RPMs Based Installation 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.
  • Page 55: Server Administrator Custom Installation Utility

    The basic usage of the script is: srvadmin-install.sh [OPTION]... Server Administrator Custom Installation Utility The Server Administrator utility runs in an interactive mode if you do not specify any options, and runs silently if you provide one or more options. The options are: •...
  • Page 56 NOTE: After installing Server Administrator, log out and then log in again to access the Server Administrator Command Line Interface (CLI). Determining The Server Administrator Architecture Use the following command to identify if the already installed Server Administrator is of 32-bit or 64-bit architecture rpm -q --queryformat "%{NAME} - %{ARCH}\n" `rpm -qa | grep srvadmin`...
  • Page 57: Managed System Software Installation Using Third Party Deployment Software

    Server Administrator is designed to match your current operating system. Installation Using Linux Repository You can install Server Administrator using the Linux Repository by following any of the methods listed below: NOTE: Ensure that you set up the Linux Repository before you install the software from the repository.
  • Page 58: Uninstalling Managed System Software

    The individual components of systems management software can be uninstalled without uninstalling all of systems management. To uninstall only the Server Administrator Web Server, use the command rpm –e `rpm -qa | grep srvadmin-tomcat`. During an uninstallation, files in which user settings are made are preserved with the .rpmsave file extension. Log files...
  • Page 59: Installing Managed System Software On Microsoft Windows Server 2008 Core And Microsoft Hyper-V Server

    A Windows Server 2008 Core or Hyper-V Server installation installs only a subset of the binaries that are required by the supported server roles. For example, the Explorer shell is not installed as part of a Windows Server 2008 Core or Hyper-V Server installation. Instead, the default user interface for a Windows Server 2008 Core or Hyper-V Server installation is the command prompt.
  • Page 60: Uninstalling Systems Management Software

    • 1036.mst (French) • 1041.mst (Japanese) • 2052.mst (Simplified Chinese) Related Links: Optional Command Line Settings Uninstalling Systems Management Software To uninstall managed system software, type msiexec /x <SysMgmt or SysMgmtx64>.msi at the command prompt.
  • Page 61: Installing Systems Management Software On Vmware Esxi

    VMware ESXi is factory-installed on some systems. For a list of these systems, see the latest Matrix . Use Server Administrator Web Server version 7.0 to access VMware ESXi 4.0 U3, VMware ESXi 4.1 U2, VMware ESXi 5.0 U1 systems.
  • Page 62: Using The Vmware Vsphere Management Assistant (Vma)

    Windows 2008 R2 SP1 64-bit server. On the desktop, double-click VMware vSphere Client and login to vCenter Server. Right-click vSphere Client host and click New Datacenter. Right-click New Datacenter and click Add Host. Provide information for the ESXi server per online instructions.
  • Page 63: Using The Power Cli

    Server Administrator installation is complete. 16. Reboot the host. NOTE: For more information on VMWare Update Manager, see the VMWare official website. NOTE: You can install Server Administrator from the VUM repository, https://vmwaredepot.dell.com/. Using The Power CLI To install Server Administrator using Power CLI: Install the supported PowerCLI of ESXi on Windows System.
  • Page 64: Enabling Server Administrator Services On The Managed System

    Common Interface Model (CIM) provider. The Server Administrator CIM provider is an Original Equipment Manufacturer (OEM) provider on the VMware ESXi system. CIM OEM providers are disabled by default on VMware ESXi 4.0 and ESXi 4.1. Enable the CIM OEM providers on the VMware ESXi system before accessing it using Server Administrator Web Server.
  • Page 65: Enabling Cim Oem Providers Using Vma (For Vmware Esxi 4.0/Esxi 4.1)

    For the changes to take effect without restarting the system, use the Restart Management Agents option in the 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.
  • Page 66: Troubleshooting

    <username> --password <password> -c <community> -t <hostname>@162/ <community> server > is the hostname or IP address of the ESXi system, < username > is a user on the ESXi system, where < password > is the password of the ESXi user, < community > is the SNMP community name and < hostname > is the <...
  • Page 67: Installing Systems Management Software On Citrix Xenserver

    Installing Systems Management Software On Citrix XenServer The Server Administrator is installed on Citrix XenServer using the Supplemental Pack. The Supplemental Pack for Citrix XenServer can be installed in two ways: • During the installation of XenServer • On a running system...
  • Page 68: Xenserver Upgrade

    $ xe-install-supplemental-pack <openmanange-supplemental-pack-filename>.iso NOTE: If a previous version of Server Administrator is already installed on the system, then the command to upgrade it to version 7.0 is ./install.sh. After the installation or upgrade, execute the following post-installation configuration script of Remote Enablement...
  • Page 69: Using Microsoft 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 user or group to a given set of privileges and to systems (Product Objects) in the network.
  • Page 70 In addition, you can set up Active Directory objects in a single domain or in multiple domains. Setting up objects in a single domain does not vary, whether you are setting up RAC, or Server Administrator objects. When multiple domains are involved, however, there are some differences.
  • Page 71: Active Directory Objects In Multiple Domains

    Figure 2. Setting Up RAC Active Directory Objects in a Single Domain Setting Up Objects In A Single Domain To set up the objects in a single domain scenario, perform the following tasks: Create two Association Objects. Create two RAC Product Objects, RAC1 and RAC2, to represent the two DRAC 4 cards. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privileges.
  • Page 72: Setting Up Server Administrator Active Directory Objects In Multiple Domains

    Setting Up Server Administrator Active Directory Objects In Multiple Domains For Server Administrator, the users in a single Association can be in separate domains and need not be in a Universal group. The following is a very similar example to show how Server Administrator systems in separate domains affect the setup of directory objects.
  • Page 73: Configuring Active Directory To Access The Systems

    Ensure that the domain forest function is in Native mode. Create two Association Objects, AO1 and AO2, in any domain. The figure shows the objects in Domain1. Create two Server Administrator Products, sys1 and sys2, to represent the two systems. sys1 is in Domain1 and sys2 is in Domain2.
  • Page 74: Configuring The Active Directory Product Name

    Extending The Active Directory Schema The schema extensions for RAC and Server Administrator are available. Extend the schema for software or hardware that you are using. Apply each extension individually to receive the benefit of its software-specific settings. Extending the Active Directory schema adds schema classes and attributes, example privileges and association objects, and a organizational unit to the schema.
  • Page 75: Using The Dell Schema Extender

    To use the Dell Schema Extender perform the following tasks: CAUTION: The Dell Schema Extender uses the SchemaExtenderOem.ini file. To ensure that the Dell Schema Extender utility functions properly, do not modify the name or the contents of this file.
  • Page 76 Table 16. dellPrivileges Class 1.2.840.113556.1.8000.1280.1.1.1.4 Description This class is used as a container Class for the Dell Privileges (Authorization Rights). Class Type Structural Class SuperClasses User dellRAC4Privileges Attributes dellRAC3Privileges dellOmsaAuxClass Table 17. dellProduct Class 1.2.840.113556.1.8000.1280.1.1.1.5 Description This is the main class from which all Dell products are derived.
  • Page 77: Active Directory Users And Computers Snap-In

    Product. This attribute is the backward link to the dellProductMembers Linked attribute. Link ID: 12071 Table 21. Server Administrator-Specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Single Valued Identifier 1.2.840.113556.1.8000.1280.1.2.2.1...
  • Page 78: Adding Users And Privileges To Active Directory

    Adding Users And Privileges To Active Directory The extended Active Directory Users and Computers snap-in allows you to add DRAC and Server Administrator users and privileges by creating RAC, Association, and Privilege objects. To add an object, perform the steps in the applicable subsection.
  • Page 79 In the Console Root (MMC) window, right-click a container. Select New. Select a RAC or Server Administrator object, depending on what you have installed. The New Object window is displayed. Type in a name for the new object. Select the appropriate Privilege Object.
  • Page 80 Remote Access Controller 5 User’s Guide . For iDRAC users, see the Integrated Remote Access Controller User's Guide . NOTE: The systems on which Server Administrator is installed must be a part of the Active Directory domain and should also have computer accounts on the domain.
  • Page 81: Frequently Asked Questions

    Microsoft Windows How do I fix a faulty installation of Server Administrator? You can fix a faulty installation by forcing a reinstall and then performing an uninstall of Server Administrator. To force a reinstall: 1. Find out the version of Server Administrator that was previously installed.
  • Page 82: What Do I Do When The Creation Of Winrm Listener Fails With The Following Error Message

    The CertificateThumbprint property must be empty when the SSL configuration will be shared with another service This error occurs when the Internet Information Server (IIS) is already installed and configured for HTTPS communication. Details about coexistence of IIS and WinRM is available at technet.microsoft.com/en-us/library/ cc782312.aspx.
  • Page 83: Do I Need To Uninstall Previous Versions Of Server Administrator Before Installing Citrix Metaframe

    Windows Server 2008, I do not see Server Administrator icon on the desktop? On an initial Server Administrator install using remote Server Administrator deploy (OMSA push) on a server running Windows Server 2008, the Server Administrator icon is not visible until the desktop is refreshed manually by pressing the <F5> key.
  • Page 84: Does Systems Management Install Support Windows Advertised Installation

    must be located in the SYSMGMT \srvadmin\windows\SystemsManagement. For more detailed information, go to msdn.microsoft.com and search for MEDIAPACKAGEPATH Property Does systems management Install support Windows Advertised installation? No. Systems management Install does not support Windows Advertised installation - the process of automatically distributing a program to client computers for installation, through the Windows group policies.
  • Page 85: Is The Time Shown During Installation Or Uninstallation By Windows Installer Services Accurate

    Where can I see the Server Administrator features that are currently installed on my system? Navigate to the Windows Control Panel and double-click Add/Remove Programs to view the Server Administrator features that are currently installed. What are the names of all the systems management features under Windows? The following table lists the names of all systems management features and their corresponding names in Windows.
  • Page 86: Red Hat Enterprise Linux Or Suse Linux Enterprise Server

    I see missing RPM file dependencies while installing Server Administrator? Server Administrator is a 32-bit application. When installed on a system running a 64-bit version of Red Hat Enterprise Linux operating system, the Server Administrator remains a 32-bit application, while the device drivers installed by Server Administrator are 64-bit.
  • Page 87: Where Can I Find The Source Packages For Open Source Rpms

    During uninstallation, error: %preun(srvadmin-NAME-X.Y.Z-N.i386) scriptlet failed, exit status 1 error message is displayed. There may be problems uninstalling Server Administrator after an unsuccessful upgrade during a manual RPM upgrade. The following error message is displayed: 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.
  • Page 88: Suse Linux Enterprise Server

    The following table lists the names of all systems management features and their corresponding init script names under Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems. Table 24. Systems Management Features — VMware ESX, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server Feature...
  • Page 89 Service Integration Layer — Provides srvadmin-hapi, srvadmin-isvc, and Instrumentation CLI. srvadmin-omacore srvadmin-omilcore Server Administrator Install Core — This is the core install package that provides the tools necessary for the rest of the Systems management install packages. All Server Administrator RPMs require this RPM.
  • Page 90 Storage Management — Provides srvadmin-omilcore, srvadmin-deng, Systems Management Storage and srvadmin-omacore Services. SA-WebServer — Provides web access to manage the server. srvadmin-hapi Server Administrator Hardware srvadmin-omilcore Application Programming Interface — This systems management package provides the device drivers and...
  • Page 91 Server Administrator. srvadmin-omilcore Server Administrator Web Server Install Core — This is the core install package. All Server Administrator Web Server RPMs require this RPM. srvadmin-wsmanclient Operating system specific WSMan srvadmin-omcommon and srvadmin- client package. omauth Remote-Enablement — Manage and monitor the current system using some other remote system.
  • Page 92: Administrator Installed

    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.
  • Page 93: What Happens If I Install The Rpm Package On An Unsupported System Or On An Unsupported Operating System

    Server Administrator is started? The daemons that run on Red Hat Enterprise Linux and SUSE Linux Enterprise Server operating systems depend on what is installed and what is enabled to run. The following table displays the daemons that typically run for a full install: Table 26.
  • Page 94: What Kernel Modules Are Loaded When Server Administrator Is Started

    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 27. Kernel Modules Loaded When Server Administrator Services are Started Driver Name Description...
  • Page 95: Linux Installer Packages

    Server srvadmin- Meta package for srvadmin- Server webserver installing the Server smcommon, Administrator Web Administrator Web srvadmin-smweb, Server for local and Server feature srvadmin-tomcat remote node management srvadmin- Meta package for srvadmin-cm, Storage storageservices installing the Server srvadmin-megalib, Management using...
  • Page 96 Server SNMP snmp contains base,srvadmin- feature dependency deng-snmp, information to srvadmin-isvc- automatically pull in snmp the Server Administrator Server SNMP feature srvadmin-server-cli Meta package that srvadmin-base, Server CLI feature contains srvadmin-omacore dependency information to automatically pull in the Server...
  • Page 97 Storage CLI feature N storageservices-cli contains srvadmin-storage- dependency information to automatically pull in the Server Administrator Storage CLI feature Table 29. Server Instrumentation and SNMP monitoring Description Required for Systems Management Software Dependant packages srvadmin- Core Install pciutils,smbi Installing omilcore...
  • Page 98 Description Required for Systems Management Software Dependant packages srvadmin- Provides srvadmin- Server isvc systems deng, Instrumentati management srvadmin- on and interface to omilcore SNMP local and monitoring remote systems management libsmbios Provides None Installation SMBIOS and software library to get...
  • Page 99 If required on a 64bit operatin system, manuall y install same. srvadmin- Management srvadmin- Replicating oslog interface omilcore Server Administrato r Events in OS Log srvadmin- Server srvadmin- Common omacs Administrato omcommon services r OMACS srvadmin- bundled in omilcore...
  • Page 100 Table 31. Server Administrator Web Server (GUI) for Local and Remote Management Description Dependant Required for Systems Management Software packages srvadmin-jre Provides srvadmin- Server JAVA omilcore Administrato Runtime for r GUI web server srvadmin- Server srvadmin- Server O*** Administrato omilcore,...
  • Page 101 Description Required for Systems Management Software Dependant packages provider that sblim-sfcb enables sblim-sfcc remote management of the server libwsman1 Openwsman None Openwsman libraries support used by library client and server components openwsman- Openwsman None Enabling server server and remote service...
  • Page 102 Interconnect * For Red Hat Enterprise management Express Linux 6.0 and libraries for Solid State SUSE Linux PCIeSS (PCIeSS) Enterprise Devices Devices Server 11 management srvadmin- Core srvadmin- Storage storage interface deng, instrumentati library for srvadmin- on, SNMP storage isvc,...
  • Page 103 *N/A for 64- bit OMSA installation, and VMware ESX. srvadmin- Common None Storage smcommon framework management or libraries using Server for GUI/CLI Administrato (for storage r GUI/CLI management srvadmin- GUI plugins srvadmin- Storage smweb for storage omcommon, management management...
  • Page 104 Server srvadmin- Server deng-snmp Administrato deng Administrato r SNMP r SNMP Framework Framework srvadmin- Server srvadmin- Server and isvc-snmp SNMP hapi, Operating module srvadmin- System isvc related SNMP Queries and SNMP Traps * — Obsolete - merged with srvadmin-storage ** — Not applicable for OM 7.0 supplemental pack for Citrix Xen 6.0.
  • Page 105 RAC CLI and None racdrsc Web Plugin management to Server using Server Administrato Administrator r for RAC 4, 5 GUI/CLI and iDRAC srvadmin- RAC SNMP None rac- components instrumentati components...
  • Page 106 Description Required for Systems Management Software Dependant packages srvadmin- RAC Data srvadmin- DRAC 4 rac4- populator for omilcore instrumentati populator- DRAC 4 srvadmin- Library for None RAC CLI tools argtable2 parsing GNU for RAC 5 and style iDRAC command management line argument.

This manual is also suitable for:

Server administrator 7.2

Table of Contents