Introduction

This module, Deploy and Configure a Horizon Connection Server, builds upon the knowledge gained from Module one. In module one you were exposed to the various components and their roles within the VDI ecosystem. There are two goals of this module:

  1. The first goal is to provide a hands-on experience in the deployment of the main VDI component, the Horizon Connection Server.
  2. The second goal is to provide you with a reference, essential information, and steps to be able to deploy your own lab or POC environment.

Modules three and four provide similar in-depth tutorials for deploying VDI enhancement solutions App Volumes and User Environment Manager. This will allow you to test and evaluate the entire Horizon VDI suite and experience first hand the art of what's possible in your own environment with your own applications and desktops.

Horizon Connection Server POC/LAB Prerequisites

To successfully deploy a Horizon Connection Server, you will need the following:

  • Windows Server 201x server
  • 2-4 CPUs (Depending on number of desktops being deployed 4 CPUs recommended for over 50 desktops)
  • 4-10 Gigabytes of RAM (Depending on number of desktops being deployed 10+ GB RAM recommended for over 50 desktops)
  • 60-100 GB Hard Disk
  • Desktop dedicated vCenter (appliance recommended but not required, hosted outside of the desktop cluster)
  • Static IP Address
  • DNS Registration Resolvable FQDN (Short, Long, Reverse)
  • Isolated management cluster or host for the Connection Server.
  • While it is possible to run the Connection Server and the desktops on the same cluster for very small lab environments, production implementations should always have separate management and desktop clusters.
  • Horizon Connection Server installer downloaded from VMware.com
  • License key for Horizon (Demo Key available for free)
  • For a comprehensive walk-through in setting up a lab or POC please see the Quick-Start Tutorial for VMware Horizon 7.
  • An Active Directory Service Account with a dedicated and delegated OU with blocked inheritance and permissions as described in Create a User Account for Instant-Clone Operations.
  • An additional Active Directory or local service account with administrator permissions in vCenter or that have the roles and privileges described in View Composer and Instant Clone Privileges Required for the vCenter Server User.

0 Comments

Add your comment

E-Mail me when someone replies to this comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.