This will be a short one. During the installation, a configurationadmin was created
This is great, because it helps a lot as the configurationadmin is already in the right permission groups to do all you need, well a lot anyway. In order to create a new tenant you will need to login using firstname.lastname@example.org and if you want, use it or give yourself the required permissions.
Anyway, here I presume you have indeed opt-in – why wouldn’t you 🙂 I will however use this user only to login in order to configure vRA7 – I won’t actually make use of the workflow this user will have access to. I’ll show that in a bit.
Anyway, browse to your newly installed vRA environment
Once logged in with your configurationadmin, you will see the configuration workflow I was referring to (see Catalog).
As I say – I will skip this, but by no means – hit it if you like – it will take a lot of the headache away, but I still prefer to do things the old way -if anything then simply to know how this is done manually. As a consultant I can’t always rely on the workflow to be present 🙂
Plus, to be perfectly honest, I don’t think this is the most intuitive one.
From this point on you can also login as System Administrator (email@example.com) and the password you have specified during the install.
This will allow you to create new tenants or give additional permissions to the default tenant.
Here for example click vsphere.local
You can see I also added a domain user to the Tenant and IaaS Administrator – at this stage you won’t be able to do so unless you already added a Directory – but more to that in a later article.
Anyway, as I said – this is a short one, follow the next articles where I do actual ‘stuff’ 😉