VMware Horizon 7 has been installed in the VMware Cloud on AWS data center.  We also have an on-premises instance of VMware Horizon 7.  This is managed by the on-premises vCenter to which we connected the VMware Cloud on AWS vCenter in an earlier step.  We have already authenticated you as the Horizon Administrator for each of these Horizon 7 instances.  

We begin at the Horizon Administrator for the on-premises Horizon 7 instance.  

1. Click on View Configuration.
2. Click on Cloud Pod Architecture
3. Click on Initialize the Cloud Pod Architecture feature
4. Click OK
5. 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.    
6. Click on the browser tab to the right of the first site View Administrator to open the second View Administrator tab for the second site.
7. Click on Cloud Pod Architecture
8. Click on Join the pod federation
9. Type viewaws.controlbytouch.com
10. Click in the User Name field
11. Type controlbytouch\administrator
12. Click in the Password field
13. Type VMware123!
14. Click OK.
15. 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.  

1. Click Sites
2. Click Add
3. Type Secondary in the Name field
4. Click OK.  You will now see 2 sites listed.
5. Click on Default First Site
6. Click Cluster-VIEWONPREM
7. Click on the Edit button under Sites
8. Click on Site pulldown menu
9. Click on Secondary
10. Click OK.  Now we have 2 sites with 1 pod each and a Cloud Pod Architecture federation between the 2 sites.

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.  

1. Click on Catalog
2. Click Global Entitlements
3. Click Add
4. Click Next to add a Desktop Entitlement.  
5. Type 1803.  We will be entitling users to a Windows 10 1803 desktop
6. Click Next to accept the default settings
7. Click Add
8. Click in the Name/User Name field
9. Type users
10. Click Find
11. Click Domain Users
12. Click OK.  We have entitled all Domain Users to the Windows 10 1803 desktop Global Entitlement.  
13. Click Next
14. Click Finish.  You can now see the dedicated desktop Global Entitlement for 1803 to which we will add desktop pools from each site.

1. Click on 1803.
2. Click on 1803 again
3. Click Local Pools tab
4. Click Add
5. Click 1803b
6. Click Add.  We have now added a pool of Windows 10 1803 desktops we previously created to the Global Entitlement.  

1. Click on the View Administrator browser tab to the left of the one in which you are currently working.  This will return you to managing the first site.  
2. Click on 1803
3. Click on 1803 again
4. Click Local Pools tab
5. Click Add
6. Click 1803
7. Click 1803 again
8. 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 or between two VMware Cloud on AWS SDDCs.

To return to the lab, click the link in the top right corner or close this browser tab.