Introduction to Vmware View Infrastructure

Introduction to VMware Horizon View

It’s a collection of products which covers both virtual desktops, physical desktops, RDS hosts and virtual applications. There are 3 editions of VMware Horizon; Standard, Advanced and Enterprise

Horizon View Standard provides virtual desktops via View. However it also includes View Composer, licensing for vSphere/vCenter Desktop and ThinApp.

The Advanced and Enterprise editions add features such as RDS hosted applications, VSAN and vCOps monitoring amongst other features such as physical desktop image management (aka Mirage).

Components of View environment:

  • View Connection Server – An internal server which manages, provisions and brokers connections to desktops
  • View Security Server – A server in the DMZ paired with a Connection Server to provide remote access to desktops from the internet. This is optional
  • View Composer  – Used to create linked clones desktop pools, improving virtual desktop management and providing storage savings
  • View Agent – Installed within each virtual desktop or RDS host so the client can connect to it
  • View Client – Installed on the end user’s computer and is used to connect to the Connection Server and virtual desktop for user.
  • ThinApp – Used to create a virtual package of an application to run on virtual or physical desktops. Installation of ThinApp is optional.

1) View Connection Server

The VMware Horizon View Connection Server is a critical component required for View to function.

At least 1 Connection Server is required in a View deployment. Depending on the size of the implementation, additional Connection Servers may be required to accommodate the number of users, whether or not external access is required and if the design includes high availability.

The View Connection Server must be installed on its own dedicated server. It must NOT be installed on the vCenter server or a domain controller.

Connection Server Types:

  • Standard Server – Is the first instance of a group of Connection Servers.
  • Replica Server – Additional Standard Connection Servers are called Replica Servers. Replica Servers can be used to provide high‐availability and load balancing. Each replica server has a local AD LDS instance (using Microsoft’s ADAM), the View LDAP data on the replica server is copied from an existing View Connection Server when a new one is installed.
  • Security Server – In a DMZ a Security server can be installed to add additional protection. Security servers ensure only authenticated users can connect to the internal network from external locations by providing a single point of access.

Minimum requirements for View Connection Server(s) are as follows:
The View Connection Server can be physical or virtual.

Pentium IV 2.0GHz Processor or Higher (Recommended: 4 vCPUs for 50 desktops or more)


4 GB RAM or higher (Recommended: 10GB vRAM for 50 desktops or more)

1Gbps vNIC

Operating System:
Windows Server 2008 R2 (Standard/Enterprise)
Windows Server 2012 R2 (Standard)

2)  View Composer

Horizon View Composer offers features such as storage reduction, improved OS management and rapid desktop deployment.

VMware Horizon View Composer uses linked clones to provide a 50% to 90% reduction in storage requirements for virtual desktops. If View Composer is not used, 100’s or 1,000’s of desktops 25GB+ in size would exhaust expensive SAN storage.

Horizon View Composer does this by using creating linked clones from a parent disk, instead of full clones. This creates what is known as a “diff disk” of the differences between the parent disk and itself once the virtual desktop is powered on. Without the parent disk the linked clones will not work.

The different could be instead of each desktop requiring 25GB+ of space each, the linked clone may only be around 5GB in size. This varies depending on the amount of changes in the desktop during the day, memory/pagefile size and also if the virtual desktop is refresh or deleted after each logoff.

Minimum requirements for Horizon View Composer are as follows:
Horizon View Composer can be installed on the same Windows server as vCenter Server (if it meets the requirements) or on a standalone server. View Composer should not be installed on the same server as View Connection Server.


1.4 GHz or faster Intel 64 or AMD 64 processor with 2 CPUs (Recommended: 2GHz or faster and 4 CPUs)

4 GB RAM or higher (Recommended: 8GB vRAM for 50 desktops or more)

1Gbps vNIC

Operating System:
Windows Server 2008 R2 (Standard/Enterprise)
Windows Server 2012 R2 (Standard)

SQL Server Database:
SQL Server 2008 SP3
SQL Server 2008 R2 SP2
SQL Server 2012 SP1

Before setting up view infrastructure make sure you vSphere environment is correctly setup. Esxi and vCenter already installed with shared storage. If everything is ready then you are ready to go.

Follow the below series of posts to setup view infrastructure.

Part-1- Installing View Composer

Part-2- Installing View Connection Server

Part-3- Configuring View Connection Server

Part-4-Configuring Event Database for View 5

Part-5-VMware View-agent Installation

9 thoughts on “Introduction to Vmware View Infrastructure

  1. Pingback: VMware View 5 Installation-Part 4 | Go Virtual.
  2. Pingback: VMware View 5 Installation-Part 5 | Go Virtual.
  3. Pingback: VMware View 5 Installation- Part 1 | Go Virtual.
  4. Pingback: VMware View 5 Installation-Part 2 | Go Virtual.
  5. Pingback: VMware View 5 Installation-Part 3 | Go Virtual.
  6. Pingback: VMware View 5 Installation-Part 5 – Virtual Reality
  7. Pingback: VMware View 5 Installation-Part 4 – Virtual Reality
  8. Pingback: VMware View 5 Installation-Part 2 – Virtual Reality
  9. Pingback: VMware View 5 Installation- Part 1 – Virtual Reality