Server Administrator Version 8.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. 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 © 2016 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.....................................................................................................................................................
Installing Managed System Software On Microsoft Windows Server 2008 Core And Microsoft Hyper-V Server................................................................................................ 31 Running Prerequisite Checker In CLI Mode.......................................................................................................................31 Installing Managed System Software In CLI Mode.....................................................................................................
I downloaded the Server Administrator files for Windows from the Support website and copied it to my own media. When I tried to launch the SysMgmt.msi file, it failed. What is wrong?........................................................... 47 Does systems management Install support Windows Advertised installation?............................................................47 How do I check the disk space availability during custom installation?..............................................................
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.
Component What is installed Deployment Scenario Systems to install on SNMP (Management Interface) Simple Network Management Protocol Interface of Server Instrumentation Install to provide local and remote system management solutions to manage Server and Storage instrumentation data using SNMP protocol. Supported systems. For a list of supported systems, see the Systems Software Support Matrix.
• User ID and password configuration through the web-based interface or the command line interface (CLI), in most cases. • SSL encryption (Auto Negotiate and 128-bit or higher). 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.
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 \SYS
Return Code Description —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. —7 An internal error has occurred. The prerequisite checker does not run. —8 The software is already running. 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.
p — Terminal property + — 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.
an existing X.509 certificate, or import a root certificate or certificate chain from a Certificate 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. Best Practices For X.
3. Click File → Add/Remove Snap-in. 4. Select Certificates, and then click Add. 5. In the Certificates snap-in dialog box, select Computer account, and then click Next. 6. Select Local Computer, and then click Finish. 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.
Configuring The Windows Firewall For WinRM To configure the Windows Firewall for WinRM: 1. Open Control Panel. 2. Click Windows Firewall. 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.
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.
You want to Select View the status of local and remote storage attached to a Storage Management. managed system and obtain storage management information in an integrated graphical view. Remotely access an inoperable system, receive alert notifications when a system is down, and remotely restart a system. DRAC Command Line Tools. NOTE: Install the Simple Network Management Protocol (SNMP) agent on the managed system using the operating system medium before installing the managed system software.
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
7. Click I accept the terms in the license agreement and then click Next. The Setup Type dialog box is displayed. 8. Select Custom and click Next. The Custom Setup dialog box is displayed. 9. Select the required software features you want to install on the system. 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.
Option 1: 1. Uninstall Server Administrator. 2. Install Citrix. 3. Reinstall Server Administrator. Option 2: After installing Citrix, type the command msiexec.exe /fa SysMgmt.msi 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.
Creating Custom Unattended Installation Packages To create a custom unattended installation package, perform the following steps: 1. Copy the SYSMGMT\srvadmin\windows directory from the DVD to the system hard drive. 2. Create a batch script that executes the installation using the Windows Installer Engine (msiexec.exe). NOTE: For Customized Unattended Installation, each required feature must be included as a command line interface (CLI) parameter for it to be installed. An example is msiexec.
Setting Result /x .msi – Uninstalls the Server Administrator software. For the product GUID, see Unattended Uninstall Using The Product GUID /q[n|b|r|f] This command sets the user interface (UI) level. /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.
Customization Parameters REINSTALL and REMOVE customization CLI parameters provide a way to customize the exact software features to install, reinstall, or uninstall when running a silent or unattended installation. With the customization parameters, you selectively install, reinstall, or uninstall software features for different systems using the same unattended installation package.
Feature ID Description SNMP Simple Network Management Protocol Interface of Server Instrumentation OSLOG Operating System Logging SA Installs SI, CLI, WMI, SNMP, OSLOG OMSM Installs SI, OMSS, CLI, WMI, SNMP, OSLOG NOTE: To manage the server, select either Server Administrator Webserver or one of the Management Interfaces – CLI, WMI, SNMP or OSLOG along with Server Instrumentation (SI) or Server Administrator Storage Management Service (OMSS).
Failed Updates Apply the MSI patches and updates provided by vendors 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 may fail. MSI packages must not be repackaged; doing so changes the feature structure and Globally Unique Identifier (GUID), which break any provided patches or updates. To make any changes to a vendor-provided MSI package, use a .mst transform 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. 3. Click the Install, Modify, Repair, or Remove Server Administrator option. The Welcome to the Install Wizard for Server Administrator screen is displayed. 4. Click Next. The Software License Agreement is displayed. 5.
The Program Maintenance dialog box is displayed. 5. Select the Repair option and click Next. The Ready to Repair the Program dialog box is displayed. 6. 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. 7. Click Finish to exit the Server Administrator installation.
3. Click Server Administrator, and then click Remove. The Add or Remove Programs dialog box is displayed. 4. 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: • Yes, reboot my system now. • No, I will reboot my system later All Server Administrator features are uninstalled.
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.
• 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 .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.
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: 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.
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.
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.ini file contains the following syntax if the Active Directory product name is configured to omsaApp.
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. 5. Click Finish.
dellOmsaAuxClass 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.
Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued Link ID: 12070 dellAssociationMembers 1.2.840.113556.1.8000.1280.1.1.2.14 List of dellAssociationObjectMembers that belong to this Product. This attribute is the backward link to the dellProductMembers Linked attribute. Distinguished Name (LDAPTYPE_DN 1.3.6.1.4.1.1466.115.121.1.12) FALSE Link ID: 12071 Table 16.
Opening The Active Directory Users And Computers Snap-In To open the Active Directory Users and Computers snap-in, perform the following steps: 1. If you are on the domain controller, click Start → Admin Tools → Active Directory Users and Computers. If you are not on the domain controller, you must have the appropriate Microsoft administrator pack installed on the local system. To install this administrator pack, click Start → Run, type MMC, and press . 2. Click File in the Console 1 window. 3.
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. Select the scope for the Association Object. 7.
Configuring Active Directory Using CLI On Systems Running Server Administrator You can use the omconfig preferences dirservice command to configure the Active Directory service. The productoem.ini file is modified to reflect these changes. If the adproductname is not present in the productoem.ini file, a default name is assigned.
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.
In this case, use the following command to create a HTTPS Listener with the CertificateThumbprint empty: winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="";CertificateThumbprint=""} What are the firewall-related configuration that needs to be done for WinRM? With firewall turned ON, WinRM must be added to the firewall exclusion list to allow TCP port 443 for HTTPS traffic.
I have installed Server Administrator using remote Server Administrator deploy on 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 key.
This error occurs when the prerequisite checker calls the systems management script, vbstest.vbs (a Visual Basic script), to verify the installation environment, and the script fails. The possible causes are: • Incorrect Internet Explorer Security Settings. Ensure that Tools → Internet Options → Security → Custom level → Scripting → Active scripting is set to Enable. Ensure that Tools → Internet Options → Security → Custom level → Scripting → Scripting of Java applets is set to Enable.
Table 18.
