What is a Connection Server? A connection server is the main component of the entire VMware View Suite. Without it, our View environment will not function. So, what does the connection server do? Well the most simple answer; it allows the user to access their respective entitlements. In other words, if a user needs to access his or her virtual desktop, they need to go through the connection server. If a user is trying to access his or her published application, they need to go through the connection server.

The connection server simply acts as a broker between the end point device (users) and the resources that are available to that user (vDesktops and Apps hosted on the servers).


Blog Series Articles:

Virtual Machine Requirements:

2014-11-07_21-40-11

Operating System Requirements:

2014-11-07_21-40-12

Assuming you have downloaded the executable, let’s begin by launching the installation for View Connection server. Just like the previous install, all of the steps are pretty much the same, nothing really changed in the installation method. The only difference, is that now we’ll be installing the connection server on Windows Server 2012 R2. The installation file should be called something like VMware-viewconnectionserver-x86_64….

View_deployment_01

  • At the Welcome screen, click on Next >

View_deployment_02

  • Read through the End-User License Agreement (EULA) and click Next >

View_deployment_03

  • Keep the default installation path unless you want to install the connection server onto another drive and click Next >

View_deployment_04

  • Here are where things get interesting. Just like the previous version of View, this particular installer allows for installation of three different components, actually, these three components are very similar to one another. But all three have a purpose:
    • View Standard Server – First server to be deployed in the Pod
    • View Replica Server – The second server deployed in the Pod which provides High Availability and Load Balancing
    • View Security Server – Deployed mainly in the DMZ for providing remote access to the Virtual Desktop Infrastructure
  • Since it’s the first server in the View Pod, we’re going to chose View Standard Server. You can have only one standard server per vCenter instance

View_deployment_05

  • We must next provide the Data Recovery Password and click Next >

View_deployment_06

  • If the firewall is configured, it’s a good idea to let the installation configure the firewall with all the right settings to let traffic through…

View_deployment_07

  • Next, we’ll need to specify a user or a group who will have access to login to the View Administrator.. it’s better to always use AD groups so make sure you specify an AD group rather than a user. Although later on if you do specify a user, you can always add the group after the installation

View_deployment_08

  • You can chose if you want to participate in the User Experience Improvement Program

View_deployment_09

  • At this point, we’re ready to install! Just click on the Install button and that should get the connection server installed!

View_deployment_10

  • Once the installation is complete, go ahead and click on the finish button. At this point, you’ll see a new shortcut is created on your desktop called View Administrator

View_deployment_11

View_deployment_12

Stay tuned for the second part of the blog series coming soon!

Re-blogged from virtualizemydc.ca