As the system administrator, you want to configure your
vRealize Automation instance as an ongoing development environment. You create local user accounts and assign yourself to the tenant administrator role. Using the tenant administrator privileges, you start configuring vRealize Automation as a development environment for building and testing blueprints.
Scenario: Create Local User Accounts for Rainpole Using your default system administrator privileges, you create two local user accounts in the default tenant. Assign one of these accounts to the tenant administrator role so you can start configuring the default tenant. You can use the second account later as a shared login for your architects to test blueprint and catalog access.
Scenario: Connect Your Corporate Active Directory to vRealize Automation for Rainpole As a tenant administrator, you want vRealize Automation to authenticate logins against your corporate active directory. You configure a connection between vRealize Automation and your single domain active directory over LDAP.
Scenario: Configure Branding for the Default Tenant for Rainpole Using your tenant administrator privileges, you customize the look and feel of the vRealize Automation console. You upload a new logo, change the colors, update the header and footer information, and configure the login screen branding.
Scenario: Create a Custom Group for Your Rainpole Architects Using your tenant administrator privileges, you create a custom group for members of your IT organization who need highly privileged access to vRealize Automation. You assign roles to this custom group as you configure vRealize Automation.
Scenario: Assign IaaS Administrator Privileges to Your Custom Group of Rainpole Architects Using your default system administrator privileges, you assign your custom group to the IaaS administrator role to allow the group to configure IaaS resources.