White Papers

Scope Based Access Control with OpenManage Enterprise 3.6|Document ID: 21396 P a g e | 12
Configuration:
Configuration compliance:
Template Management
Yes.
Device Managers can see only the compliance
templates they own.
Configuration:
Configuration Compliance:
Baselines
Yes.
Device Managers can see only the compliance
baselines they own.
Configuration:
Configuration Compliance:
Compliance Report
No changes.
Given a set of targets, make compliant should
only run for those targets that are in the Device
Manager’s scope.
Configuration: Identity
Pools
Minor changes.
Identity pools are treated as community entities.
Pool usage counts reflect total usage from pools.
The grid shows the usage details as applicable to
the Device Manager’s scope. (i.e., if there are
devices outside the Device Manager’s scope that
are using virtual identities from an identity pool,
that usage info will not be shown in the grid).
Configuration: VLANs
No changes.
VLANs are treated as community entities.
Alerts: Alert Log
Yes.
Device Managers can see only the alerts from
devices in their scope, any appliance alerts and
any alerts from un-discovered devices.
Alerts: Alert Policies
Yes.
Device Managers can see only the built-in alert
policies and any alert policies they own. “Edit /
Enable / Disable / Delete” are not allowed for
built-in policies.
Target Picker only shows devices / groups that
are in the Device Manager’s scope.
Monitor: Audit Logs
No changes.
Device Managers can see all activity on the
console.
Monitor: Jobs
Yes.
Device Managers can see built-in jobs and jobs
that they own. “Enable / Disable / Delete” are not
allowed for built-in jobs. When any job runs, it