Users Guide

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 self-signed certificate is regenerated.
Related Links
Minimum Login Roles for Microsoft SQL Server
Database Size and Scalability
The following table provides information about the changes to the database size in an environment with
2000 devices based on alerts, tasks, and alert actions.
Events Database Size
Initial database size 47.5 MB
After discovery and inventory of 2000 devices 48.5 MB
After 2000 alerts are generated 53.5 MB
22