Installing OpenManage Essentials. Dell EMC OpenManage Essentials Version 2.4
Add to My manuals377 Pages
advertisement
2
Installing OpenManage Essentials
Related links
Downloading OpenManage Essentials
Installation prerequisites and minimum requirements
Installing OpenManage Essentials
Migrating IT Assistant to OpenManage Essentials
Installation prerequisites and minimum requirements
For a list of supported platforms, operating systems, and browsers, see the Dell EMC OpenManage Essentials Support Matrix at dell.com/OpenManageManuals .
To install OpenManage Essentials, you require local system administrator rights and the system you are using must meet the criteria mentioned in the Minimum Requirements for OpenManage Essentials section of the Dell EMC OpenManage Essentials Support
Matrix available at dell.com/OpenManageManuals .
Related links
Installing OpenManage Essentials
Terms and conditions for using Relational Database Management
Systems
The Relational Database Management System (RDBMS) used for installing OpenManage Essentials is Microsoft SQL Server. SQL
Server has configuration settings separate from the OpenManage Essentials database. The server has logins (SQL or Windows) that may or may not have access to the OpenManage Essentials database.
When OpenManage Essentials is installed, Internet security is modified by adding registry entries to the ZoneMaps for HKLM and
HKCU. This ensures that Internet Explorer identifies the fully qualified domain name as an intranet site.
A self-signed certificate is created and this certificate is installed in the root Certificate Authorities (CA) and My certificates.
To prevent certificate errors, remote clients must either install OpenManage Essentials certificate in both CA and Root Certificate
Stores or have a custom certificate published to client systems by the domain administrator.
For a typical installation of OpenManage Essentials:
• Use the local instance of SQL Server that has all supported components.
• The RDBMS is altered to support both SQL and Windows authentication.
• An SQL Server login user is generated for OpenManage Essentials’ services. This login is added as a RDBMS SQL login with the dbcreator role and given the db_owner role over the ITAssist and OMEssentials databases.
NOTE: The password for the typical install, auto generated SQL Server login account, is controlled by the application and different on every system.
For the highest level of security, it is recommended that you use a domain service account that is specified during custom installation for SQL Server.
At runtime, when the OpenManage Essentials website determines that it has an invalid certificate or certificate binding; the selfsigned certificate is regenerated.
Related links
Minimum login roles for Microsoft SQL Server
21
Minimum login roles for Microsoft SQL Server
The following table provides information about the minimum permissions for SQL Server based on different installation and upgrade use cases:
Table 2. Minimum login roles for Microsoft SQL Server
Number Use Case
1 Installing OpenManage Essentials for the first time and you select the Typical option during the installation process.
Minimum Login Roles for SQL Server sysadmin access on the installed instance.
2 Installing OpenManage Essentials for the first time, you select the Custom option during the installation process and an empty OpenManage Essentials database is present
(locally or remotely).
NOTE: If you select the Custom install option and do not enter any credentials then the installation is considered as a Typical installation and sysadmin rights are required.
db_owner access on the OpenManage Essentials database.
3
4
You are installing OpenManage Essentials for the first time, you select the Custom option during the installation process, and an empty OpenManage Essentials database is not present.
dbcreator access on the server.
Upgrading OpenManage Essentials from an earlier version to the latest version and an OpenManage Essentials database is present (locally or remotely).
db_owner access on the OpenManage Essentials database.
Recommended database size
The following table provides information about the recommended database size in environments with different hardware configurations for OpenManage Essentials:
Table 3. Recommended database size
Recommende d database size
Number of devices
Large deployments
8000
Large deployments
5500
Large deployments
2000
Medium deployments Small deployments
500 100
SQL Server database size
14 GB 10 GB 6 GB 2 GB 1 GB
During the daily maintenance, OpenManage Essentials compresses and optimizes the database. OpenManage Essentials also downloads updates for managed servers. These updates are saved in the local file system (not in the database) where OpenManage
Essentials is installed.
NOTE: OpenManage Essentials can maintain up to 175,000 task execution history details without any issues. If the task execution history details exceed 175,000, you may experience problems starting OpenManage Essentials. The earlier task execution history records are purged when the limit set under Task Settings → Task Execution History Records to be
change the purge settings of task execution history details.
22
NOTE: For more information, see the
OpenManage Essentials Scalability and Performance
technical white paper at
DellTechCenter.com/OME.
Downloading OpenManage Essentials
To download OpenManage Essentials, go to dell.com/support or the Dell TechCenter website at DellTechCenter.com/OME .
Installing OpenManage Essentials
Before you install OpenManage Essentials, make sure that you have local administrator rights on the system.
To install OpenManage Essentials:
1.
Extract the OpenManage Essentials installation package.
2.
Double-click the Autorun.exe file available in the folder where you extracted the installation package.
The OpenManage Install screen is displayed. The following options are available:
• Dell EMC OpenManage Essentials — Select this option to install OpenManage Essentials, and Troubleshooting Tool.
• Dell EMC Repository Manager — Select to install Repository Manager. Using Repository Manager, you can create customized bundles and repositories of Update Packages, software utilities such as update drivers, firmware, BIOS, and other applications.
• Dell EMC License Manager — Select to install License Manager. The License Manager is a one-to-many license deployment and reporting tool for the integrated Dell Remote Access Controller (iDRAC), Chassis Management Controller
(CMC), OpenManage Essentials, and the PowerEdge storage sled licenses.
• Dell EMC SupportAssist Enterprise — Select to install SupportAssist Enterprise. The SupportAssist Enterprise provides proactive support capabilities for supported server, storage, and networking solutions.
• Documentation — Click to view the online help.
• View Readme — Click to view the readme file. To view the latest readme, go to DellTechCenter.com/OME .
3.
In OpenManage Install , select Dell EMC OpenManage Essentials , and click Install .
The OpenManage Essentials Prerequisites window displays the following requirement types:
• Critical — This error condition prevents the installation of a feature.
• Warning — This warning condition may disable the Typical installation but not an Upgrade of the feature later during installation. Also, later during installation, use the Custom installation setup type to select the feature.
• Information — This informational condition does not affect the Typical selection of a feature.
There are two options for resolving critical dependencies:
• Click Install All Critical Prerequisites to immediately begin installing all critical prerequisites without further interaction.
Install All Critical Prerequisites may require a restart depending on the configuration and the prerequisites installation will resume automatically after restart.
• Install each prerequisite individually by clicking the associated link with the required software.
NOTE: Ensure that KB2919355 update is installed on Windows 2012 R2 systems to run OpenManage Essentials 2.4.
To install KB2919355 update manually, see the Microsoft Knowledge Base article ID 2919355 at support.microsoft.com.
NOTE: The latest iDRAC and chassis firmware require TLS 1.1 and TLS 1.2 protocols to be enabled on Windows 2008
R2 and Windows 2012 systems. To enable TLS 1.1 and TLS 1.2 as the default secure protocols in WinHTTP, see the
Microsoft Knowledge Base article ID 3140245 at support.microsoft.com.
NOTE: To configure a remote database, you do not require an SQL Express installation on the local system. See
Setting Up OpenManage Essentials Database on a Remote SQL Server
. If you are not configuring a remote database, then install SQL Express by clicking the warning prerequisite link. Selecting Install All Critical Prerequisites does not install SQL Express.
4.
Click Install Essentials .
23
NOTE: If you are installing OpenManage Essentials for the first time, a dialog box is displayed prompting you to select if you want to install OpenManage Essentials on a local or remote database. If you choose to install
OpenManage Essentials on a local database, SQL Server 2012 Express is installed on the system. If you choose to install OpenManage Essentials on a remote database, the installation follows the
Custom Setup Installation steps.
5.
In the install wizard for OpenManage Essentials, click Next .
6.
In the License Agreement page, read the license agreement, select I accept the terms in the license agreement , and then click Next .
7.
In Setup type select either Typical or Custom installation.
• If you selected Typical , click Next . Verify the installation settings in the Ready to Install the Program page and the click
Install .
NOTE: If the default ports assigned to the OpenManage Essentials services are either blocked or used by another application, a message is displayed prompting you to either unblock the ports or select the Custom installation where you can specify another port.
NOTE: The parameters of all tasks that you create are encrypted and saved. During a reinstallation, if you choose to use a database that was retained from a previous OpenManage Essentials installation, the existing tasks will not run successfully. To resolve this issue, you must recreate all tasks after the installation.
• If you selected Custom , in Custom Setup , click Next and follow the instructions in
.
8.
After the installation is complete, click Finish .
If you have installed OpenManage Essentials on a virtual machine (VM), the following are the suggested settings for the
OpenManage Essentials VM:
• Increase CPU settings based on resource availability.
• Disable Dynamic Memory .
• Increase Memory Weight to high.
Custom Setup Installation
To install OpenManage Essentials using custom setup:
1.
In Custom Setup , click Change to change the installation location, and then click Next .
2.
In custom settings for port numbers, if required, change default values for Network Monitoring Service port number , Task
Manager Service port number , Package Server Port , and Console Launch port and then click Next .
3.
In Database Server , do any of the following and then click Next :
• Local database—If you have multiple SQL Server versions available on the management system and you want to select an
SQL Server on which you want to set up the OpenManage Essentials database, then select the SQL server from the
Database Server list, the type of authentication, and provide the authentication details. If you do not select a database server, by default, a supported version of SQL Server Standard, Enterprise, or Express that is available is selected for the installation. For more information, see the Installing Dell OpenManage Essentials technical white paper at delltechcenter.com/ome .
•
Browse and select the remote system and then provide the authentication details. You can also set up the OpenManage Essentials database on a remote system by providing the IP address or host name and the database instance name of the remote system in Database Server.
NOTE: If you select the Custom install option and do not enter any credentials, the installation is considered as a typical installation and sysadmin rights are required.
NOTE: If you have multiple database instances running on a selected database server, you can specify the required database instance name to configure the Essentials database with it. For example, using (local)\MyInstance, you are configuring Essentials database on a local server and MyInstance named database instance.
NOTE: The parameters of all tasks that you create are encrypted and saved. During a reinstallation, if you choose to use a database that was retained from a previous OpenManage Essentials installation, the existing tasks will not run successfully. To resolve this issue, you must recreate all tasks after the installation.
24
NOTE: If you select the Custom install option, you can customize the database name. You can enter any name of your choice in the Database Name field. If you do not enter a database name, by default, OMEssentials is selected.
Typically, you can use the database name field in a scenario where you have a dedicated remote SQL server that you want to use for installing multiple OpenManage Essentials instances. For example, you can assign the database name as DB_OME_Site1, DB_OME_Site2, and DB_OME_Site3 while installing the respective OpenManage Essentials instances.
NOTE: The database name must start with an alphabet and it should not exceed 80 characters in length. You may also include special characters in the database name, except square brackets ([]), apostrophe ('), and curly brackets
({}).
4.
Verify the installation settings in the Ready to Install the Program page and the click Install .
Setting up OpenManage Essentials Database on a Remote SQL Server
You can configure OpenManage Essentials to use an SQL Server present on a remote system. Before setting up the OpenManage
Essentials database on the remote system, check for the following prerequisites:
• Network communication between the OpenManage Essentials system and the remote system is functioning.
• SQL connection works between the OpenManage Essentials system and the remote system for the specific database instance.
You can use the Microsoft SQL Server Express 2012 Management Studio tool to verify the connection. On the remote database server, enable TCP/IP protocol and if you are using SQL Authentication, enable mixed mode on the remote SQL Server.
You can retarget the database if:
• SQL credential to the SQL Server fails.
• Windows credential to the SQL Server fails.
• Login credentials have expired.
• Database is moved.
Retargeting the OpenManage Essentials Database
You can setup the OpenManage Essentials console to connect to an OpenManage Essentials database available on a remote system.
For example, after installing OpenManage Essentials with a local database, you can back up and restore the OpenManage Essentials database on a remote system. After the database is restored on the remote system, you can setup OpenManage Essentials to connect to the restored database available on the remote system.
To retarget the OpenManage Essentials database:
1.
Back up the OpenManage Essentials database. See Backing up the OpenManage Essentials Database .
2.
Restore the OpenManage Essentials database. See
Restoring the OpenManage Essentials Database .
3.
Create a new user in SQL Server. See Creating a new user in SQL Server .
4.
Backing up the OpenManage Essentials Database
Before you back up the OpenManage Essentials database:
• Ensure that OpenManage Essentials is installed on the system using the Typical installation method.
• Ensure that Microsoft SQL Server Management Studio is installed on the system where OpenManage Essentials is installed.
• Ensure that you stop Internet Information Services (IIS) and all OpenManage Essentials services.
To back up the OpenManage Essentials database:
1.
Open SQL Server Management Studio.
2.
In Object Explorer , expand the Databases node.
3.
Right-click the OMEssentials database and then click Tasks → Back Up .
The Back Up Database - OMEssentials window is displayed.
25
4.
Click OK to start the database back up.
A confirmation message is displayed after the database back up is completed. The OpenManage Essentials database backup file,
OMEssentials.bak, is saved at C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESSOME\MSSQL\Backup.
Restoring the OpenManage Essentials Database
Before you begin to restore the OpenManage Essentials database:
• Ensure that OpenManage Essentials database back up file, OMEssentials.bak, is available on the system. If required, you must copy and paste the OpenManage Essentials database back up file from the system where you created the back up file.
• Ensure that Microsoft SQL Server Management Studio is installed on the system.
• Ensure that you have sysadmin access for SQL Server.
To restore the OpenManage Essentials database:
1.
Open SQL Server Management Studio on the system where you want to restore the OpenManage Essentials database.
2.
In Object Explorer , right-click Databases → Restore Database .
The Restore Database window is displayed
3.
Under Source , select Device and click the browse button.
The Select backup devices window is displayed.
4.
Click Add and then browse to select the OpenManage Essentials database back up file.
5.
Click OK to close the Select backup devices window.
6.
Click OK in the Restore Database window to start restoring the database.
A confirmation message is displayed after the database is restored. The restored OMEssentials database is displayed under
Databases in Object Explorer .
NOTE: The database restoration may not be successful if multiple instances of the backup file, OMEssentials.bak, are available on the system. To resolve the issue, rename both the files (OMEssentials and OMEssentials_log) in the Restore database file as section of the Restore Database window, and then try restoring the database.
Creating a new user in SQL Server
To create a new user in SQL Server:
1.
Open SQL Server Management Studio on the system where you restored the OpenManage Essentials database.
2.
In Object Explorer expand the Security node.
3.
Click Login → New Login .
The Login - New window is displayed.
4.
In the General page: a. Type a name in the Login name field.
b. Select Windows authentication or SQL Server authentication based on your preference.
c. Type the password and reconfirm the password in the appropriate fields.
d. Optional: If you want to enforce password policy options for complexity, select Enforce Policy Password .
e. From the Default database list, select OMEssentials .
f. From the Default language list, select a default language for the login.
5.
In the Server Roles page, select public .
6.
In the User Mappings page: a. Under Users mapped to this login , select OMEssentials .
b. Under Database role membership for: OMEssentials, select db_owner and public .
7.
Click OK .
The new user that you created is displayed under Security → Logins in Object Explorer .
26
Connecting to the OpenManage Essentials Database
To connect to the OpenManage Essentials database:
1.
On the system where OpenManage Essentials is installed, open the command prompt, and run the following command: sqlcmd -E -S ".\SQLEXPRESSOME" -Q "ALTER LOGIN [OMEService] WITH
PASSWORD='DummyPassword'"
NOTE: Verify that the OpenManage Essentials database instance that was created during the typical installation is
SQLEXPRESSOME.
NOTE: Copying and pasting the command may result in incorrect characters. Therefore, it is recommended that you type the complete command.
2.
Open OpenManage Essentials.
The database login error window is displayed.
3.
Click OK on the database login error window.
The Database Connection Error window is displayed.
4.
In the Database Connection Error window: a. In the Server Name field, type the name of the system where you restored the OpenManage Essentials database.
b. From the Authentication list, select the authentication method for the database.
c. Type the user name and password of the new user you created in the appropriate fields.
d. Type the name of the database that you have already created in SQL Server.
e. Click Connect .
5.
Close and reopen OpenManage Essentials.
6.
Restart the Internet Information Services (IIS).
7.
Restart the OpenManage Essentials services or restart the server.
After the database retargeting is completed successfully, if required, you can delete the OpenManage Essentials database from the system on which OpenManage Essentials is installed.
Installing OpenManage Essentials on a domain controller
When installing OpenManage Essentials on a domain controller, it is recommended that you install OpenManage Essentials with a remote database. There are specific restrictions when running SQL Server on a domain controller, and considering the resources demands of a domain controller, SQL Server performance may be degraded which will affect the performance of OpenManage
Essentials. For more information on the restrictions when running SQL Server on a domain controller, see the Microsoft Knowledge
Base article ID 2032911 at support.microsoft.com
.
NOTE: For security reasons, it is recommended that you do not install SQL Server 2012 on a domain controller. SQL
Server Setup will not prevent you from installing SQL Server on a domain controller, however, the following limitations apply:
• You cannot run SQL Server services on a domain controller under a local service account.
• After SQL Server is installed on a system, you cannot change the system from a domain member to a domain controller.
You must uninstall SQL Server before you change the host system to a domain controller
• SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
• SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
When setting up OpenManage Essentials on a domain controller, ensure that the following prerequisites are met:
• Ensure that network communication between the system on which OpenManage Essentials is installed and the remote database system is functional.
• Ensure that the SQL Server user has permission to backup, create, and configure databases.
• When using SQL Server authentication, ensure that SQL Server and Windows authentication mode is enabled within SQL
Server. See Enabling SQL Server Authentication and Windows Authentication in SQL Server
27
•
Ensure that TCP/IP is enabled in SQL Server. See Verifying the SQL Server TCP/IP status .
After OpenManage Essentials is installed on a domain controller:
• By default, the Domain Admins group is added as a member of the OmeAdministrators and OmePowerUsers roles.
• Local Windows user groups are not included in the OpenManage Essentials roles. OmeAdministrators , OmePowerUsers , or
OmeUsers rights can be granted to users or user groups by adding them to the OpenManage Essentials Windows groups.
OmeSiteAdministrators rights can be granted by OmeAdministrators through the Device Group Permissions portal.
The following sections provide instructions to install and setup OpenManage Essentials on a domain controller with a remote or local database.
Installing OpenManage Essentials on a domain controller with a remote database
Before you begin installing OpenManage Essentials on a domain controller, ensure that you are logged in to the domain controller with administrator rights.
To install OpenManage Essentials on a domain controller with a remote database:
1.
Extract the OpenManage Essentials installation package.
2.
Double-click the Autorun.exe file available within the folder where you extracted the installation package.
The OpenManage Install window is displayed.
3.
Select Dell EMC OpenManage Essentials and click Install .
The OpenManage Essentials Prerequisites window is displayed.
4.
Click Install All Critical Prerequisites .
NOTE: If SQL Server is not already installed on the domain controller, the Prerequisites window displays a warning message with a link that allows you to install SQL Express on the domain controller (local) with an OpenManage
Essentials-specific SQLEXPRESSOME database instance. If you ignore the warning message, when the
OpenManage Essentials installation begins, a message is displayed requesting you to confirm whether you want to install OpenManage Essentials with a local or remote database
5.
When the confirm database location message is displayed, click No to install OpenManage Essentials on a remote database.
The Custom Setup window is displayed.
6.
Click Next .
The OpenManage Essentials Custom Settings window is displayed.
7.
If required, change the default port numbers based on your requirement, and click Next .
The Database Server window is displayed.
8.
Perform one of the following:
• Click Browse and select the remote database.
• Type the host name and database instance name in the Database Server field.
9.
Click Windows authentication or SQL Server authentication .
NOTE: For Windows authentication, if you are using a non-domain Windows account, the credentials must exist on both the domain controller and the remote system, and should also be identical. The Windows user account must have the privileges required to create databases in SQL Server.
10.
Type the user name and password in the appropriate fields and click Next .
The Ready to Install the Program window is displayed.
11.
Click Install .
After the installation of OpenManage Essentials is completed, add the logged in administrator to the OMEAdministrators user group.
See
Adding Users to the OpenManage Essentials Groups
.
NOTE: After the OpenManage Essentials database is set up on the remote system, if the database is either moved or altered, open OpenManage Essentials to re-target using the new database connection settings.
28
Installing OpenManage Essentials on a domain controller with a local database
Before you begin installing OpenManage Essentials on a domain controller, ensure that you are logged in to the domain controller with administrator rights.
To install OpenManage Essentials on a domain controller with a local database:
1.
Extract the OpenManage Essentials installation package.
2.
Double-click the Autorun.exe file available within the folder where you extracted the installation package.
The OpenManage Install window is displayed.
3.
Select Dell EMC OpenManage Essentials and click Install .
The OpenManage Essentials Prerequisites window is displayed.
NOTE: If SQL Server is not already installed on the domain controller, the Prerequisites window displays a warning message with a link that allows you to install SQL Express on the domain controller (local) with an OpenManage
Essentials-specific SQLEXPRESSOME database instance.
4.
In the Prerequisites window, click the link to install SQL Express on the domain controller.
5.
.
6.
Configure the SQLEXPRESSOME instance to run using the domain service account. See
Configuring the Database Instance .
7.
Click Install Essentials on the Prerequisites window, and follow the instructions on the screen to complete the installation of
OpenManage Essentials.
After the installation of OpenManage Essentials is completed, add the logged in administrator to the OMEAdministrators user group.
See
Adding Users to the OpenManage Essentials User Groups
.
Creating a Domain Service Account
A domain service account is required to run SQL Server on the domain controller.
To create a domain service account:
1.
Click Start → Administrative Tools .
2.
Select Active Directory Users and Computers .
3.
On the left pane, right-click Managed Service Account → New → User .
The New Object – User window is displayed.
4.
Type the first name and user logon name in the appropriate fields, and click Next .
5.
Type a password and reconfirm the password in the appropriate fields, and click Finish .
Configuring the database instance
The SQL Server service will not start if you are using the default NETWORK SERVICE or LOCAL SYSTEM accounts. Therefore, you must configure the SQLEXPRESSOME database instance to run using a domain service account.
To configure the SQLEXPRESSOME database instance:
1.
Open Microsoft SQL Server Configuration Manager.
2.
On the left pane, click SQL Server Services .
3.
On the right-pane, right-click SQL Server (SQLEXPRESSOME) and click Properties .
The SQL Server (SQLEXPRESSOME) Properties window is displayed.
4.
In the Log on tab, select This account .
5.
Type the domain service account name, password, and confirm the password in the appropriate fields.
6.
Click Restart .
7.
Click Apply
Adding users to the OpenManage Essentials user groups
To add users to the OpenManage Essentials user groups:
29
NOTE: The users you add to the OpenManage Essentials user group must also belong to the built-in local Administrator group. For information on adding a Windows user account to a group, see “Adding a user account to a group” at support.microsoft.com
1.
Open Server Manager.
2.
Click Tools → Computer Management .
3.
In the left pane, click Local Users and Groups → Groups .
4.
In the right-pane, right-click OmeAdministrators and select Add to Group .
5.
In the OmeAdministrator Properties window, click Add .
The Select Users window is displayed.
6.
In the Enter the object names to select field, type the user name.
7.
Click Check Names and then click OK .
The user name is displayed in the Members list within the OmeAdministrator Properties window.
8.
Click OK .
Enabling SQL Server and Windows Authentication Mode in SQL Server
To enable SQL Server and Windows authentication mode:
1.
Open SQL Server Management Studio.
2.
In Obejct Explorer , right-click the top-level SQL Server object and click Properties .
The Server Properties window is displayed.
3.
In the left pane, click Security .
4.
In the right pane, under Server authentication , click SQL Server and Windows Authentication mode .
5.
Click OK .
6.
In Obejct Explorer , right-click the top-level SQL Server object and click Restart .
Verifying SQL Server TCP or IP Status
To verify the TCP/IP status of SQL Server:
1.
Click Start → All Programs → SQL Server Configuration Manager
NOTE: If multiple versions of SQL Server Configuration Manager are installed, ensure that you select the latest version.
2.
On the left pane, click to expand SQL SQL Native Client 11.0 Configuration .
3.
Click Client Protocols .
4.
On the right pane, ensure that the status of TCP/IP is Enabled .
5.
If TCP/IP is not enabled, right-click TCP/IP and select Enable .
Installing SupportAssist Enterprise
SupportAssist Enterprise integrates with OpenManage Essentials to provide proactive support capabilities for enterprise server, storage, and networking solutions using the existing environment data. SupportAssist collects information from supported devices, and automatically creates support cases when issues arise. This helps Dell EMC to provide you an enhanced, personalized, and efficient support experience.
To install SupportAssist:
NOTE: Before you begin, make sure that:
• The system is able to connect to the Internet.
• You have the Administrator rights on the system.
• On the firewall, port 443 is open to access https://ftp.dell.com
.
30
NOTE: If the installation of SupportAssist Enterprise fails, you can retry the installation later. To retry the installation, right-click the Dell EMC SupportAssistSetup.exe file available at C:\Program Files\Dell\SysMgt\Essentials
\SupportAssistSetup and select Run as administrator.
1.
Extract the OpenManage Essentials installation package.
2.
In the folder where you extracted the installation package, double-click the Autorun.exe file.
The OpenManage Install window is displayed.
3.
If OpenManage Essentials version 2.4 is not installed on the system, make sure that Dell EMC OpenManage Essentials is selected.
4.
Select Dell EMC SupportAssist Enterprise , and then click Install .
If you selected Dell EMC OpenManage Essentials and Dell EMC SupportAssist Enterprise , installation of OpenManage
Essentials is completed and then SupportAssist Enterprise is installed. The system prerequisites for installing SupportAssist
Enterprise are verified. If the system prerequisites are met, the Welcome to Dell EMC SupportAssist Enterprise Installer window is displayed.
5.
Click Next .
The License Agreement window is displayed.
6.
Read the terms in the communication requirements and click I Agree .
NOTE: SupportAssist Enterprise installation requires that you allow Dell EMC to save certain Personally Identifiable
Information (PII) such as your contact information, administrator credentials of the devices to be monitored, and so on. SupportAssist installation cannot proceed unless you allow Dell EMC to save your PII.
7.
Read the software license agreement, click I Agree , and then click Next .
If the system connects to the Internet through a proxy server, the Proxy Settings window is displayed. Else, the Installing
SupportAssist Enterprise window is displayed briefly, and then the Installation Completed window is displayed.
8.
If the Proxy Settings window is displayed, provide the following: a. In the Server Address field, type the proxy server address or name.
b. In the Port field, type the proxy port number.
NOTE: If the proxy server credentials are not provided, SupportAssist Enterprise connects to the proxy server as an anonymous user.
c. If the proxy server requires authentication, select Proxy requires authentication , and then provide the following information in the corresponding fields:
• Username — The user name must contain one or more printable characters, and must not exceed 104 characters.
• Password — The password must contain one or more printable characters, and must not exceed 127 characters.
• Confirm Password — Re-enter the password. The password must match with the one provided in the Password field.
d. Click Install .
The proxy settings are validated. If the validation is unsuccessful, verify the proxy settings and try again or contact your network administrator for assistance.
e. In the Validation Successful dialog box, click OK .
The Installing SupportAssist Enterprise window is displayed briefly, and then the Installation Completed window is displayed.
9.
Click Finish .
When you start SupportAssist Enterprise, the SupportAssist Enterprise Setup Wizard is displayed. You must complete all steps in the SupportAssist Enterprise Setup Wizard before you can use SupportAssist Enterprise. For more information, see the Dell EMC
SupportAssist Enterprise User’s Guide at Dell.com/ServiceabilityTools .
Installing Repository Manager
The Repository Manager is an application that helps manage system updates easily and effectively. Using Repository Manager, you can build a custom repository based on the managed system configurations that are obtained from OpenManage Essentials.
31
To install Repository Manager:
1.
Double-click the OpenManage Essentials executable file.
2.
In OpenManage Install , select Dell EMC Repository Manager , and then click Install .
3.
In Dell EMC Repository Manager - InstallShield Wizard , click Next .
4.
In License Agreement , select I accept the terms in the license agreement , and click Next .
5.
In Customer Information , do the following and click Next .
a. Provide user name and organization information.
b. Select either Anyone who uses this computer (all users) to make this application available to everyone or Only for me
(Windows User) to retain access.
6.
In Destination Folder , use the default location or click Change to specify another location, and then click Next .
7.
In Ready to Install the Program , click Install .
8.
After the installation is complete, click Finish .
Installing License Manager
The License Manager is a one-to-many license deployment and reporting tool for the integrated Dell Remote Access Controller
(iDRAC), Chassis Management Controller (CMC), OpenManage Essentials, and the PowerEdge storage sled licenses.
To install License Manger:
1.
Double-click the OpenManage Essentials executable file.
2.
In OpenManage Install , select Dell EMC License Manager .
3.
Select a language for the installation, and click OK .
4.
In the Welcome screen, click Next .
5.
In License Agreement , select I accept the terms in the license agreement and click Next .
6.
In Setup Type , select any of the following:
• To accept the default installation path, choose Typical installation and click Next .
• To enable specific program features and change the installation path, select Custom installation and click Next . In Custom
Setup , select the License Manager features that you require; check for disk space, assign a new location for installing
License Manager.
7.
In the Ready to Install screen, click Install .
8.
After the installation is complete, click Finish .
Upgrading OpenManage Essentials
You can upgrade OpenManage Essentials versions 2.1, 2.2, and 2.3 to version 2.4.
Before you upgrade, ensure that the minimum available free space on the hard drive is about 10 GB.
To upgrade:
1.
Double-click the OpenManage Essentials executable file.
The Dell OpenManage Install screen is displayed. The following options are available:
• Dell EMC OpenManage Essentials — Select this option to install OpenManage Essentials, and Troubleshooting Tool.
• Dell EMC Repository Manager — Select this option to install Repository Manager. Using Repository Manager, you can create customized bundles and repositories of Update Packages, software utilities such as update drivers, firmware, BIOS, and other applications.
• Dell EMC License Manager — Select this option to install License Manager. The License Manager is a one-to-many license deployment and reporting tool for the integrated Dell Remote Access Controller (iDRAC), Chassis Management Controller
(CMC), OpenManage Essentials, and PowerEdge storage sled licenses.
• Dell EMC SupportAssist Enterprise — Select this option to install SupportAssist Enterprise. The SupportAssist Enterprise provides proactive support capabilities for supported server, storage, and networking solutions.
32
NOTE: If SupportAssist Enterprise is already installed on the system, by default, the Dell EMC SupportAssist
Enterprise option is selected and disabled. After the upgrade of OpenManage Essentials, SupportAssist
Enterprise is also upgraded. If applicable, you may be required to provide the proxy settings during the upgrade of SupportAssist Enterprise. For more information, see the
ServiceabilityTools.
Dell EMC SupportAssist User’s Guide
at dell.com/
• Documentation — Click to view the online help.
• View Readme — Click to view the readme file. To view the latest readme, go to dell.com/OpenManageManuals .
2.
In the OpenManage Install screen, select Dell EMC OpenManage Essentials and click Install .
The OpenManage Essentials Prerequisites window, displays the following requirement types:
• Critical — This error condition prevents the installation of a feature.
• Warning — This warning condition may disable the Typical installation but not an Upgrade of the feature later during installation.
• Information — This informational condition does not affect the Typical installation of a feature.
NOTE: If OpenManage Essentials version 1.1 is installed on the system on a local database using SQL Server 2008
Express edition, and an OpenManage Essentials-specific named instance SQLEXPRESSOME is not available, the
SQL Server prerequisites displays a Critical icon. To proceed with the installation, you must install SQL Server
Express 2012 SP1 with the SQLEXPRESSOME instance. Data from the earlier version of SQL Server is migrated automatically.
3.
Click Install Essentials .
4.
In the install wizard for OpenManage Essentials, click Next .
5.
In the License Agreement page, read the license agreement, select I accept the terms in the license agreement , and then click Next .
6.
If applicable, provide the Package Server Port and the Task Manager Service Port.
If either the package server port or task manager service port is blocked during an upgrade, provide a new port. Click Next .
NOTE: For information about the supported ports and protocols, see
Supported Protocols and Ports on Managed
and
Supported Protocols and Ports on Management Stations
.
7.
Click Ok .
8.
Click Install .
9.
After the installation is complete, click Finish .
After the upgrade is complete, you must perform the following steps:
1.
Run discovery and inventory for all existing discovery ranges.
2.
In the Device Search portal, verify if you get the expected results for all existing device queries.
3.
In the System Update portal, if the existing catalog is not the latest, make sure that you get the latest catalog.
Reconfiguring OpenManage Essentials version 2.4 after upgrading
This section contains information about the changes in templates on the Deployment portal, baselines in the Configuration portal, and tasks that must be performed after upgrading to OpenManage Essentials version 2.4 from OpenManage Essentials version 2.2 and earlier.
The upgraded version of OpenManage Essentials provide the following enhancements:
• Enhanced configuration settings for the Chassis templates and baselines with user-friendly attribute names.
• Enhanced details about changed attributes for Chassis Deployment.
• Create baselines for server and chassis from corresponding server or chassis templates that were available in the earlier version of OpenManage Essentials. The newly created server and chassis baseline names are suffixed with Baseline .
NOTE: Baselines are used for device compliance.
• Provides the option to recreate the Chassis template for deployment and the Chassis baseline for compliance-related tasks.
NOTE: After upgrading to OpenManage Essentials 2.4, the template deployment tasks are available under
Deployment → Tasks.
33
• Provides the option to discover devices based on specific device type and specific protocol. For more information, see
Configuring the Discovery Wizard
.
After the upgrade is complete, you must perform the following tasks:
• From the Deployment portal, recreate the Chassis Template. For more information, see
.
• From the Manage → Configuration portal , recreate the Chassis Baseline. For more information see
.
• Recreate the scheduled chassis deployment tasks that were created in OpenManage Essentials version 2.2 and earlier as the scheduled chassis deployment task cannot be edited or rerun after upgrading to OpenManage Essentials version 2.4. The user can edit the scheduled task that is created after the upgrade.
NOTE: Ensure that the recreated chassis template and baseline are reviewed, and required changes and selection are made to the attribute values.
Recreating chassis template
After upgrading to the latest version of OpenManage Essentials, the existing chassis templates, which were created in OpenManage
Essentials version 2.2 and earlier, are displayed as broken.
To recreate the chassis template:
1.
Click Deployment → Templates .
2.
From the Chassis Templates , select a template.
3.
On the Template action window, click the Recreate this Template button to recreate the chassis template.
4.
On the Task Authentication window, type the template credentials and click OK .
A 'Create template' task is submitted for execution.
5.
Click OK .
The selected chassis template is recreated.
NOTE: The recreated chassis template name is not changed.
6.
Click the recreated chassis template and click the Attributes tab to make the desired changes to the template attributes.
NOTE: For compliance and deployment related tasks, ensure that the chassis has an enterprise license, supported firmware version, and is discovered by using the WS-Man protocol. For more information, see
Device requirements for deployment and compliance tasks .
NOTE: The chassis template which is created from a file does not display the Recreate this Template button and has to be recreated manually from the chassis configuration file.
Recreating chassis baseline
OpenManage Essentials 2.4 automatically creates a corresponding chassis baseline for the chassis template that was created in
OpenManage Essentials version 2.2 and earlier after upgrading. The chassis baseline that is created after the upgrade has the baseline name suffixed with Baseline . The chassis baselines are displayed as broken in the Configuration portal and must be recreated.
To recreate the chassis baseline:
1.
Click Manage → Configuration → Compliance by Baseline → Chassis Basleine .
2.
From Chassis Baselines , select a baseline.
3.
On the Baseline action window, click the Recreate this Baseline button to recreate the chassis baseline.
4.
On the Task Authentication window, type the chassis credentials and click OK .
A 'Create baseline' task is submitted for execution.
5.
Click OK .
The selected chassis baseline is recreated.
NOTE: The recreated baseline name is not changed.
NOTE: While recreating the chassis baseline, OpenManage Essentials will automatically take care of all the devices that are associated with the baseline in the earlier version and the compliance-related tasks.
34
6.
Click the recreated baseline and click the Attributes tab to check the baseline attributes.
NOTE: For compliance and deployment related tasks, ensure that the chassis has an enterprise license, supported firmware version, and is discovered by using the WS-Man protocol. For more information, see
Device requirements for deployment and compliance tasks .
NOTE: The chassis baseline which is created from a file does not display the Recreate this Template button and has to be recreated manually from the chassis configuration file.
Uninstalling OpenManage Essentials
NOTE: Before uninstalling OpenManage Essentials, you must uninstall OpenManage Essentials MIB Import Utility and
SupportAssist Enterprise (if installed).
To uninstall OpenManage Essentials:
1.
Click Start → Control Panel → Programs and Features.
2.
In Uninstall or change a program , select Dell EMC OpenManage Essentials and click Uninstall .
3.
In the message Are you sure you want to uninstall OpenManage Essentials?
, click Yes .
4.
In the message Uninstalling OpenManage Essentials removes the OpenManage Essentials database. Do you want to retain the database?
, click Yes to retain the database or click No to remove it.
5.
Click Finish .
Migrating IT Assistant to OpenManage Essentials
Direct migration from IT Assistant to OpenManage Essentials version 2.4 is not supported. However, you can migrate IT Assistant to an earlier version of OpenManage Essentials, and then upgrade to OpenManage Essentials version 2.4. For information about migrating IT Assistant to an earlier version of OpenManage Essentials, see the appropriate Dell EMC OpenManage Essentials User's
Guide at dell.com/OpenManageManuals .
Related links
Installing OpenManage Essentials
35
advertisement