In this multi-part series we will deploy the Identity Appliance, the vCAC Appliance, the Windows IaaS components, ITBM standard, Application Services, and then do a basic tenant setup.
Notice this deployment is not going to be production ready but will give you hands on pretty quickly.
- Part 1 – Identity Appliance
- Part 2 – vCAC Appliance
- Part 3 – Windows IaaS Install
- Part 4 – Initial Tenant Configuration
- Part 5 – License, Endpoint, Group, Reservation, Blueprint, and Entitlement
- Part 6 – ITBM
- Part 7 – Basic Application Services
In Part 2 we go through the basic build out of the vCAC Appliance. If you haven’t yet please walk through the configuration of your Identity Appliance in Part 1.
Now let’s step through the deployment of the OVF or OVA.
Browse to the location of your OVF or OVA.
Review details.
Review the EULA and accept.
Name your virtual machine (I choose the fqdn for my deployment).
Select disk location and type.
Select the network you plan to deploy the virtual appliance to, *Notice this needs to be available from the SSO and IaaS components.
Enter the settings for your virtual machine
- Enter and confirm the root password
- Select if you wish to enable SSH
- Set your hostname – USE FQDN!!!
- Set your default gateway
- Set your DNS servers
- Set your network IP address
- Set your netmask
Check power on and click finish. This process will take a few moments depending on your storage and network configuration
Now launch a web browser go to https://fqdn:5480 in my example I used https://vcac-va-ng.biteback.records:5480
Login with root and the password you just defined.
In the System tab go to Time Zone and set it to your local time zone.
In the Admin tab under Time Settings define your ntp servers and save settings. I HIGHLY recommend not using host time because if the host time drifts there’s no warning and it will create issues with the vCAC components.
In the vCAC Settings tab you will Resolve Host Name and save settings if it populates correctly. If not you will need to review your DNS configuration!
In the vCAC Settings tab under SSL you will generate a new certificate.
Once complete you the SSL setting it give you see the SSL Certificate is replaced successfully.
In the vCAC Settings tab under SSO you will fill out the details from the Identity Appliance
- Enter the FQDN hostname of your SSO or Identity Appliance and append the :7444 port number
- Default Tenant cannot be changed
- administrator@vsphere.local
- Set the admin password you defined when configuring the Identity Appliance
Verify the certificate when prompted
This process will take some time to complete as it is configuring all of the SSO details. Once complete you will see the configuration is updated successfully.
In the vCAC Settings tab under Licensing you will want to wait till it returns No valid licenses. Then you can enter your license key.
Once validated you will see the details of the license key
Now we will navigate to the default tenant configuration page so we can verify everything has been setup prior to moving on to the windows component installs. My url is https://vcac-va-ng.biteback.records/vcac
Login with your administrator@vsphere.local
Assuming everything worked as expected you will see this as the result of your login.
Now that you have configured the virtual appliances the next step in Part 3 will be to build the windows components.
