Server Administrator Version 8.4 Installation Guide — Microsoft Windows October 2016 Rev.
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 © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction................................................................................................................. 5 What Is New In This Release............................................................................................................................................ 5 Software Availability.....................................................................................................................................................
Chapter 4: Installing Managed System Software On Microsoft Windows Server 2008 Core And Microsoft Hyper-V Server................................................................................................. 30 Running Prerequisite Checker In CLI Mode................................................................................................................30 Installing Managed System Software In CLI Mode..................................................................................................
1 Introduction 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.
Table 1. Managed System Software Components Component What is installed Deployment Scenario Systems to install on Remote Enablement (Management Interface) Instrumentation Service and CIM Provider Install to perform remote systems management tasks. Install Remote Enablement on one system and Server Administrator Web Server on another system. You can use the system with the Server Administrator to remotely monitor and manage the systems which have Remote Enablement installed. Supported systems.
NOTE: Telnet does not support SSL encryption. ● Session time-out configuration (in minutes) through the web-based interface. ● Port configuration to allow systems management software to connect to a remote device through firewalls. NOTE: For information about ports that the various systems management components use, see the User Guide for that component. For information about the Security Management, see the Server Administrator User’s Guide at dell.com/ openmanagemanuals.
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.
Table 2. Return Codes While Running the Prerequisite Checker Silently Return Code Description —2 The operating system is not supported. The prerequisite checker does not run. —3 The user does not have Administrator privileges. The prerequisite checker does not run. —4 Not an implemented return code. —5 The prerequisite checker does not run. The user failed to change the working directory to %TEMP%. —6 The destination directory does not exist. The prerequisite checker does not run.
NOTE: Prerequisites specific to an operating system are listed as part of the installation procedures. Supported Operating Systems And Web Browsers For information on supported operating systems and web browsers, see the Systems Software Support Matrix . NOTE: Ensure that the web browser is configured to bypass the proxy server for local addresses.
Supported Systems Management Protocol Standards Install a supported systems management protocol on the managed system before installing the management station or managed system software. On supported Windows operating system, systems management software supports: ● Common Information Model (CIM)/Windows Management Instrumentation (WMI) ● Simple Network Management Protocol (SNMP) Install the SNMP package provided with the operating system.
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. Microsoft Active Directory If you use Active Directory service software, you can configure it to control access to the network. The Active Directory database is modified to support remote management authentication and authorization.
Best Practices For X.509 Certificate Management For the security of the system while using server administrator, ensure the following: Unique host name All systems that have Server Administrator installed should have unique host names. Change 'localhost' to unique For systems with host name set to localhost change the host name to a unique host name.
7. Click Close, and then click OK. 8. On the Console window, expand Certificates (Local Computer) in the left navigation pane. 9. Right-click Personal, select All tasks > Request New Certificate. 10. Click Next. 11. Select the appropriate certificate type, Mostly (Computer), and then click Enroll. 12. Click Finish. Creating The HTTPS Listener With The Valid CA Signed Certificate Run the installer and click the link on the prerequisite checker to create the HTTPS listener.
3. Click Exceptions tab. 4. Select Windows Remote Management check box. If you do not see the check box, click Add Program to add Windows Remote Management. Configuring The Envelope Size For WinRM To configure the envelope size for WinRM: NOTE: On WinRM version 2.0, enable the compatibility mode for WinRM version 2.0 to use port 443. WinRM version 2.0 uses port 5986 by default.
3 Installing Managed System Software On Microsoft Windows Operating Systems 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.
Table 4. Deployment Scenarios You want to Select You must then install the Server Administrator Web Server on the remote system. 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. DRAC Command Line Tools.
Typical Installation When you access 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 Storage Management Command Line Interface WMI SNMP Operating System Logging DRAC Command Line Tools Intel SNMP Agent Broadcom SNMP Agent QLogic SNMP Agent During a Typical installation, individual management station
If you are installing Server Administrator on an unsupported system, the installer displays only the Server Administrator Web Server option. A selected feature has a hard drive icon depicted next to it. A feature that is not selected has a red X depicted next to it. By default, if the prerequisite checker finds a software feature with no supporting hardware, the prerequisite checker automatically ignores the feature. To accept the default directory path to install managed system software, click Next.
Performing An Unattended Installation Of Managed System Software The Systems Management installer features a Typical Setup option and a Custom Setup option for the unattended installation procedure. Unattended installation enables you to simultaneously install Server Administrator on multiple systems. Perform an unattended installation by creating a package that contains the necessary managed system software files.
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.
Table 5. Command Line Settings for MSI Installer Setting Result /f[p|o|e|d|c|a|u |m|s|v] This command repairs a product. /fp – This option reinstalls a product if a file is missing. /fo – This option reinstalls a product if a file is missing or if an older version of a file is installed. /fe – This option reinstalls a product if a file is missing or an equal or older version of a file is installed.
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. The following table provides the list of feature IDs for each software feature. NOTE: The software feature IDs mentioned in the table are case-sensitive. Table 6.
Table 7. Windows Installer Return Codes Error Code Value Description ERROR_SUCCESS_REBOOT_REQUIRED 3010 A restart is required to complete the installation. This message is indicative of a successful installation. NOTE: For more information on all the error codes returned by the msiexec.exe and InstMsi.exe Windows Installer functions, see support.microsoft.com.
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.3 is supported only for Server Administrator versions 7.0 and later. ● You can upgrade to the latest version of Server Administrator which includes Linux granular installation.
7. Click Next to accept the selected software features for installation. The Ready to Modify the Program dialog box is displayed. 8. Click Install to install the selected software features. The Installing Server Administrator screen is displayed. Messages give the status and progress of the software features being installed. When the selected features are installed, the Install Wizard Completed dialog box is displayed. 9. Click Finish to exit the Server Administrator installation.
This dialog enables you to modify, repair, or remove the program. The Program Maintenance dialog box is displayed. 4. Select the Remove option and click Next. The Remove the Program dialog box is displayed. 5. Click Remove. The Uninstalling Server Administrator screen is displayed and provides the status and progress of the software features being uninstalled. When the selected features are uninstalled, the Install Wizard Completed dialog box is displayed. 6.
Distributing The Unattended Uninstallation Package The 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: 1. Configure the ISV distribution software to execute the msiexec.exe /x DVD Drive\<32–bit or 64–bit MSI path on the DVD>/qb command, if you are using the DVD, after the unattended uninstallation package has been distributed. 2.
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.
● ● ● ● 1034.mst 1036.mst 1041.mst 2052.mst (Spanish) (French) (Japanese) (Simplified Chinese) Related Links: Optional Command Line Settings Uninstalling Systems Management Software To uninstall managed system software, type msiexec /x .msi at the command prompt.
5 Using Microsoft Active Directory 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.
Figure 1. Typical Setup for Active Directory Objects 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. The following figure shows the set up of the 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: 1. Create two Association Objects. 2. Create two RAC Product Objects, RAC1 and RAC2, to represent the two DRAC 4 cards. 3. Create two Privilege Objects, Priv1 and Priv2, in which Priv1 has all privileges (administrator) and Priv2 has login privileges. 4. Group User1 and User2 into Group1. 5.
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. Instead of RAC devices, you will have two systems running Server Administrator (Server Administrator Products sys1 and sys2). sys1 and sys2 are in different domains.
● ● ● ● Extending the Active Directory Schema 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.
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. 1. Click Next on the Welcome screen. 2. Read the warning and click Next. 3. Select Use Current Log In Credentials or enter a user name and password with schema administrator rights. 4. Click Next to run the Dell Schema Extender.
Table 12. 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 13. dellOmsa2AuxClass Class OID 1.2.840.113556.1.8000.1280.1.2.1.1 Description This class is used to define the privileges (Authorization Rights) for Server Administrator.
Table 15. General Attributes Added to the Active Directory Schema Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued Link ID: 12071 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.2.1 TRUE TRUE if the User has Read-Only rights in Server Administrator Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.1466.115.
5. Select the Active Directory Users and Computers snap-in and click Add. 6. Click Close and click OK. 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.
Adding Objects To An Association Object By using the Association Object Properties window, you can associate users or user groups, privilege objects, systems, RAC devices, and system or device groups. NOTE: RAC users must use Universal Groups to span domains with their users or RAC objects. You can add groups of Users and Products. You can create related groups in the same way that you created other groups. To Add Users Or User Groups 1. Right-click the Association Object and select Properties. 2.
The following table shows the valid parameters for the command. Table 17. Active Directory Service Configuration Parameters name=value pair Description prodname= Specifies the software product to which you want to apply the Active Directory configuration changes. Prodname refers to the name of the product defined in omprv32.ini. For Server Administrator, it is omsa. enable= true: Enables Active Directory service authentication support.
6 Frequently Asked Questions 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/en-us/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.
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.
● 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. During installation or 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.
Table 18.
