vRealize Operations provides backward compatibility for users of the earlier version of vRealize Operations, so that users of vCenter Server who have privileges in the earlier version in vCenter Server can log in to vRealize Operations.

When you register vRealize Operations in vCenter Server, certain roles become available in vCenter Server.
  • The Administrator account in the previous version of vRealize Operations maps to the PowerUser role.
  • The Operator account in the previous version of vRealize Operations maps to the ReadOnly role.

During registration, all roles in vRealize Operations, except for vRealize Operations Administrator, Maintenance, and Migration, become available dynamically in vCenter Server. Administrators in vCenter Server have all of the roles in vRealize Operations that map during registration, but these administrator accounts only receive a specific role on the root folder in vCenter Server if it is specially assigned.

Registration of vRealize Operations with vCenter Server is optional. If users choose not to register vRealize Operations with vCenter Server, a vCenter Server administrator can still use their user name and password to log in to vRealize Operations, but these users cannot use the vCenter Server session ID to log in. In this case, typical vCenter Server users must have one or more vRealize Operations roles to log in to vRealize Operations.

When multiple instances of vCenter Server are added to vRealize Operations, user credentials become valid for all of the vCenter Server instances. When a user logs in to vRealize Operations, if the user selects all vCenter Server options during login, vRealize Operations requires that the user's credentials are valid for all of the vCenter Server instances. If a user account is only valid for a single vCenter Server instance, that user can select the vCenter Server instance from the login drop-down menu to log in to vRealize Operations.

vCenter Server users who log in to vRealize Operations must have one or more of the following roles in vCenter Server:

  • vRealize Operations Content Admin Role
  • vRealize Operations General User Role 1
  • vRealize Operations General User Role 2
  • vRealize Operations General User Role 3
  • vRealize Operations General User Role 4
  • vRealize Operations Power User Role
  • vRealize Operations Power User without Remediation Actions Role
  • vRealize Operations Read Only Role

For more information about vCenter Server users, groups, and roles, see the vCenter Server documentation.