Dell Openmanage Server Administrator 8.4 Install Guide2 en Us
Dell Openmanage Server Administrator 8.4 Install Guide2 en Us
Dell Openmanage Server Administrator 8.4 Install Guide2 en Us
4
Installation Guide — Microsoft Windows
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. Dell and the Dell
logo are trademarks of Dell Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of
their respective companies.
2016 - 10
Rev. A00
Contents
1 Introduction.....................................................................................................................6
What Is New In This Release.............................................................................................................................................. 6
Software Availability..................................................................................................................................................... 6
Systems Management Software........................................................................................................................................ 6
Server Administrator Components On A Managed System.......................................................................................... 7
Security Features............................................................................................................................................................... 8
Other Documents You Might Need.................................................................................................................................... 9
2 Preinstallation Setup..................................................................................................... 10
Prerequisite Checker.........................................................................................................................................................10
Installation Requirements...................................................................................................................................................11
Supported Operating Systems And Web Browsers.....................................................................................................12
Multilingual User Interface Support.............................................................................................................................12
Viewing Localized Versions Of The Web-Based Interface...........................................................................................12
System Requirements................................................................................................................................................. 12
Digital Certificates.......................................................................................................................................................13
Enabling Windows Installer Logging Service................................................................................................................13
Microsoft Active Directory..........................................................................................................................................14
Configuring SNMP Agents................................................................................................................................................14
Secure Port Server And Security Setup............................................................................................................................14
Setting User And Server Preferences......................................................................................................................... 14
X.509 Certificate Management...................................................................................................................................14
Remote Enablement Requirements...................................................................................................................................15
Installing WinRM......................................................................................................................................................... 15
Certificate Authority Signed Self-Signed Certificate...................................................................................................15
3
4 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............................................................................................................ 31
Uninstalling Systems Management Software................................................................................................................... 32
4
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?....................................................................... 47
What do I do when I see the current version is already installed message is displayed?............................................. 47
What is the best way to use the prerequisite checker information?........................................................................... 47
In the Prerequisite Checker screen, I get the following message. What can I do to resolve this problem?................. 47
Is the time shown during installation or uninstallation by Windows Installer Services accurate?.................................48
Can I launch my installation without running the prerequisite checker? How do I do that?........................................ 48
How do I know what version of systems management software is installed on the system?..................................... 48
Do I need to reboot the system after upgrading systems management ?.................................................................. 48
Where can I see the Server Administrator features that are currently installed on my system?................................. 48
What are the names of all the systems management features under Windows?....................................................... 48
5
1
Introduction
This topic provides information on:
NOTE: If you are installing management station and managed system software on the same system, install identical
software versions to avoid system conflicts.
NOTE: For the list of supported operating systems and servers, see the OpenManage Software Support Matrix in the
required version of OpenManage Software at dell.com/openmanagemanuals.
Software Availability
The Server Administrator software can be installed from:
NOTE: For more information on these DVDs, see Systems Management Tools And Documentation <Version Number>
Installation Guide.
6
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.
Storage Management Server Administrator Storage Install to implement hardware Only those systems on which
Management RAID solutions and configure you have installed Server
the storage components Instrumentation or the
attached to the system. For Management Interfaces.
more information on Storage
Management, see the Server
Administrator Storage
Management User’s Guide in
the docs directory.
Command Line Interface Command Line Interface of Install to provide local and Supported systems. For a list
(Management Interface) Server Instrumentation remote system management of supported systems, see the
solutions to manage Server Systems Software Support
and Storage instrumentation Matrix.
data using command-line
interfaces.
WMI (Management Interface) Windows Management Install to provide local and Supported systems. For a list
Instrumentation Interface of remote system management of supported systems, see the
Server Instrumentation solutions to manage Server Systems Software Support
data using WMI protocol. Matrix.
7
Component What is installed Deployment Scenario Systems to install on
SNMP (Management Simple Network Management Install to provide local and Supported systems. For a list
Interface) Protocol Interface of Server remote system management of supported systems, see the
Instrumentation solutions to manage Server Systems Software Support
and Storage instrumentation Matrix.
data using SNMP protocol.
Remote Enablement Instrumentation Service and Install to perform remote Supported systems. For a list
(Management Interface) CIM Provider systems management tasks. of supported systems, see the
Install Remote Enablement on Systems Software Support
one system and Server Matrix.
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.
Operating System Logging Operating System Logging Install to allow local system Supported systems. For a list
(Management Interface) management-specific events of supported systems, see the
logging on the operating Systems Software Support
system for Server and Storage Matrix.
instrumentation. On systems
running Microsoft Windows,
use the Event Viewer to locally
view the collected events.
DRAC Command Line Tools Hardware application Install to receive email alerts Only those systems on which
programming interface and for warnings or errors related you have installed Server
iDRAC 12G or iDRAC, DRAC 5, to voltage, temperature, and Instrumentation or
or DRAC 4 (depending on the fan speed. Remote Access Management Interface.
type of the system) Controller also logs 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 Intel Simple Network Install to enable Server Only on systems on which
Interfaces) Management Protocol Administrator to obtain Server Instrumentation is
(SNMP) Agent information about Intel installed and which are running
Network Interface Cards on Windows operating system.
(NICs).
Broadcom SNMP Agent (NIC Broadcom SNMP Agent Install to enable Server Only on systems on which
Interfaces) Administrator to obtain Server Instrumentation is
information about Broadcom installed and which are running
NICs. on Windows operating system.
QLogic SNMP Agent (NIC QLogic SNMP Agent Install to enable Server Only on systems on which
Interfaces) Administrator to obtain Server Instrumentation is
information about QLogic installed and which are running
NICs. on Windows operating system.
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.
8
• 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: 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.
• The Lifecycle Controller 2 Version 1.00.00 User's Guide provides information on using the Lifecycle Controller.
• The Management Console User’s Guide provides information about installing, configuring, and using Management Console.
• 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.
• The Server Administrator SNMP Reference Guide documents the SNMP management information base (MIB).
• The Server Administrator CIM Reference Guide documents the Common Information Model (CIM) provider, which is an
extension of the standard management object format (MOF) file. This guide explains the supported classes of management
objects.
• The Server Administrator Messages Reference Guide lists the messages that are displayed on the Server Administrator home
page Alert log, or on the operating system’s event viewer. This guide explains the text, severity, and cause of each alert
message that the Server Administrator displays.
• The 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.
• The Remote Access Controller 5 User’s Guide provides complete information about installing and configuring a DRAC 5
controller and using DRAC 5 to remotely access an inoperable system.
• The Integrated Remote Access Controller User's Guide provides complete information about configuring and using an integrated
Remote Access Controller to remotely manage and monitor the system and its shared resources through a network.
• The Update Packages User's Guide provides information about obtaining and using the Update Packages for Windows and
Linux as part of the system update strategy.
• The Server Update Utility User's Guide provides information on using the Server Update Utility.
• The Systems Management Tools and Documentation DVD contains readme files for applications found on the media.
NOTE: If the product does not perform as expected or you do not understand a procedure described in this guide, see
Getting Help in the system’s Hardware Owner’s Manual.
9
2
Preinstallation Setup
Ensure that you perform the following before installing Server Administrator:
Prerequisite Checker
The setup.exe (available at \SYSMGMT\srvadmin\windows) starts the prerequisite checker program. The prerequisite checker
program examines the prerequisites for software components without launching the actual installation. This program displays a
status window that provides information about the system’s hardware and software that may affect the installation and operation
of software features.
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.
Run the prerequisite checker silently by running runprereqchecks.exe /s from the SYSMGMT\srvadmin\windows
\PreReqCheckerdirectory on the Systems Management Tools and Documentation DVD. After running the prerequisite checker, an
HTML file (omprereq.htm) is created in the %Temp% directory. This file contains the results of the prerequisite check. The Temp
directory is at X:\Documents and Settings\username\Local Settings\Temp. To find %TEMP%, go to a command-line prompt
and type echo %TEMP%.
The results are written under the HKEY_LOCAL_MACHINE\Software\Dell Computer Corporation\OpenManage \PreReqChecks
\MN\ key for a managed system:
While running the prerequisite checker silently, the return code from runprereqchecks.exe is the number associated with the
highest severity condition for all the software products. The return code numbers are the same as those used in the registry. The
following table details the return codes.
10
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.
—9 The WSH is corrupted, is a wrong version, or is not installed. The prerequisite checker does not run.
—10 An error has occurred with the scripting environment. The prerequisite checker does not run.
NOTE: A negative return code (-1 through -10) indicates a failure in running the prerequisite checker tool. Probable
causes for negative return codes include software policy restrictions, script restrictions, lack of folder permissions, and
size constraints.
NOTE: If you encounter a return code of 2 or 3, it is recommended that you inspect the omprereq.htm file in the
windows temporary folder %TEMP%. To find %TEMP%, run echo %TEMP%.
• One of the storage controllers or drivers has outdated firmware or driver. See firmwaredriverversions_<lang>.html (where <
lang > stands for language) or firmwaredriverversions.txt found in the %TEMP% folder. To find %TEMP%, run echo %TEMP
%.
• RAC component software version 4 is not selected for a default install unless the device is detected on the system. The
prerequisite checker generates a warning message in this case.
• Intel, Broadcom, and QLogic agents are selected for a default install only if the corresponding devices are detected on the
system. 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.
• 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.
Common causes for a return code of 3 (failure) from the prerequisite checker:
• You are not logged in as a built-in Administrator, Domain Administrator, or user who is a part of Domain Admins and Domain
Users group.
• The MSI package is corrupt or one of the required XML files is corrupt.
• Error during copying from a DVD or network access problems while copying from a network share.
• Prerequisite checker detects that another MSI package installation is running or that a reboot is pending:
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\Windows\CurrentVersion\Installer\InProgress indicates that another MSI
package installation is in progress. HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\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.
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.
11
NOTE: Prerequisites specific to an operating system are listed as part of the installation procedures.
NOTE: Ensure that the web browser is configured to bypass the proxy server for local addresses.
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. This is because any non-Unicode application runs
only when the system locale (also called Language for non-Unicode Programs on XP) is set to match the application's
language.
System Requirements
Install Server Administrator on each system to be managed. You can manage systems running Server Administrator locally or
remotely through a supported web browser.
Related Link:
12
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. If SNMP is installed post Server Administrator installation, restart
Server Administrator services.
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.
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.
To enable this logging service during a silent install, open the registry editor and create the following path and keys:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmup
The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as
follows for MSI version 3.1:
v — Verbose output
o — Out-of-disk-space message
i —Status message
c — Initial UI parameter
w — Non-fatal warning
a — Startup of action
r — Action-specific record
u — User request
13
p — Terminal property
"*" — 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:
Related Links:
Configure the SNMP agent to change the community name, enable set operations, and send traps to a management station. To
configure the SNMP agent for proper interaction with management applications, perform the procedures described in the Server
Administrator User’s Guide.
Related Links:
• Installation Requirements
• Supported Systems Management Protocol Standards
14
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.
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.
Unique host name All systems that have Server Administrator installed should have unique host names.
Change 'localhost' to For systems with host name set to localhost change the host name to a unique host name.
unique
• Microsoft Windows
• Microsoft Hyper-V
• Hyper-V Server
• Citrix XenServer
To install the Remote Enablement feature, configure the following on the system:
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.
15
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. Select the appropriate certificate type, Mostly (Computer), and then click Enroll.
12. Click Finish.
NOTE: The HTTP listener is enabled by default and listens at port 80.
NOTE: To configure user authorization — For WinRM and WMI Servers, you must login with administrator privileges. -
For Windows Server 2008 operating systems, you must login as a built-in Administrator, Domain Administrator, or user
who is a part of Domain Admins and Domain Users group.
NOTE: The administrator is configured by default.
WinRM
To configure user authorization for WinRM servers:
WMI
To configure user authorization for WMI servers:
16
Configuring The Windows Firewall For WinRM
To configure the Windows Firewall for WinRM:
17
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. See the Systems Software
Support Matrix for a list of operating systems currently supported.
NOTE: Use the Systems Management Tools and Documentation DVD to perform an unattended and scripted silent
installation of the managed system software. Install and uninstall the features from the command line.
• Install the Server Administrator Web Server on any system (laptop, or desktop) and the Server Instrumentation on another
supported system.
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.
• Continue to install the Server Administrator Web Server and the Server Instrumentation on the same system.
The following table lists the deployment scenarios for installing and using Server Administrator and helps you make the right choice
while selecting the various installation options:
18
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 DRAC Command Line Tools.
notifications when a system is down, and remotely restart a
system.
NOTE: Install the Simple Network Management Protocol (SNMP) agent on the managed system using the operating
system medium before installing the managed system software.
Installer Location
The location of the installers for 32–bit and 64–bit are:
NOTE: You cannot install both 32–bit and 64–bit installers on the same system.
• Using the setup program at \SYSMGMT\srvadmin\windows on the Systems Management Tools and Documentation DVD.
• Using the unattended installation method through the Windows Installer Engine msiexec.exe.
NOTE: SNMP service is stopped and started during Systems Management installation and uninstallation. As a result,
other third-party services, dependent on SNMP stop. If the third-party services are stopped, manually restart the
services.
NOTE: For Blade systems,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, exit the installation and free up memory. Close other applications or perform any other task that frees up
memory, before reattempting Server Administrator installation.
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:
The Systems Management installer features a Typical Setup option and a Custom Setup option for installing Server Administrator
and other managed system software.
Related Links:
19
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:
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. You can, however, go to Custom Setup and select the DRAC Command Line Tools software module for
installation.
NOTE: To install the drivers successfully, the installer runs in an elevated privilege mode.
NOTE: The Remote Enablement feature is available only through the Custom Setup option.
NOTE: Server Administrator installation also installs some of the required Visual C++ runtime components on
the system.
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.
NOTE: To install the drivers successfully, the installer runs in an elevated privilege mode.
1. Log in as a built-in Administrator, Domain Administrator, or user who is a part of Domain Admins and Domain Users group, to
the system on which you want to install the system management software.
2. Close all open applications and disable any virus-scanning software.
3. Insert the Systems Management Tools and Documentation DVD into the system's DVD drive. The autorun menu is displayed.
4. Select Server Administrator from the autorun menu and click Install.
The Server Administrator prerequisite status screen is displayed and runs the prerequisite checks for the managed system.
Any relevant informational, warning, or error messages are displayed. Resolve all error and warning situations, if any.
5. Click the Install, Modify, Repair, or Remove Server Administrator option.
The Welcome to the Install Wizard for Server Administrator screen is displayed.
6. Click Next.
The Software License Agreement is displayed.
20
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. 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. Else, click Change and browse to the
directory where you want to install the managed system software, and click OK.
10. Click Next on the Custom Setup dialog box to accept the selected software features for installation.
NOTE: You can cancel the installation process by clicking Cancel. The installation rolls back the changes that you
made. If you click Cancel after a certain point in the installation process, the installation may not roll back properly,
leaving the system with an incomplete installation.
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. You can safely ignore this message and continue with installation.
Related Links:
21
Option 1:
Option 2:
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. The unattended installation option
also provides several features that enable you to configure, verify, and view information about unattended installations.
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.
NOTE: After an unattended installation is complete, to use the command line interface (CLI) feature of Server
Administrator, you must open a new console window and execute the CLI commands from there. Executing
CLI commands from the same console window in which Server Administrator was installed does not work.
You can make the DVD image available to the remote system by either distributing the entire contents of the media, or by mapping
a drive from the target system to the location of the DVD image.
1. Share an image of the Systems Management Tools and Documentation DVD with each remote system on which you want to
install Server Administrator.
You can accomplish this task by directly sharing the DVD or by copying the entire DVD to a drive and sharing the copy.
2. Create a script that maps a drive from the remote systems to the shared drive described in step 1. This script should execute
msiexec.exe /i Mapped Drive\<32–bit or 64–bit MSI path on the DVD>/qb after the drive has
been mapped.
3. Configure the ISV distribution software to distribute and execute the script created in step 2.
4. Distribute this script to the target systems by using the ISV software distribution tools.
The script executes to install Server Administrator on each remote system.
5. Reboot each remote system to enable Server Administrator.
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.
22
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.
Related Links:
Customization Parameters
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.
The batch script installs Server Administrator along with specified features on each remote system.
3. Reboot each remote system to enable Server Administrator.
NOTE: See support.microsoft.com for details about all the command-line switches for the Windows Installer Tools.
Setting Result
/i <Package|Product Code> This command installs or configures a product.
/i <SysMgmt or SysMgmtx64>.msi – Installs the Server
Administrator software.
23
Setting Result
/x <SysMgmt or SysMgmtx64>.msi – Uninstalls the Server
Administrator software. For the product GUID, see Unattended
Uninstall Using The Product GUID
/qb – basic UI. This option is used for unattended but not silent
installation.
/fv – This option runs from the source and re-caches the local
package. Do not use this reinstall option for the first installation
of an application or feature.
CP_MESSAGE_FORMAT=<enhanced | traditional> 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.
24
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. 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. You can also choose to uninstall
one or multiple features on a specific group of servers.
NOTE: Type the REINSTALL, and REMOVE CLI parameters in upper case, as they are case‑sensitive.
You can include the REINSTALL customization parameter on the command line and assign the feature ID (IDs) of the software
feature that you want to reinstall. For example, msiexec.exe /i SysMgmt.msi REINSTALL=BRCM /qb
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.
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.
Feature ID Description
ALL All features
BRCM Broadcom Network Interface Card (NIC) Agent
QLG QLogic SNMP Agent
INTEL Intel NIC Agent
IWS Server Administrator Web Server
OMSS Server Administrator Storage Management Service
RAC4 DRAC Command Line Tools (RAC 4)
RAC5 DRAC Command Line Tools (RAC 5)
iDRAC (for 11th generation of PowerEdge servers) Integrated DRAC Command Line Tools
iDRAC12G (for 12th generation of PowerEdge servers) Integrated DRAC Command Line Tools
SI Server Instrumentation
RmtMgmt Remote Enablement
CLI Command Line Interface of Server Instrumentation
WMI Windows Management Instrumentation Interface of Server
Instrumentation
25
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).
NOTE: If SI or OMSS is installed using silent installation (unattended installation), then IWS and WMI are automatically
installed.
MSI Return Code
An application event log entry is recorded in the SysMgmt.log file. The following table shows some of the error codes returned by
the msiexec.exe Windows Installer Engine.
NOTE: For more information on all the error codes returned by the msiexec.exe and InstMsi.exe Windows Installer
functions, see support.microsoft.com.
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. All files that are modified by the installation actions are restored to their original state if a rollback
occurs.
When the MSI engine is going through the installation sequence, it ignores all actions that are scheduled as rollback actions. If a
Custom Action, MSI Standard Action, or a installation action fails, then a rollback starts.
You cannot roll back an installation once it is completed; transacted installation is only intended as a safety net that protects the
system during an installation session. If you want to remove an installed application, you should uninstall that application.
NOTE: Driver installation and removal is not executed as part of the installation transaction and therefore cannot be
rolled back if a fatal error occurs during execution.
NOTE: Installations, uninstallations, and upgrades that you cancel during installer cleanup, or after the installation
transaction is completed, are not rolled back.
26
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.
NOTE: A GUID is 128-bit long, and the algorithm used to generate a GUID guarantees unique GUID. The product GUID
uniquely identifies the application.
The setup program runs the prerequisite checker, which uses the system's PCI bus to search for installed hardware, such as
controller cards.
The setup program installs or upgrades all of the managed system software features that are appropriate for the particular system's
hardware configuration.
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. 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.
• When upgrading an operating system to a major version, uninstall the existing Systems Management software and reinstall the
latest Systems Management software. When upgrading only to an update level change (for example, Red Hat Enterprise Linux 5
Update 7 to Red Hat Enterprise Linux 5 Update 8), upgrade to the latest Systems Management software; all user settings are
preserved.
NOTE: Uninstalling Systems Management software deletes its user settings. Reinstall Systems Management
software and apply the user settings.
• If you have installed Server Administrator Web Server version 7.3, ensure that you install Server Instrumentation version 7.3 on
the managed system. Accessing an earlier version of Server Administrator using Server Administrator Web Server version 7.3
may display an error.
Upgrade
For an unattended upgrade, the msiexec.exe /i SysMgmt.msi /qb command accesses the DVD to accept the software
license agreement and upgrades all the required Server Administrator features on selected remote systems. All major user settings
are retained during an unattended upgrade.
NOTE: It is not possible to upgrade from a 32-bit to a 64-bit systems Management software on a 64-bit operating
system.
1. Insert the Systems Management Tools and Documentation DVD into the system's DVD drive. The autorun menu is displayed.
2. Select Server Administrator and click Install.
If the autorun program does not start automatically, go to the SYSMGMT\srvadmin\windows directory on the DVD, and run
the setup.exe file.
27
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. Click I accept the terms in the license agreement and Next if you agree.
The Setup Type dialog box is displayed.
6. Continue the installation from step 8 as mentioned in the Custom Installation section.
Modify
If you want to add or remove Server Administrator components:
NOTE: If you run the installer from another system and try to add a component using the Modify option, the
installer may display an error. A corrupt source on the system on which you run the installer may have caused the
error. You can verify this by checking the following registry entry: HKLM\Software\Classes\Installer\Products
\<GUID>\sourcelist\lastusedsource. If the value of lastusedsource is a negative number, it means that the source is
corrupt.
Repair
If you want to repair an installed Server Administrator component that is damaged:
28
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.
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.
1. Insert the Systems Management Tools and Documentation DVD into the system's DVD drive.
If the setup program does not start automatically, run the setup.exe in the SYSMGMT\srvadmin\windows directory on the
DVD.
The Server Administrator prerequisite status screen is displayed and runs the prerequisite checks for the managed system.
Any relevant informational, warning, or error messages detected during checking are displayed. Resolve all error and warning
situations, if any.
2. Click the Install, Modify, Repair, or Remove Server Administrator option.
The Welcome to the Install Wizard for Server Administrator screen is displayed.
3. Click Next.
This dialog enables you to modify, repair, or remove the program.
29
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:
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. Use the ISV distribution software to distribute the typical unattended uninstallation package to the remote systems.
The program executes to uninstall managed systems software on each remote system.
3. Reboot each remote system to complete uninstallation.
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.exe /x <SysMgmt or SysMgmtx64>.msi /qn runs the unattended uninstallation, but silently (without
displaying messages.)
30
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. 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.
NOTE: On Windows Server 2008 R2 SP1 Core and Windows Server 2012 Core, to install Server Administrator, Windows-
on-Windows (WOW) mode should be enabled.
NOTE: Windows Server 2008 Core or Hyper-V Server operating system does not support a graphical user interface
(GUI) based installation of software components. Install the software in the Command Line Interface (CLI) mode on
Server Core. For more information on Server Core, see microsoft.com.
NOTE: On Windows 7, to install the systems management software successfully, log in using an account which belongs
to the Administrators group and must run the setup.exe using the option Run as administrator from the right-click menu.
NOTE: Log in as a built-in Administrator, Domain Administrator, or user who is a part of Domain Admins and Domain
Users group, to install the systems management software on supported Microsoft Windows operating system. For more
information about user privileges, see the corresponding Microsoft Windows operating system Help.
NOTE: Server Administrator is also supported on Windows Server 2012.
Related Links:
Prerequisite Checker
in the command prompt. Replace <language_transform >.mst with the appropriate language file:
• 1031.mst (German)
• 1034.mst (Spanish)
• 1036.mst (French)
31
• 1041.mst (Japanese)
• 2052.mst (Simplified Chinese)
Related Links:
32
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.
The Active Directory schema defines the rules for what data can be included in the database. To extend the schema in Active
Directory, install the latest received unique OIDs, unique name extensions, and unique linked attribute IDs for the new attributes and
classes in the directory service from the Systems Management Tools and Documentation DVD.
The Product Object links the system to Active Directory for authentication and authorization queries. When a system is added to
the network, the administrator must configure the system and its product object with its Active Directory name so that users can
perform authentication and authorization with Active Directory. The administrator must also add the system to at least one
Association Object for users to authenticate.
The following figure illustrates that the Association Object provide the connection that is needed for all of the authentication and
authorization.
33
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. 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.
34
Figure 2. Setting Up RAC Active Directory Objects in a Single Domain
Related Links:
35
Figure 3. Setting Up RAC Active Directory Objects In Multiple Domains
36
Figure 4. Setting up Server Administrator Active Directory Objects In Multiple Domains
Related Links:
37
Configuring The Active Directory Product Name
To configure the Active Directory product name:
NOTE: Before you extend the schema, you must have Schema Admin privileges on the Schema Master Flexible Single
Master Operation (FSMO) Role Owner of the domain forest.
Extend the schema using two different methods. Use the Schema Extender utility, or use the Lightweight Directory Interchange
Format (LDIF) script file.
NOTE: The organizational unit is not added if you use the LDIF script file.
The LDIF script files and the Schema Extender utility are located in the following directories on the Systems Management Tools and
Documentation DVD:
The following table lists the folder names and <installation type>.
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.
38
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.
Table 9. Class Definitions for Classes Added to the Active Directory Schema
OID 1.2.840.113556.1.8000.1280.1.1.1.2
SuperClasses Group
Attributes dellProductMembers
dellPrivilegeMember
OID 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).
SuperClasses User
Attributes dellRAC4Privileges
dellRAC3Privileges
39
dellOmsaAuxClass
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.
SuperClasses Computer
Attributes dellAssociationMembers
OID 1.2.840.113556.1.8000.1280.1.2.1.1
SuperClasses None
Attributes dellOmsaIsReadOnlyUser
dellOmsaIsReadWriteUser
dellOmsaIsAdminUser
OID 1.2.840.113556.1.8000.1280.1.2.1.2
SuperClasses dellProduct
Attributes dellAssociationMembers
40
Attribute Name/Description Assigned OID/Syntax Object Identifier Single Valued
Link ID: 12070
Table 16. Server Administrator-Specific Attributes Added to the Active Directory Schema
Installing The Extension To The Active Directory Users And Computers Snap-In
When you are installing the systems management software using the Systems Management Tools and Documentation DVD, you
can install the Snap-in by selecting the Active Directory Snap-in option.
For 64-bit Windows operating systems, the Snap-in installer is located under <DVD drive>:\SYSMGMT
\x64\ManagementStation\windows\ADSnapIn.
NOTE: Install the Administrator Pack on each management station that is managing the new Active Directory objects. If
you do not install the Administrator Pack, you cannot view the new object in the container.
NOTE: For more information about the Active Directory Users and Computers snap-in, see the Microsoft
documentation.
Related Links:
41
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 <Enter>.
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.
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.
42
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.
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 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. The associated objects specify the products
connected to the network that are available for the defined users or user groups.
To Add Products
1. Select the Products tab and click Add.
2. Type the system, device, or group name and click OK.
3. In the Properties window, click Apply and then OK.
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.
43
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.
The default value is system name-software-product name, where system name is the name of the system
running Server Administrator, and softwareproduct name refers to the name of the software product defined in omprv32.ini (that is,
computerName-omsa).
NOTE: Restart the Server Administrator service after you have configured Active Directory.
The following table shows the valid parameters for the command.
Table 17. Active Directory Service Configuration Parameters
44
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.
When I run virtual media on the DRAC controller over a Wide Area
Network (WAN) with low bandwidth and latency, launching Systems
Management Install directly on the virtual media failed, what do I do?
Copy the web install package to the local system and then launch systems management Install.
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.
2. Download the installation package for that version.
3. Locate <SysMgmt or SysMgmtx64>.msi and enter the following command at the command prompt to force a reinstall.
msiexec /i <SysMgmt or SysMgmtx64>.msi REINSTALL=ALL REINSTALLMODE=vomus
4. Select Custom Setup and choose all the features that were originally installed. If you are not sure which features were
installed, select all of them and perform the installation.
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.
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.
45
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="<host_name>";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.
When launching the Systems Management Install, an error message may display, stating a
failure to load a specific library, a denial of access, or an initialization error. An example of
installation failure during Systems Management Install is "failed to load OMIL32.DLL." What do
I do?
This is most likely due to insufficient Component Object Model (COM) permissions on the system. To remedy this situation, see the
article support.installshield.com/kb/view.asp?articleid=Q104986
The Systems Management Install may also fail if a previous installation of systems management software or some other software
product was unsuccessful. Delete the following temporary windows installer registry, if present:
HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress
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 system.
When I run systems management Install, I see unreadable characters on the Prerequisite check
information screen.
When you run systems management Install in English, German, French, or Spanish and get unreadable characters on the
Prerequisite Check Information screen, ensure that the browser encoding has the default character set. Resetting the browser
encoding to use the default character set resolves the problem.
I have installed Server Administrator and Online Diagnostics in the same directory and Online
Diagnostics fails to work, what do I do?
If you have installed Server Administrator and Online Diagnostics in the same directory, Online Diagnostics may fail to work. On
uninstalling Server Administrator, you may also lose all Online Diagnostics files. To avoid this problem, install Server Administrator
and Online Diagnostics in different directories. In general it is recommended not to install more than one application in the same
directory.
46
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 <F5> key.
I see a warning message while uninstalling Server Administrator on Windows Server 2008 as
the installer tries to remove the shortcut?
While uninstalling Server Administrator on Windows Server 2008, you might see a warning message as the installer tries to remove
the shortcut. Click OK to continue the uninstallation.
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 the managed system software MSI package. If you
want to make the own DVD you must ensure that the DVD layout stays the 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
What do I do when I see the current version is already installed message is displayed?
If you upgrade from version X to version Y using MSP and then try to use the version Y DVD (full install), the prerequisite checker
on the version Y DVD informs you that the current version is already installed. If you proceed, the installation does not run in
Maintenance mode and you do not get the option to Modify, Repair, or Remove. Proceeding with the installation removes the
MSP and creates a cache of the MSI file present in the version Y package. When you run it a second time, the installer runs in
Maintenance mode.
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.
47
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:
a. Right-click My Computer on the desktop and click Open → Tools → Folder Options → File Types.
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. 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.
Can I launch my installation without running the prerequisite checker? How do I do that?
Yes, you can. For example, you can run the MSI of the managed system software, directly from SYSMGMT\srvadmin\Windows
\SystemsManagement. In general, it is not a good idea to bypass the prerequisite checker as there could be important information
that you would not know otherwise.
How do I know what version of systems management software is installed on the system?
Navigate to the Windows Control Panel and double-click Add/Remove Programs and select systems management software.
Select the link for support information.
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.
48
Table 18. Systems Management Features — Windows
49