- Notes, cautions, and warnings
- Revision history
- Preface
- About 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 or Windows 2022 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
- 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
- Global exclusion of ranges
- Specify discovery mode for creating a server discovery job
- Create customized device discovery jobs for servers
- Specify discovery mode for creating a chassis discovery job
- Create customized device discovery jobs for chassis
- Specify discovery mode for creating a Dell storage discovery job
- Specify discovery mode for creating a network switch discovery job
- Create customized device discovery jobs for HTTPS storage devices
- Create customized device discovery jobs for SSH devices
- Create customized device discovery jobs for SNMP devices
- Specify discovery mode for creating multiple discovery jobs
- Delete a device discovery job
- Manage devices and device groups
- Organize devices into groups
- Create a custom group (Static or Query)
- Create a Static device group
- Create a Query device group
- Edit a static group
- Edit a query group
- Rename a static or query group
- Delete a static or query device group
- Clone a static or query group
- Add devices to a new group
- Add devices to existing group
- Refresh health on group
- Devices list
- All Devices page — device list actions
- Delete devices from OpenManage Enterprise
- Exclude devices from OpenManage Enterprise
- Run inventory on devices
- Update the device firmware and drivers by using baselines
- Refresh the device health of a device group
- Refresh health on devices
- Roll back an individual device's firmware version
- Export the single device inventory
- Performing more actions on chassis and servers
- Hardware information displayed for MX7000 chassis
- Export all or selected data
- View and configure individual devices
- Organize devices into groups
- Managing device inventory
- 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
- Monitor and Manage device alerts
- Monitor audit logs
- Using jobs for device control
- Manage the device warranty
- Reports
- Managing MIB files
- Troubleshoot connections
- Managing OpenManage Enterprise appliance settings
- Configure OpenManage Enterprise network settings
- Manage OpenManage Enterprise users
- Role and scope-based access control in OpenManage Enterprise
- Add and edit OpenManage Enterprise local users
- Edit OpenManage Enterprise user properties
- Enable OpenManage Enterprise users
- Disable OpenManage Enterprise users
- Delete OpenManage Enterprise users
- Import AD and LDAP groups
- Transfer of ownership of Device Manager entities
- 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
- Manage Console preferences
- Set the login security properties
- 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
- Firmware and DSU requirement for HTTPS
- Schedule Reference
- Firmware baseline field definitions
- Supported and unsupported actions on 'Proxied' sleds
- 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
- PowerEdge server naming conventions
Dell EMC OpenManage Enterprise 3.9 User's Guide
Directory services integration in OpenManage Enterprise
Pre-requisites/supported attributes for LDAP Integration
Directory Services enables you to import directory groups from AD or LDAP for use on the console. OpenManage Enterprise supports integration of the following directory services:- Windows Active Directory
- Windows AD/LDS
- OpenLDAP
- PHP LDAP
| Attribute of User Login | Attribute of Group Membership | Certificate Requirement | |
|---|---|---|---|
| AD/LDAP | Cn, sAMAccountName | Member |
|
| OpenLDAP | uid, sn | Uniquemember | Only PEM certificate format is supported |
| PHP LDAP | uid | MemberUid |
You must ensure that the following user pre-requisites are met before you begin with the directory service integration:
- BindDN user and user used for 'Test connection' should be the same.
- If Attribute of User Login is provided, only the corresponding username value assigned to the attribute is allowed for appliance login.
- User used for Test connection should be part of any non-default group in LDAP
- Attribute of Group Membership should have either the 'userDN' or the short name (used for logging in) of the user.
- When MemberUid is used as 'Attribute of Group Membership,' the username used in appliance login will be considered case sensitive in some LDAP configurations.
- When search filter is used in LDAP configuration, user login is not allowed for those users who is not part of the search criteria mentioned.
- Group search will work only if the groups have users assigned under the provided Attribute of Group Membership .
NOTE If the OpenManage Enterprise is hosted on an IPv6 network, the SSL authentication against domain controller using FQDN would fail if IPv4 is set as preferred address in DNS. To avoid this failure, do one of the following:
- DNS should be set to return IPv6 as preferred address when queried with FQDN.
- DC certificate needs to have IPv6 in SAN field.
- Add a directory connection. See Add or edit Active Directory groups to be used with Directory Services.
- Import directory groups and map all users in the group to a specific role. See Import AD and LDAP groups.
- For DM users, edit the directory group to add the groups the DM can manage. See Add and edit OpenManage Enterprise local users.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\