Server Administrator Version 7.4 Installation Guide - Microsoft Windows April 2014 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. NOTE: A WARNING indicates a potential for property damage, personal injury, or death. Copyright © 2014 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction................................................................................................................................. 5 What Is New In This Release................................................................................................................................................5 Software Availability........................................................................................................................................................
Installing Managed System Software On Microsoft Windows Server 2008 Core And Microsoft Hyper-V Server..........................................................................................................................29 Running Prerequisite Checker In CLI Mode..................................................................................................................... 29 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.
Software Availability The Server Administrator software can be installed from: • • Systems Management Tools and Documentation DVD Support site — For more information, see dell.com/support. Systems Management Software Systems management software is a suite of applications that enables you to manage the systems with proactive monitoring, notification, and remote access.
Table 1. Managed System Software Components(continued) Component What is installed Deployment Scenario Systems to install on Administrator Storage Management User’s Guide in the docs directory. 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 command-line interfaces. Supported systems.
Security Features Systems management software components provide these security features: • • • Authentication for users from operating system with different privilege levels, or by using the optional Microsoft Active Directory. 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.
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(continued) Return Code Description the installation of the software. If you do not resolve the issues, the software is not installed. —1 A Microsoft Windows Script Host (WSH) error. The prerequisite checker does not run. —2 The operating system is not supported. 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.
Related Link Customization Parameters Installation Requirements This section describes the general requirements of the Server Administrator and provides information on supported operating systems and web browsers. 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 .
• The Server Administrator Storage Management Service requires Server Administrator installed on the managed system. See the Server Administrator Storage Management User’s Guide for complete software and hardware requirements. Related Link: Supported Systems Management Protocol Standards Install a supported systems management protocol on the managed system before installing the management station or managed system software.
! — 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.
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' For systems with host name set to localhost change the host name to a unique host name.
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. NOTE: The HTTP listener is enabled by default and listens at port 80. Configuring User Authorization For WinRM And WMI Servers To provide access rights to WinRM and WMI services, explicitly add users with the appropriate access levels. NOTE: To configure user authorization - For WinRM and WMI Servers, you must login with administrator privileges.
3. Check the value of the MaxEnvelopeSizekb attribute. If the value is less than 4608, type the following command: winrm s winrm/config @{MaxEnvelopeSizekb="4608"} 4.
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(continued) 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.
• • • • • • • • • • 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 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.
• • Yes, reboot my system now. No, I will reboot my system later. NOTE: If you have selected Remote Enablement during installation, an error message A provider, WinTunnel, has been registered in the Windows Management Instrumentation namespace ROOT\dcim\sysman to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. is logged in Windows Event Log.
Distributing The Entire DVD as The Typical Unattended Installation Package 1. Distribute the entire image of the Systems Management Tools and Documentation DVD to the target systems. 2. Configure the ISV distribution software to execute the msiexec.exe /i DVD Drive\<32–bit or 64–bit MSI path on the DVD>/qb command from the DVD image. The program executes to install Server Administrator on each remote system. 3. Reboot each remote system to enable Server Administrator.
Table 5. Command Line Settings for MSI Installer(continued) Setting Result /x .msi – Uninstalls the Server Administrator software. /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. This option is used for unattended installation while displaying a modal dialog box showing install progress.
This command runs the installation for Systems Management and reinstalls only the Broadcom agent, in an unattended but not silent mode. You can include the REMOVE customization parameter on the command line and assign the feature ID (IDs) of the software feature that you want to uninstall. For example, msiexec.exe /i SysMgmt.msi REMOVE=BRCM /qb This command runs the installation for Systems Management and uninstalls only the Broadcom agent, in an unattended but not silent mode.
Table 7. Windows Installer Return Codes Error Code Value Description ERROR_SUCCESS 0 The action is completed successfully. ERROR_INVALID_PARAMETER 87 One of the parameters was invalid. ERROR_INSTALL_USEREXIT 1602 The user canceled the installation. 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.
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.
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. If you are prompted to reboot the system, select from the following reboot options to make the managed system software services available for use: • • Yes, reboot my system now. No, I will reboot my system later.
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. Click Finish to exit the Server Administrator uninstallation. If you are prompted to reboot the system, select from the following reboot options: • • Yes, reboot my system now.
Unattended Uninstall Command Line Settings The Command Line Settings for MSI Installer table shows the unattended uninstall command line settings available for unattended uninstallation. Type the optional settings on the command line after msiexec.exe /x .msi with a space between each setting. For example, running msiexec.exe /x SysMgmt.msi /qb runs the unattended uninstallation, and displays the unattended uninstallation status while it is running. Running msiexec.
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.
• 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.
Setting Up Objects In A Single Domain To set up the objects in a single domain scenario, perform the following tasks: 1. 2. 3. 4. 5. 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. Group User1 and User2 into Group1.
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.
• 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.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. 2. 3. 4. 5. Click Next on the Welcome screen. Read the warning and click Next. Select Use Current Log In Credentials or enter a user name and password with schema administrator rights. Click Next to run the Dell Schema Extender. Click Finish.
Table 12. dellProduct Class(continued) 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. Class Type Auxiliary Class SuperClasses None Attributes dellOmsaIsReadOnlyUser dellOmsaIsReadWriteUser dellOmsaIsAdminUser Table 14. dellOmsaApplication Class OID 1.2.840.113556.1.8000.1280.1.2.1.
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 if the User has Read-Only 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.2.2 TRUE if the User has Read-Write rights in Server Administrator Boolean (LDAPTYPE_BOOLEAN 1.3.6.1.4.1.
Creating A Product Object To create a Product Object: NOTE: Server Administrator users must use Universal-type Product Groups to span domains with their product objects. NOTE: When adding Universal-type Product Groups from separate domains, create an Association object with Universal scope. The default Association objects created by the Schema Extender utility are domain Local Groups and do not work with Universal-type Product Groups from other domains. 1.
Click the Privilege Object tab to add the privilege object to the association that defines the user’s or user group’s privileges when authenticating to a system. NOTE: Add only one Privilege Object to an Association Object. To Add A Privilege 1. Select the Privileges Object tab and click Add. 2. Type the Privilege Object name or browse and click OK. Click the Products tab to add one or more systems or devices to the association.
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.
NOTE: If you installed Server Administrator in a non-default directory, make sure to change it in Custom Setup as well. Once the application is installed, you can uninstall it from Add/Remove Programs.
I am getting the following error message while launching systems management Install: An older version of Server Administrator software is detected on this system. You must uninstall all previous versions of Server Administrator applications before installing this version If you see this error when trying to launch systems management Install, it is recommended that you run the OMClean.exe program, under the SYSMGMT\srvadmin\support\OMClean directory, to remove an older version of Server Administrator on the
Where can I find the MSI log files? By default, the MSI log files are stored in the path defined by the %TEMP% environment variable. 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? MSI requires all installers to specify the MEDIAPACKAGEPATH property if the MSI file does not reside on the root of the DVD. This property is set to SYSMGMT\srvadmin\windows\SystemsManagement for
In the Prerequisite Checker screen, I get the following message. What can I do to resolve this problem? An error occurred while attempting to execute a Visual Basic Script. Please confirm that Visual Basic files are installed correctly. 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.
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. Table 18.
