Server Administrator Version 8.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. 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 Copyright © 2015 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction........................................................................................................... 6 What Is New In This Release................................................................................................................. 6 Software Availability.........................................................................................................................6 Systems Management Software.................................................................
Uninstalling Managed System Software............................................................................................. 33 Uninstalling Managed System Software Using The Provided Media...........................................33 Uninstalling Managed System Software Features Using The Operating System........................33 Unattended uninstall using the product GUID............................................................................
I am getting the following error message while launching systems management Install:........ 51 Do I need to uninstall previous versions of Server Administrator before installing Citrix Metaframe?....................................................................................................................................52 When I run systems management Install, I see unreadable characters on the Prerequisite check information screen......................................................................
Introduction 1 This topic provides information on: • Installing Server Administrator on managed systems. • Installing and using the Remote Enablement feature. • Managing remote systems using Server Administrator Web Server. • Configuring the system before and during a deployment or upgrade. NOTE: If you are installing management station and managed system software on the same system, install identical software versions to avoid system conflicts.
Server Administrator Components On A Managed System The setup program provides the following options: • Custom Setup • Typical Setup The custom setup option allows you to select the software components you want to install. The table lists the various managed system software components that you can install during a custom installation. Table 1.
Component What is installed Deployment Scenario Systems to install on Command Line Interface (Management Interface) Command Line Interface of Server Instrumentation Install to provide local and remote system management solutions to manage Server and Storage instrumentation data using commandline interfaces. Supported systems. For a list of supported systems, see the Systems Software Support Matrix.
Component What is installed Deployment Scenario Systems to install on event data and the most recent crash screen (available only on systems running Windows operating system) to help you diagnose the probable cause of a system crash. Intel SNMP Agent (NIC Interfaces) Intel Simple Network Management Protocol (SNMP) Agent Install to enable Server Administrator to obtain information about Intel Network Interface Cards (NICs).
• The Systems Build and Update Utility User’s Guide provides information on using the Systems Build and Update Utility. • The Systems Software Support Matrix provides information about the various systems, the operating systems supported by these systems, and the systems management components that can be installed on these systems. • The Server Administrator User's Guide describes the installation and use of Server Administrator.
2 Preinstallation Setup Ensure that you perform the following before installing Server Administrator: • Read the installation instructions for the operating system. • Read the Installation Requirements to ensure that the system meets or exceeds the minimum requirements. • Read the applicable readme files and the Systems Software Support Matrix. • Close all applications running on the system before installing the Server Administrator applications. Prerequisite Checker The setup.exe (available at \SY
Return Code Description 2 A warning condition, or conditions, is associated with the software. It is recommended that you resolve the conditions causing the warning before proceeding with the installation of the software. To continue, select and install the software using the custom installation. 3 An error condition, or conditions, is associated with the software. Resolve the conditions causing the error before proceeding with the installation of the software.
• Domain Name System (DNS) or Windows Internet Name Service (WINS) server running on the system can cause a warning condition for RAC software. See the relevant section in Server Administrator readme for more information. • Do not install managed system and management station RAC components on the same system. Install only the managed system RAC components, as they offer the required functionality.
The MUI Pack are a set of language-specific resource files that you can add to the English version of a supported Windows operating system. The installer supports only six languages: English, German, Spanish, French, Simplified Chinese, and Japanese. NOTE: When the MUI Pack is set to non-Unicode languages like Simplified Chinese, set the system locale to Simplified Chinese. This enables display of the prerequisite checker messages.
NOTE: For information about installing a supported systems management protocol standard on the managed system, see the operating system documentation. The following table shows the availability of the systems management standards for each supported operating system. Table 3. 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.
+ — Append to existing file ! — Flush each line to the log "*" — Wildcard, log all information except for the v option. To include the v option, specify "/l*v". Once activated, the log files are generated in the %TEMP% directory. Some log files generated in this directory are: • Managed System Installation – SysMgmt_.log These log files are created by default if the prerequisite checker user interface (UI) is running.
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. X.509 Certificate Management Web certificates are necessary to ensure that the identity and information exchanged with a remote system is not viewed or changed by others. To ensure system security, it is strongly recommended that you either generate a new X.509 certificate, reuse an existing X.
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 configure the Remote Enablement feature on the system. NOTE: It is recommended that you use a certificate signed by a CA. Using A Certificate Signed By A CA To use a certificate signed by a CA: 1. Request a valid CA signed certificate. 2. Create a HTTP listener with the CA signed certificate.
If you are using WinRM 2.0, type winrm configsddl default. 3. Click Add and add the required users or groups (local/domain) to the list. 4. Provide the appropriate permission(s) to the respective users and click OK. WMI To configure user authorization for WMI servers: 1. Click Start → Run. 2. Type wmimgmt.msc, and then click OK. The Windows Management Infrastructure (WMI) screen is displayed. 3. Right-click the WMI Control (Local) node in the left pane, and then click Properties.
Installing Managed System Software On Microsoft Windows Operating Systems 3 On Microsoft Windows, an autorun utility is displayed when you insert the Systems Management Tools and Documentation DVD. This utility allows you to choose the systems management software you want to install on the system. If the autorun program does not start automatically, use the autorun program from the DVD root or the setup program in the SYSMGMT\srvadmin\windows directory on the Systems Management Tools and Documentation DVD
You want to Select Manage and monitor the current system on the Windows Management Instrumentation Interface. Server Instrumentation and WMI. Manage and monitor the current system on the Simple Network Management Protocol Interface. Server Instrumentation and SNMP. Manage and monitor the current system from a remote system. Remote Enablement For systems running on Microsoft Windows, Remote Enablement is under the Server Instrumentation option.
NOTE: If you use the MSI file to try to install Server Administrator on a system where the User Account Control settings is set to a greater level, the installation fails and displays a message: Server Administrator installation program could not install the HAPI driver. You must perform the installation process as an administrator. You can also install Server Administrator successfully by the following methods: • Click the setup.
NOTE: You can change the alert message format from Traditional Message Format to Enhanced Message Format using the Custom Setup option. Custom Installation The sections that follow describe how to install Server Administrator and other managed system software using the Custom Setup option. NOTE: Management station and managed system services can be installed in the same or in different directories. You can select the directory for installation.
• Enhanced Message Format (Recommended) • Traditional Message Format The Ready to Install the Program dialog box is displayed. 12. 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. After the selected features are installed, the Install Wizard Completed dialog box is displayed. 13. Click Finish to exit the Server Administrator installation.
The unattended installation package is distributed to the remote systems using a software distribution tool from an independent software vendor (ISV). When the package is distributed, the installation script executes to install the software. Creating And Distributing The Typical Unattended Installation Package The Typical Setup unattended installation option uses the Systems Management Tools and Documentation DVD as the unattended installation package. The msiexec.exe /i .
Related Links: Customization Parameters Distributing Custom Unattended Installation Packages For distributing custom unattended installation packages: 1. Configure the ISV distribution software to execute the batch script once the installation package is distributed. 2. 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.
Setting Result /q or /qn – no UI. This option is used for silent and unattended installation. /qb – basic UI. This option is used for unattended but not silent installation. /qr – reduced UI. This option is used for unattended installation while displaying a modal dialog box showing install progress. /qf – full UI. This option is used for standard attended installation. /f[p|o|e|d|c|a|u |m|s|v] This command repairs a product.
Setting Result CP_MESSAGE_FORMAT= This command sets the alert message type to Enhanced Message Format (recommended) or Traditional Message Format. For example, running msiexec.exe /i SysMgmt.msi /qn installs Server Administrator features on each remote system based on the system's hardware configuration. This installation is done silently and unattended.
Feature ID Description OMSS Server Administrator Storage Management Service RAC4 DRAC Command Line Tools (RAC 4) RAC5 iDRAC (for DRAC Command Line Tools (RAC 5) 11th iDRAC12G (for servers) generation of PowerEdge servers) Integrated DRAC Command Line Tools 12th Integrated DRAC Command Line Tools generation of PowerEdge SI Server Instrumentation RmtMgmt Remote Enablement CLI Command Line Interface of Server Instrumentation WMI Windows Management Instrumentation Interface of Server Instru
overwritten files, registry keys, and other resources. Windows temporarily saves all files that it deletes or overwrites during the course of an installation or removal, so that they can be restored if necessary, which is a type of rollback. After a successful installation, Windows deletes all of the temporary backup files. In addition to the rollback of MSI Standard Actions, the library also has the ability to undo commands listed in the INI file for each application if a rollback occurs.
• You can upgrade to the latest version of Server Administrator which includes Linux granular installation. If you require the Linux granular installation options, you must uninstall the existing version of Server Administrator and install the latest version of Server Administrator. . • To upgrade from versions earlier than 6.3, uninstall the existing version of Server Administrator and reinstall the latest version of Server Administrator.
5. Select the Modify option and click Next. The Custom Setup dialog box is displayed. 6. To select a specific managed system software application, click the drop-down arrow beside the listed feature and select either This feature will be installed… to install the feature, or This feature will not be available to ignore the feature. A selected feature has a hard drive icon depicted next to it. A deselected feature has a red X next to it.
Uninstalling Managed System Software You can uninstall managed system software features by using the Systems Management Tools and Documentation DVD, or the operating system. You can simultaneously perform unattended uninstallation on multiple systems. Uninstalling Managed System Software Using The Provided Media Perform the following tasks to uninstall managed system software using the provided media. 1. Insert the Systems Management Tools and Documentation DVD into the system's DVD drive.
If you are prompted to reboot the system, select from the following reboot options: • Yes, reboot my system now. • No, I will reboot my system later All Server Administrator features are uninstalled. Unattended uninstall using the product GUID If you do not have the installation DVD or the MSI package available during an uninstallation, use the package GUIDs in the command line to uninstall systems management software on managed systems or management stations running Windows operating system.
4 Installing Managed System Software On Microsoft Windows Server 2008 Core And Microsoft Hyper-V Server 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 reduce the maintenance and management requirements and the attack surface for those server roles.
Installing Managed System Software In CLI Mode Launch the MSI file from the command prompt using the command msiexec /i .msi. To install the localized version of the managed system software, type msiexec /i .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.
Using Microsoft Active Directory 5 If you use Active Directory service software, configure it to control access to the network. The Active Directory database is modified to support remote management authentication and authorization. Server Administrator, as well as Integrated Remote Access Controllers (iDRAC), Remote Access Controllers (RAC), can now interface with Active Directory. With this tool, you can add and control users and privileges from one central database.
represents the system. The Association Object links it with users and privileges. You can create as many Association Objects as you need. Each Association Object can be linked to as many users, groups of users, and Product Objects as required. The users and Product Objects can be from any domain. However, each Association Object may only link to one Privilege Object. This behavior allows an administrator to control users and their rights on specific systems.
The following figure shows the set up of the Active Directory objects in a single domain. In this scenario, 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 administrator privilege on both DRAC 4 cards and give User3 login privilege on the RAC2 card. Figure 2.
Figure 3. Setting Up RAC Active Directory Objects In Multiple Domains Setting Up RAC Active Directory Objects In Multiple Domain To set up the objects for this multiple domain scenario, perform the following tasks: 1. Ensure that the domain forest function is in Native mode. 2. Create two Association Objects, AO1 (of Universal scope) and AO2, in any domain. 3. Create two RAC Device Objects, RAC1 and RAC2, to represent the two remote systems. 4.
Figure 4. Setting up Server Administrator Active Directory Objects In Multiple Domains Setting Up Server Administrator Active Directory Objects For Multiple Domain To set up the objects for this multiple domain scenario, perform the following tasks: 1. Ensure that the domain forest function is in Native mode. 2. Create two Association Objects, AO1 and AO2, in any domain. The figure shows the objects in Domain1. 3. Create two Server Administrator Products, sys1 and sys2, to represent the two systems.
• Installing the Extension to the Active Directory Users and Computers Snap-In • Adding Users and Privileges to Active Directory • Configuring the Systems or Devices Configuring The Active Directory Product Name To configure the Active Directory product name: 1. Locate the omsaoem.ini file in the installation directory. 2. Edit the file to add the line adproductname=text, where text is the name of the product object that you created in Active Directory. For example, the omsaoem.
Folder Name Installation Type NOTE: Only iDRAC6 is supported on xx1x systems and iDRAC7 is supported on xx2X systems. To use the LDIF files, see the instructions in the readme that is in the LDIF files directory. To use the Schema Extender to extend the Active Directory Schema, perform the steps in Using the Dell Schema Extender. Copy and run the Schema Extender or LDIF files from any location.
Table 10. dellAssociationObject Class OID 1.2.840.113556.1.8000.1280.1.1.1.2 Description This class represents the Dell Association Object. The Association Object provides the connection between the users and the devices or products. Class Type Structural Class SuperClasses Group Attributes dellProductMembers dellPrivilegeMember Table 11. dellPrivileges Class OID 1.2.840.113556.1.8000.1280.1.1.1.
dellOmsaIsReadWriteUser dellOmsaIsAdminUser Table 14. 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 15.
Table 16. Server Administrator-Specific Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued dellOMSAIsReadOnlyUser 1.2.840.113556.1.8000.1280.1.2. TRUE TRUE if the User has Read-Only 2.1 rights in Server Administrator Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.121.1.7) dellOMSAIsReadWriteUser 1.2.840.113556.1.8000.1280.1.2. TRUE TRUE if the User has Read-Write 2.2 rights in Server Administrator Boolean (LDAPTYPE_BOOLEAN 1.
administrator pack installed on the local system. To install this administrator pack, click Start → Run, type MMC, and press . 2. Click File in the Console 1 window. 3. Click Add/Remove Snap-in. 4. Click Add. 5. Select the Active Directory Users and Computers snap-in and click Add. 6. Click Close and click OK.
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. 1. In the Console Root (MMC) window, right-click a container. 2. Select New. 3. Select a RAC or Server Administrator object, depending on what you have installed. The New Object window is displayed. 4. Type in a name for the new object. 5. Select Association Object. 6.
Configuring The Systems Or Devices For instructions on configuring the Server Administrator systems using CLI commands, see Configuring Active Directory Using CLI on Systems Running Server Administrator. For DRAC users, see the Remote Access Controller 4 User’s Guide or Remote Access Controller 5 User’s Guide. For iDRAC users, see the Integrated Remote Access Controller User's Guide.
Frequently Asked Questions 6 What ports do systems management applications use? The default port used by Server Administrator is 1311. These ports are configurable. For port information of a particular component, see the User Guide of that respective component.
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/enus/library/cc782312.aspx.
Do I need to uninstall previous versions of Server Administrator before installing Citrix Metaframe? Yes. Uninstall previous versions of Server Administrator before installing Citrix Metaframe (all versions). As errors may exist in the registry after the Citrix Metaframe installation, you must reinstall Server Administrator. When I run systems management Install, I see unreadable characters on the Prerequisite check information screen.
same. The SysMgmt.msi file 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.
• b. Look for the VBS file extension and ensure that File Types is set to VBScript Script File. c. If not, click Change and choose Microsoft Windows Based Script Host as the application that gets invoked to run the script. WSH is the wrong version, corrupted, or not installed. WSH is installed during operating system installation, by default. Download WSH from msdn.microsoft.com. Is the time shown during installation or uninstallation by Windows Installer Services accurate? No.
Feature Name in WIndows Server Administrator DSM SA Connection Service DSM SA Shared Services Server Administrator Storage Management Service Mr2kserv Remote Access Controller Console (DRAC 4) Remote Access Controller 4 (DRAC 4) 55
