Objective 1.1 – Describe techniques to prepare environment for Horizon

  • Determine characteristics of Active Directory domain accounts
    • Groups, Permissions.
      • Separate groups should be created for different users within Active Directory.
      • You must join each Connection Server host to an Active Directory domain. The host must not be a domain controller.
    • Trust relationships
      • Users are authenticated using Active Directory against the View Connection Server domain and any additional user domains with which a trust agreement exists.
      • vdmadmin command is used to manage the domain lists on the connection server.
    • Describe organizational units (OUs) for machine accounts
      • You should create an organizational unit (OU) specifically for your remote desktops.
      • A client in kiosk mode is a thin client or a locked-down PC that runs the client software to connect to a Connection Server instance and launch a remote desktop session. If you configure clients in kiosk mode, you should create dedicated OUs and groups in Active Directory for kiosk mode client accounts. Creating dedicated OUs and groups for kiosk mode client accounts partitions client systems against unwarranted intrusion and simplifies client configuration and administration.
    • Select the appropriate group policy object (GPO) template file.
      • Horizon 7 includes several component-specific group policy administrative (ADMX) template files.
      • You can optimize and secure remote desktops by adding the policy settings in these files to a new or existing GPO in Active Directory and then linking that GPO to the OU that contains your desktops.
      • All ADMX files that provide group policy settings for Horizon 7 can be downloaded from the VMware Downloads site at https://my.vmware.com/web/vmware/downloads
  • Verify system requirements for installation
    • Horizon 7 supports the following Active Directory Domain Services (AD DS) domain functional levels:
      • Windows Server 2008
      • Windows Server 2008 R2
      • Windows Server 2012
      • Windows Server 2012 R2
      • Windows Server 2016
    • Horizon Connection Server Hardware Requirements
Hardware ComponentRequiredRecommended
ProcessorPentium IV 2.0GHz processor or higher4 CPUs
Network Adapter100Mpbs NIC1Gbps NICs
Memory Windows Server 2008 R2 64-bit4GB RAM or higherAt least 10GB RAM for deployments of 50 or more remote desktops
Memory Windows Server 2012 R2 64-bit4GB RAM or higherAt least 10GB RAM for deployments of 50 or more remote desktops

Operating System Support for Horizon Connection Server

Operating SystemVersionEdition
Windows Server 2008 R2 SP164-bitStandard Enterprise Datacenter
Windows Server 2012 R264-bitStandard Datacenter
Windows Server 201664-bitStandard Datacenter

Standalone View Composer Requirements

Hardware ComponentRequiredRecommended
Processor1.4 GHz or faster Intel 64 or AMD 64 processor with 2 CPUs2GHz or faster and 4 CPUs
NetworkingOne or more 10/100Mbps network interface cards (NICs)1Gbps NICs
Memory4GB RAM or higher8GB RAM or higher for deployments of 50 or more remote desktops
Disk space40GB60GB
  • Licensing
Horizon 7 Standard (CCU)Includes: VDIWorkstation (1 admin license)
vSphere Desktop
vCenter Desktop (includes 25 Operating System Instances [OSIs] of VMware vRealize Log Insight™ for vCenter for Desktop)
Horizon 7 Advanced  (Named)Includes: Horizon 7 Standard Hosted Apps (RDSH)
Horizon 7 Advanced (CCU)Virtualization pack for Skype for Business
VMware Fusion® Pro
vSAN Advanced for Desktop (Named)
Horizon 7 Enterprise  (Named)Includes: Horizon 7 Advanced App Volumes Enterprise
Horizon 7 Enterprise (CCU)User Environment Manager
Instant Clones
vRealize Operations for Horizon (includes support for third-party VDI/ RDSH environments)Help Desk Tool
Linux VDI
Horizon 7 for LinuxIncludes: Linux VDI
vSphere Desktop
vCenter Desktop

Leave a Reply

Your email address will not be published. Required fields are marked *