White Papers

Profile Management and Deployment Enhancements in OpenManage Enterprise 3.4 |438
2.1.5 Migrate Profiles
When it is time to retire a server, the migrate wizard can be used to move the profile, including all settings and
virtual identities, to its replacement. The ‘Force’ option can be used to move the profile even when the source
system is no longer available.
Options to migrate a profile.
2.2 Comprehensive Deployment Covering Target and Secure Attributes
Attributes involved in server configuration can be broadly classified into template attributes and target
attributes.
The value of a template attribute is always tied to the template and gets deployed to every target device
whenever a profile created from the template is used for deployment. Changes to template attributes affect
every profile created from the template.
The value of a target attribute is tied to a target device, so it is specific to each target device that a profile is
deployed to. Target attributes can be further classified into:
• Virtual identity attributes: Values assigned automatically by OME identity assignment logic.
• Quasi attributes: Values are inherited from the source template but can be modified on a per-target
basis.
• True target attributes: Values should be uniquely specified per deployment target.
In previous OME releases, there was no support for quasi or true target attributes in deployment. Only
template and virtual identity attributes could be deployed. Quasi attributes could also not be used to check
compliance. Several boot control attributes are Quasi attributes. In OME 3.4, quasi attributes inherit values
from the source system (from which the template is captured) and can be deployed. Also, the compliance can
be evaluated for these attributes.