Dell OpenManage Enterprise version 4.5

Enhancements:
- Integration of Power Management features
-Support for automatic physical hierarchy creation using device location information
- Support for staggered power on and power off operation on the devices in a rack
- Support for rack-level GPU and CPU reporting
- Support for Azure Stack HCI platforms
- Support for Dell switches with SONiC OS
- Support for Power Shelf
- Improved scalability for discovery and inventory
- Live message notification
- Support for SHA-384 and SHA-512 hashing algorithms and AES-256 encryption for enhanced security

Fixes:
- OpenManage Enterprise now supports firmware updates for AX devices. Previously, AX devices appeared grayed out in the compliance report when included in a compliance baseline with other devices.
- Fixed an issue where syslog forwarding skipped informational alerts after upgrading to version 4.3.2.
- Fixed an issue where entities created by OIDC users were deleted from the OpenManage Enterprise database upon reboot, disrupting scheduled jobs, firmware baselines, compliance reports, template configurations and deployments, baselines, profiles, alert policies, and reports.
- Fixed an issue where deleting a parent group using the DELETE /api/GroupService/Groups(id) API did not remove its associated child groups. This caused orphaned groups to persist in the API response while remaining hidden in the web interface.
- Fixed an issue where onboarding tasks failed when a user with a custom role and access to a single static group created a discovery task.
- Rolling back the firmware version of a PowerEdge 17G server (iDRAC 10) to a lower version now completes successfully.
- Newly imported MIB files are now correctly listed in the Category selection when creating an alert policy within the Create Alert Policy wizard.
- Deleted custom MIB files no longer appear in the Category selection of the Create Alert Policy wizard, when navigating to the Alert Policies page to create a new policy.
- If Ping Identity is used for OIDC provider, the appliance can only be used with Administrator role. With OIDC provider PingFederate, it is observed that all the OpenID client policies associated with the OpenManage Enterprise Client IDs are reset to the policy marked as 'Default' when the appliance console gets re-registered with the OIDC provider. Re-registration of the appliance console with an OIDC provider happens if there is an appliance upgrade, change in network configuration, or change in SSL certificate.
- Ownership information for device managers (AD/LDAP and OIDC) is lost on appliance upgrade. Post upgrade of OpenManage Enterprise from version 3.5 or earlier versions, the AD/LDAP, and OIDC (Ping-Federate or Keycloak) device managers must re-create all the previous-version entities such as jobs, alert policies, configuration templates, configuration baselines, profiles, firmware baselines, firmware catalogs, and reports as these entities are only available to the administrators post upgrade.
- When OpenManage Enterprise is restarted on a new or an upgraded appliance, the associated user IDs of policies and EPR entities that are created by an OIDC user is deleted from the OpenManage Enterprise database. This deletion disrupts the functionality of various entities such as scheduled jobs for reports, EPR, policies, and restore job when performed with a backup file. You cannot view existing EPR or policies, nor create an EPR or policies even with administrator privileges.
- After the default inventory job is completed, the devices are removed from power management and monitoring if OpenManage Enterprise is unable to communicate with the device. After the fix, devices having licenses continue to be power-managed and monitored even if the device communication is unsuccessful during an inventory job.