White Papers

Profile Management and Deployment Enhancements in OpenManage Enterprise 3.4 |438
1 Background and Overview
This technical white paper outlines how OME 3.4 addresses many feature gaps and customer issues in
device Configuration and Deployment. The following are the key features that are implemented and the
customer issues that have been addressed:
• Profile Management Portal
- Ability to generate profiles with settings and virtual identities for deployment to a device that
are discovered or yet to be discovered using Service Tag.
- Ability to easily view what was deployed to a device (settings and virtual identities).
- Ability to easily view what has changed on the profile since the last deployment.
- Ability to deploy just the delta or change-set on the profile only. Thereby, reducing overall
deployment time.
- Problem-free part replacement using full redeployment of profile.
- Easier server retirement or replacement via unassign and assign of a profile or migrate profile
actions.
• Boot Attribute deployment without caveats
- Previous releases had the restriction that to deploy boot attributes, a template had to be
associated with an identity pool and boot attributes could only be seen in the context of
identity reservation. In previous releases, boot attributes could not be included for
configuration compliance either.
• Deployment covers all attributes
- In previous releases, deployment did not include secure or target specific attributes. The only
target specific attributes that were supported were the virtual identity attributes.
• Intelligent Identity pools
- Identity pool definitions are not fixed, so it is possible that there are intersections with pool
definitions in other OME instances or other consoles. Previously, OME was unable to detect
any externally assigned identity intersection with identity pools and so could potentially
inadvertently cause a virtual identity conflict.
• Easier workflows to manage OME-M sleds
- In previous releases, when OME was used to manage multiple MX-7000chassis, the
workflows involved repetitive steps to re-create networks on OME. OME-M Sleds would also
need to be rebooted to apply VLAN changes as applying VLAN changes was tightly
integrated with template deployment.
1.1 Audience
The information in this white paper is intended for users who have some familiarity with the OME
Configuration and Deployment workflows for template creation, identity pool creation, template deployment,
configuration compliance, and so on. For comprehensive detail of all these features, see the OpenManage
Enterprise 3.4 User’s guide and OpenManage Enterprise Version 3.4 and OpenManage Enterprise – Modular
Edition Version 1.20.00 RESTful API guide.