Home > Horizon Suite, vCenter Server, VMware > HOWTO: VMware Horizon Suite 6 – vCenter Server Configuration

HOWTO: VMware Horizon Suite 6 – vCenter Server Configuration

In the previous post, https://vnetwise.wordpress.com/2014/09/07/howto-vmware-horizon-view-6-vcenter-server-installation/, we covered how to get your basic vCenter v5.5U1 installed – which will largely be the same be it for vCenter for general infrastructure, for View or for Horizon. In this article, we’ll be doing some basic configuration of vCenter to get some hosts and a cluster built so we have a place to deploy Horizon Suite.

To begin, we’re going to want to launch the vSphere Web Client. If you’re doing so from the server vs a workstation, you may run into your first minor hiccup:


You’ll need to install Adobe Flash Player. So you’ll need to make a decision as to if you want to install this on your server, or continue the work from a workstation that has allowances for this. Perhaps your server policy doesn’t allow additional software installed. Maybe Flash specifically is banned. Maybe it is not, but browsing the public internet from a server is denied by force or request. In either manner, we’ll assume you’re performing the remaining of these steps from a system with Adobe Flash installed.

1) Launch your browser and point at https://<vcenter>:9443/vsphere-client:


Note that you may need/want to add the self-signed SSL as trusted, and also that pop-ups and/or plug-ins may be blocked as you go. So if a feature doesn’t work, check this.

Login as administrator@vsphere.local



We want to confirm that our AD domain is present. If not, we need to add it. vSphere 5.5 U1 is much better at ensuring this is added by default.



When you click on ADMINSTRATORS, you will note that the only member is the administrator@vsphere.local account. Click the ADD MEMBER icon.

4) From the DOMAIN drop down, choose your AD domain. Change it to SHOW GROUPS first, and search for your AD group.


In my case, I have created a “vSphere Admins – VDI” group so we don’t use the Domain Admins or similar. Select the item and click ADD so it shows up in the GROUPS field. Then click OK.


You can verify that your group now shows up.

5) Next, we’ll need to click HOME:




vCenter Servers:


Select your vCenter Server:




Note the only group currently is the VSPHERE.LOCAL\ADMINSTRATOR user. This is what we’re going to be adding to, so our new group has rights.

6) Similar to Step 4 above, click ADD, change the domain to your AD domain and search for your group. Click ADD.


This returns you to the ADD PERMISSION screen with the group selected. Next you need to change the ASSIGNED ROLE to ADMINISTRATOR. Then click OK.


Now your AD group shows up as an Administrator at the vCenter Server object – and it’s children.

7) Choose to log out from the drop down:


We want to log back in as an AD user of the AD group we’ve added, so we can confirm things are working as expected.


Remember that it is in UPN format, so it will be <username>@<domainname>

8) Click on VCENTER -> VCENTER SERVERS -> <your vCenter>. Click ACTIONS, and choose NEW DATACENTER.



Enter the name of your datacenter and click OK.

9) The client will automatically take you to the new DATACENTER object. Click on ACTIONS -> NEW CLUSTER:



Enter the name and details for your cluster. Enable HA and DRS. Click OK.


Click on CLUSTERS to change to that context. Then double click on the cluster name in the lower right corner.

NOTE: There are some configurations within the Horizon Suite that require DRS to be enabled – even if you have a cluster of one host. So ensure you do set it, even if you set the operation to MANUAL.

10) Click ACTIONS -> ADD HOST:


Add the host name and click NEXT.


Enter the username and password for the host:


Accept the SSL thumbprint and click YES.


In my case, the host is already being managed by another vCenter. So I’ll click NEXT to bring it into this vCenter.


The existing host already has a licence. If not, you can either enter a key or choose to use Evaluation Mode. Click NEXT.


We will choose to NOT enable lockdown mode. Click NEXT.


We’re going to use the default Resource Pool. Click NEXT.


Click FINISH to complete the host addition.

Repeat for any additional hosts. I’ll be adding NW-ESXI02.netwise.ca as well.

At this point, the basics of the vCenter for View are now configured. We now have:

· A Cluster inside a Datacenter object

· 2 hosts, so we can do some vMotion/DRS and test failover – what good is a PoC that doesn’t test failure situations to ensure that it behaves as you expect

· Hosts have storage and networking configured and are otherwise ready to go.

We haven’t touched on other settings such as alerts, or NTP/SysLog/etc, but they’re really more in-scope for a general vCenter walkthrough, and we’ll assume either this is just a demo environment or you’d be performing those tasks anyways, and you’re just here to find out how to get Horizon Suite up and running. Also, we haven’t touched on things I’d be typically using like NetApp VSC, VAAI for NFS, or VMware Update Manager (VUM). We’ll talk about this later, once we get the general environment going.

Our next step will be to actually deploy some of the Horizon components.

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: