Create, clone, and edit compliance baseline templates using a deployment template, reference device, or importing from a file.
Use compliance template to create compliance baselines and then periodically check the configuration compliance status of devices that are associated with the baseline. See
Configuration compliance.
You can create compliance templates by using deployment template, reference device, importing from a file. See
Manage compliance templates.
NOTE:
To perform any tasks on OpenManage Enterprise, you must have necessary role-based user privileges and scope-based operational access to the devices. See
Role and scope-based access
For best results with deploying templates ensure that your source and target are of like hardware and configurations. Otherwise, attributes that are not available on the target could cause an failure with the compliance deployment.
The compliance templates associated to baselines are not dynamic. Newer attributes that are added by either the addition of new hardware or update firmware will not be captured in the base template. To perform compliance against any new attributes, create a new compliance template and then create a new baseline.
By selecting
Configuration > Configuration Compliance > Template Management, you can view the list of compliance templates based on the scope-based access that you have in OpenManage Enterprise. For example, an administrator can view and manage all the compliance templates, however, device managers can only view and manage the templates that they create and own. On this screen:
Export report about a compliance template. On the
Compliance Templates screen, select the corresponding check box, and then click
Export. See
Export data.
Delete a compliance template. On the
Compliance Templates screen, select the corresponding check box, and then click
Delete.
Configuration compliance is scalable to a maximum of 6,000 devices. To efficiently manage large-scale configuration compliance activity do the following:
Disable the default Configuration Inventory task that is triggered automatically and run it manually when needed.
Create compliance baselines with lesser number of devices. For example, 6,000 devices must be categorized into four separate baselines with 1,500 devices each.
All the baselines should not be checked for compliance at the same time.
NOTE:When you edit a compliance template, configuration compliance is automatically triggered on all the baselines that it is associated with. If there is a use case of frequent template edits the above scale environment is unsupported, and it is recommended that you associate a maximum of 100 devices per baseline for optimal performance.