Users Guide
Table Of Contents
- Dell EMC OpenManage Enterprise Version 3.5 User's Guide
- Contents
- Tables
- About Dell EMC OpenManage Enterprise
- Security features in OpenManage Enterprise
- Install OpenManage Enterprise
- Installation prerequisites and minimum requirements
- Deploy OpenManage Enterprise on VMware vSphere
- Deploy OpenManage Enterprise on Hyper-V 2012 R2 and earlier host
- Deploy OpenManage Enterprise on Hyper-V 2016 host
- Deploy OpenManage Enterprise on Hyper-V 2019 host
- Deploy OpenManage Enterprise by using Kernel-based Virtual Machine
- Deploy OpenManage Enterprise programmatically
- Get started with OpenManage Enterprise
- Log in to OpenManage Enterprise
- Configure OpenManage Enterprise by using Text User Interface
- Configure OpenManage Enterprise
- Recommended scalability and performance settings for optimal usage of OpenManage Enterprise
- Supported protocols and ports in OpenManage Enterprise
- Use case links for the supported protocols and ports in OpenManage Enterprise
- OpenManage Enterprise Graphical User Interface overview
- OpenManage Enterprise Home portal
- Managing devices
- Organize devices into groups
- Create or delete a Static device group
- Create or edit a Query device group
- Adding or editing devices in a Static child group
- Rename child groups of Static or Query Dynamic groups
- Clone a Static or Query group
- Add devices to a new group
- Add devices to existing group
- Delete devices from OpenManage Enterprise
- Exclude devices from OpenManage Enterprise
- Update the device firmware and drivers by using baselines
- Roll back an individual device's firmware version
- Refresh the device inventory
- Refresh the device status
- Export the single device inventory
- Devices list
- Performing more actions on chassis and servers
- Hardware information displayed for MX7000 chassis
- Export all or selected data
- Viewing and configuring devices
- Start Management application iDRAC of a device
- Start the Virtual Console
- Organize devices into groups
- Manage the device firmware and drivers
- Manage device deployment templates
- Create a deployment template from a reference device
- Create a deployment template by importing a template file
- View a deployment template information
- Edit a server deployment template
- Edit a chassis deployment template
- Edit IOA deployment template
- Edit network properties of a deployment template
- Deploy device deployment templates
- Deploy IOA deployment templates
- Clone deployment templates
- Auto deployment of configuration on yet-to-be-discovered servers or chassis
- Create auto deployment targets
- Delete auto deployment targets
- Export auto deployment target details to different formats
- Overview of stateless deployment
- Define networks
- Edit or delete a configured network
- Export VLAN definitions
- Import network definitions
- Manage Profiles
- Managing the device configuration compliance
- Monitoring device alerts
- Manage audit logs
- Using jobs for device control
- Discovering devices for monitoring or management
- Discover servers automatically by using the server-initiated discovery feature
- Create a device discovery job
- Protocol support matrix for discovering devices
- View device discovery job details
- Edit a device discovery job
- Run a device discovery job
- Stop a device discovery job
- Specify multiple devices by importing data from the .csv file
- Globally excluding devices
- Specify discovery mode for creating a server discovery job
- Create customized device discovery job protocol for servers –Additional settings for discovery protocols
- Specify discovery mode for creating a chassis discovery job
- Create customized device discovery job protocol for Chassis – Additional settings for discovery protocols
- Specify discovery mode for creating a Dell storage discovery job
- Specify discovery mode for creating a network switch discovery job
- Create customized device discovery job protocol HTTPS storage devices –Additional settings for discovery protocols
- Create customized device discovery job protocol for SNMP devices
- Specify discovery mode for creating a MULTIPLE protocol discovery job
- Delete a device discovery job
- Managing device inventory
- Manage the device warranty
- Reports
- Managing MIB files
- Managing OpenManage Enterprise appliance settings
- Configure OpenManage Enterprise network settings
- Manage OpenManage Enterprise users
- Ending user sessions
- Directory services integration in OpenManage Enterprise
- OpenManage Enterprise login using OpenID Connect providers
- Add an OpenID Connect provider to OpenManage Enterprise
- Configure an OpenID Connect provider policy in PingFederate for role-based access to OpenManage Enterprise
- Configure an OpenID Connect provider policy in Keycloak for role-based access to OpenManage Enterprise
- Test the registration status of OpenManage Enterprise with the OpenID Connect provider
- Edit an OpenID Connect provider details in OpenManage Enterprise
- Enable OpenID Connect providers
- Delete OpenID Connect providers
- Disable OpenID Connect providers
- Security Certificates
- Set the login security properties
- Manage Console preferences
- Customize the alert display
- Configure SMTP, SNMP, and Syslog alerts
- Manage incoming alerts
- Manage warranty settings
- Check and update the version of the OpenManage Enterprise and the available plugins
- Execute remote commands and scripts
- OpenManage Mobile settings
- Enable or disable alert notifications for OpenManage Mobile
- Enable or disable OpenManage Mobile subscribers
- Delete an OpenManage Mobile subscriber
- View the alert notification service status
- Notification service status
- View information about OpenManage Mobile subscribers
- OpenManage Mobile subscriber information
- Troubleshooting OpenManage Mobile
- Other references and field descriptions
- Schedule Reference
- Firmware baseline field definitions
- Schedule job field definitions
- Alert categories after EEMI relocation
- Token substitution in remote scripts and alert policy
- Field service debug workflow
- Unblock the FSD capability
- Install or grant a signed FSD DAT.ini file
- Invoke FSD
- Disable FSD
- Catalog Management field definitions
- Firmware/driver compliance baseline reports— devices with 'Unknown' compliance status
- Generic naming convention for Dell EMC PowerEdge servers
● If there is a use case of frequent template edits, it is recommended that you associate a maximum of 100 devices per
baseline for optimal performance.
1. On the Compliance Templates page, select the corresponding check box, and then click Edit.
2. On the Template Details page, the configuration properties of the compliance template is listed.
3. Expand the property you want to edit, and then enter or select data in the fields.
a. To enable the property, select the check box, if not already enabled.
4. Click Save or Discard to implement or to reject the changes.
The compliance template is edited and the updated information is saved.
Related tasks
Manage compliance templates on page 83
Clone a compliance template on page 84
Create a configuration compliance baseline
OpenManage Enterprise can assign 10 baselines to a single device and check the compliance level of maximum 250 devices at a
time. To view the list of baselines, click OpenManage Enterprise > Configuration > Configuration Compliance.
You can create a configuration compliance baseline by:
● Using an existing deployment template. See Managing the device configuration compliance on page 82.
● Using a template captured from a support device. See Create a compliance template from reference device on page 84.
● Using a template imported from a file. See Create a compliance template by importing from a file on page 84.
When you select a template for creating a baseline, the attributes associated with the templates are also selected. However, you
can edit the baseline properties. See Edit a configuration compliance baseline on page 86.
CAUTION:
If a compliance template used for a baseline is already associated with another baseline, editing the
template properties changes the baseline compliance levels of devices already associated. Read through the
Error and Event message displayed and act accordingly. For more information about error and event messages,
see the
Error and Event Message Reference Guide
available on the support site.
NOTE: Before creating configuration compliance baseline, ensure that you have created the appropriate compliance
template.
1. Select Configuration > Configuration Compliance > Create Baseline.
2. In the Create Compliance Baseline dialog box:
● In the Baseline Information section:
a. From the Template drop-down menu, select a compliance template. For more information about templates, see
Managing the device configuration compliance on page 82.
b. Enter a compliance baseline name and description.
c. Click Next.
● In the Target section:
a. Select devices or device groups. Only compatible devices are displayed. See Select target devices and device groups on
page 103.
NOTE:
Only compatible devices are listed. If you select a group, the devices that are not compatible with
the compliance template, or the devices that do not support the configuration compliance baseline feature, are
exclusively identified to help you select effectively.
3. Click Finish.
A compliance baseline is created and listed. A compliance comparison is initiated when the baseline is created or updated.
The overall compliance level of the baseline is indicated in the COMPLIANCE column. For information about the fields in the
list, see Managing the device configuration compliance on page 82.
NOTE:
Whenever a configuration baseline is created, a configuration inventory job is automatically created and run
by the appliance to collect the inventory of the devices associated with the baseline for which the inventory data is
unavailable. This newly-created Configuration inventory job has the same name as the baseline for which the inventory
Managing the device configuration compliance 85