Unix Privileged Account profile This Run As profile and its associated UNIX or Linux  – credentials are used for activities that are protected by a higher level of security and therefore require an account that has higher privileges on the UNIX or Linux computer. This can be (but does not have to be) the root account. You will need to configure these profiles with the appropriate UNIX or Linux computer credentials for the management pack workflows that use them to function correctly. Accounts and Groups Over the lifetime of your Operations Manager deployment, you will potentially need many accounts and security groups. During Operations Manager Setup, you are only prompted for four. You need to consider additional accounts when planning out role-based security assignments, notifications, and alternate credentials to run processes. For guidance on planning role-based security assignments, see . Role-Based Security Accounts and Groups Operations Manager controls access to monitored groups, tasks, views, and administrative functions through the assignment of user accounts to roles. A role in Operations Manager is the combination of a profile type (operator, advanced operator, administrator) and a scope (what data the role has access to). Typically, Active Directory security groups are assigned to roles, and then individual accounts are assigned to those groups. Prior to deploying, plan out Active Directory security groups that can be added to these and any custom-created roles so that you can then add individual user accounts to the security groups. Operations Manager provides the following role definitions out-of-the-box. Role name Profile type Profile description Role scope Operations Manager Administrator Has full privileges to Full access to all Administrators: Operations Manager; Operations Manager Created at setup; no scoping of the data, services, cannot be deleted; Administrator profile is administrative, and must contain one or supported authoring tools more global groups Operations Manager Advanced Operator Has limited change Access to all groups, Advanced Operators: access to Operations views, and tasks Created at Manager currently present and globally scoped; cannot configuration; ability to those imported in the be deleted create overrides to future rules; monitors for targets or groups of targets within the configured scope
 Unix Privileged Account profile – This Run As profile and its associated UNIX or Linux credentials are used for activities that are protected by a higher level of security and therefore require an account that has higher privileges on the UNIX or Linux computer. This can be (but does not have to be) the root account. You will need to configure these profiles with the appropriate UNIX or Linux computer credentials for the management pack workflows that use them to function correctly. Accounts and Groups Over the lifetime of your Operations Manager deployment, you will potentially need many accounts and security groups. During Operations Manager Setup, you are only prompted for four. You need to consider additional accounts when planning out role-based security assignments, notifications, and alternate credentials to run processes. For guidance on planning role-based security assignments, see . Role-Based Security Accounts and Groups Operations Manager controls access to monitored groups, tasks, views, and administrative functions through the assignment of user accounts to roles. A role in Operations Manager is the combination of a profile type (operator, advanced operator, administrator) and a scope (what data the role has access to). Typically, Active Directory security groups are assigned to roles, and then individual accounts are assigned to those groups. Prior to deploying, plan out Active Directory security groups that can be added to these and any custom-created roles so that you can then add individual user accounts to the security groups. Operations Manager provides the following role definitions out-of-the-box. Role name Profile type Profile description Role scope Operations Manager Administrators: Created at setup; cannot be deleted; must contain one or more global groups Administrator Has full privileges to Operations Manager; no scoping of the Administrator profile is supported Full access to all Operations Manager data, services, administrative, and authoring tools Operations Manager Advanced Operators: Created at globally scoped; cannot be deleted Advanced Operator Has limited change access to Operations Manager configuration; ability to create overrides to rules; monitors for targets or groups of targets within the configured scope Access to all groups, views, and tasks currently present and those imported in the future
SC2012_OpsMgr_Deployment.docx