This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.
The orange boxes show where to click, and the left and right arrow keys can also be used to move through the simulation in either direction.
To return to the lab, click the link in the top right corner or close this browser tab.
Deploy a new SDDC in VMware Cloud on AWS
In this step you will deploy the SDDC infrastructure in VMware Cloud on AWS on which Horizon 7 will be installed.
- Click the Create SDDC button
- Click on the AWS Region field
- Click on EU (London)
- Click in the SDDC Name field.
- Type HoL
- Click on the Number of Hosts field
- Click on 1. This will deploy a minimal installation suitable for a Proof of Concept.
- Click Next
- Click Next
- Click on the Deploy SDDC button. This process takes between 90 minutes and 2 hours, but we have sped it up for the purposes of this lab simulation. This will deploy an entire SDDC including vCenter, vSphere host(s), VSAN storage, and NSX networking.
Request a Public IP for Compute Gateway
In this step, we will get a public IP address for the gateway that we will use to connect to the compute resources in the VMware Cloud on AWS SDDC.
- Click View Details
- Click the Networking & Security tab
- Click the scroll bar on the left to scroll down
- Click System > Public IPs
- Click Request New IP
- Click Save. See the new public IP that we will use in the next step.
Setup IPSEC between On-premises and VMC datacenters
- Click on VPN to expand the menu
- Click on Policy Based
- Click Add VPN button
- Click in the VPN Name field
- Type OnPremises
- Click in the Remote Public IP field
- Type 80.127.105.12 This is the IP address for the On-premises datacenter to which we are connecting this VMware Cloud on AWS datacenter.
- Click in the Remote Networks field
- Type 10.0.0.0/16
- Click in the Local Networks field
- Click to scroll right
- Click on sddc-cgw-ne...
- Click in Select Networks
- Click infrastructure s...
- Click on scroll bar on right
- Click in Preshared Key field
- Type VMware1!
- Click Save
- You can now see the IPSEC network between the On-premise and VMware Cloud network is up and running. Note the green status indicator and Up status. We now have a secure connection between our on-premises datacenter and the VMware Cloud on AWS SDDC.
Make VMware Cloud vCenter Accessible from On-premises datacenter
- Click on Settings tab
- Click on vCenter FQDN
- Click on EDIT
- Click on the Public IP dropdown below Resolution Address
- Click on Private IP: 10.2.224.4
- Click on Save
- Click on Networking & Security tab
- Click on Inventory > Groups
- Click on Management Groups
- Click the Add Group button
- Click in the Name field
- Type ONPremises
- Click in Members field
- Type 10.0.0.0/16 This is the On-premsies subnet
- Click Save
- Click on Workload Groups
- Click the Add Group button
- Click in the Name field
- Type vCenter
- Click in the Member type field
- Click on IP Address
- Click in Members field
- Type 10.2.224.4 This is the internal subnet of the vCenter on VMware Cloud on AWS.
- Click the Save button
- Click on Security > Edge Firewall
- Click the Add New Rule button
- Click in the Name field
- Type vCenter Inbound Rule
- Click on Set Source
- Click on User Defined Groups radio button
- Click the Select box on the ONPremises line
- Click in scroll bar on right to scroll down
- Click Save
- Click Set Destination
- Click the Select box on the vCenter line
- Click on scroll bar on far right to scroll down
- Click Save
- Click in Services field
- Click on HTTPS (TCP 4..
- Click on SSO (TCP 744..
- Click on ICMP (ALL ICM..
- Click on Publish button. This configures the firewall rules to allow the on-premises datacenter vCenter to reach the VMware Cloud vCenter on HTTPS, SSO, and ICMP
- Click on Settings tab
- Click Default vCenter User Account
- Click on the eye symbol next to password to reveal the password. You can now see the admin username and password for the VMware Cloud on AWS vCenter
- Click on Sphere Client (HTML5). You can now see the URL to access the vSphere HTML5 client for the vCenter for the VMware Cloud on AWS SDDC. This gives you all the information you need to connect to vCenter in the VMware Cloud on AWS SDDC and install VMware Horizon as you normally would.
- Click on the vCenter URL. We have already logged you into the vSphere Client using the credentials you saw above. Take a look and see that you are now logged into the vCenter for the VMware Cloud on AWS SDDC. You can see the single ESXi host we deployed and the NSX components that were deployed in the first part of the lab. You now have a complete datacenter including NSX networking, storage and compute ready to deploy VMware Horizon 7. This step will be completed for you before we move on to showing Cloud Pod Architecture federation. The important concept to keep in mind is that deploying Horizon 7 in this SDDC is the same as deploying it in an on-premises datacenter. The work of deploying the datacenter has been completed by the automation in VMware Cloud on AWS.
Setup a Cloud Pod Architecture Federation
VMware Horizon 7 has been installed in the VMware Cloud on AWS data center. We also have an on-premise instance of VMware Horizon 7. This is managed by the on-remises vCenter to which we connected the VMware Cloud on AWS vCenter in an earlier step. We have already authenticated you as an administrator the Horizon Administrator for each of these Horizon 7 instances.
- Click on the browser tab to the right of the vCenter tab that is already open. This is the Horizon Administrator for the on-premises Horizon 7 instance.
- Click on View Configuration.
- Click on Cloud Pod Architecture
- Click on Initialize the Cloud Pod Architecture feature
- Click OK
- Click OK to reload the client to get the current status. This has initialized the Cloud Pod Architecture from the first site. Now we need to join the federation from the second site in the VMware Cloud on AWS SDDC.
- Click on the browser tab to the right of the first site Horizon Administrator to open the second Horizon Administrator tab for the second site.
- Click on Cloud Pod Architecture
- Click on Join the pod federation
- Type viewaws.controlbytouch.com
- Click in the User Name field
- Type controlbytouch\administrator
- Click in the Password field
- Type VMware123!
- Click OK.
- Click OK. The Cloud Pod Architecture federation is now established between the Horizon 7 pods on-premises and in the VMware Cloud on AWS SDDC. You can see both sites are listed as Default First Sites since we have not yet setup other sites. We will now setup a secondary site and add a pod to the secondary site.
Create a Secondary site and attach on-premises pod to secondary site
- Click Sites
- Click Add
- Type Secondary in the Name field
- Click OK. You will now see 2 sites listed.
- Click on Default First Site
- Click Cluster-VIEWONPREM
- Click on the Edit button under Sites
- Click on Site pulldown menu
- Click on Secondary
- Click OK. Now we have 2 sites with 1 pod each and a Cloud Pod Architecture between the 2 sites.
Create a Global Entitlement for a Win10 Desktop
A Cloud Pod Architecture Global Entitlement allows us to create a desktop or application entitlement that spans across Horizon pods. In this case we will create a Windows 10 desktop entitlement that has desktops from pods in both sites. This can be used to expand the pool size beyond the default sizes or for disaster recovery to route a user automatically to a desktop or application resource in another datacenter in the event of a failure.
- Click on Catalog
- Click Global Entitlements
- Click Add
- Click Next to add a Desktop Entitlement.
- Click in the Name field
- Type 1803. We will be entitling users to a Windows 10 1803 desktop
- Click Next to accept the default settings
- Click Add
- Click in the Name/User Name field
- Type users
- Click Find
- Click Domain Users
- Click OK. We have entitled all Domain Users to the Windows 10 1803 desktop Global Entitlement.
- Click Next
- Click Finish. You can now see the dedicated desktop Global Entitlement for 1803 to which we will add desktop pools from each site.
Add Desktop Pools from the VMware Cloud Site to the Global Entitlement
- Click on 1803.
- Click on 1803 again
- Click Local Pools tab
- Click Add
- Click 1803b
- Click Add. We have now added a pool of Windows 10 1803 desktops we previously created to the Global Entitlement.
Add Desktop Pools from VMware Cloud Site to Global Entitlement
- Click on the View Administrator browser tab to the left of the one in which you are currently working
- Click on 1803
- Click on 1803 again
- Click Local Pools tab
- Click Add
- Click 1803
- Click 1803 again
- Click Add. We have now created a Global Entitlement for a Windows 10 desktop using desktop pools from both sites, including an on-premises and cloud-based Horizon 7 instance. This works exactly the same as if you were using two on-premises Horizon 7 instances.