An other post in the VMware Lab Flings series. This time a fling that will make life a bit simpler in deploying Horizon View 5.3, the Horizon View Configuration Tool. Check it out here http://labs.vmware.com/flings/horizon-view-configuration-tool.
What is this tool about? It is a virtual appliance with the required components to automate a VMware Horizon View 5.3 deployment. This means no longer going around with installers at servers and watching those installers go by. With just inserting a licensed Windows server image, some unmanaged ESXi hosts (they will be managed afterwards), configuration parameters (yes you will have to input something yourself) and Horizon licenses and you are set up with the following components:
- Optional, VM with Active Directory Domain Controller configured. Optional as you can choose to integrate with an existing domain.
- Windows 2008R2 VM with Horizon View Connection Server installed.
- Windows 2008R2 VM with Horizon View Composer installed.
- vCenter Server Appliance (vCSA) deployed and configured.
The automation tool in it’s current initial state is very useful for doing basic Horizon View infrastructures for small deployments or Proof of concepts. Be aware that there is no official support from VMware for flings, it is a little on the own risk (with help from the community and fling engineers of course).
The Composer is set-up with a SQL Express database, maybe here should be an option to include an external database server.
What is needed?
For the servers that will be deployed a Windows 2008R2 ISO is needed together with a license to operate them.
The configuration parameters for networking (one DHCP scope IP plan, either managed or unmanaged depending on greenfield DC or integration), some storage (VMFS datastore with at least 250GB for the infrastructure VM’s plus data store for your VD’s) and VD ESXi hosts (not yet managed).
For the hosts make sure that Secure Shell (SSH) and the ESXi Shell are both set to running.
You will ofcourse need the Horizon View Configuration Tool downloaded and next to it you need VMware Studio to download here https://my.vmware.com/web/vmware/details?downloadGroup=STUDIO2600GA&productId=193.
Deploy both the VMware Studio and the Horizon View Configuration tool to one of your ESXi hosts. Deployment is straightforward, accepting the EULA (with the deployment and after start up) and configuring the correct networks and storage locations.
Both hosts should be powered on and configured for there IP addresses. Standardly they will try to get a DHCP lease, but if your doing an greenfield with a DC and unmanaged DHCP this could be a chicken egg story. For this a static IP is recommended. But if you have a managed DHCP elsewhere a reserved DHCP with DNS records is no problemo. The Horizon View Configuration Tool must be able to reach the VMware Studio (it will check in configuration, bobo’s will be determined there)
For the purpose of test driving I am installing both appliances in VMware Workstation. I have a Windows DC there with DHCP set up. I got two ESXi 5.5 hosts not managed. I have an OpenFiler NFS data store setup to store the infrastructure VM’s on to.
My VCT is running with a DHCP lease and DNS record. I can access the webservice at http://<fqdn vct or IP>/vct.
But first upload the 2008R2 ISO with WinSCP or something similar to the VCT appliance. Just put the ISO (with friendly name) in the root (that is /) of the appliance. The default user is root and password is vmware. When the ISO is on there, you can open up and fill in the values for the existing/integration or new DC deployment.
Fill in the values on the tab’s. First start with the ESX connection, AD DS, vCenter, Connection server and finish with the composer.
When you want servers in trail mode, don’t fill in a product key for the Windows server components.
With the automation kicking in the only places to look for what is happening are the connections to the hosts (but without a vCenter deployed this is limited with a vSphere client) and the log files on the VCT appliances. Just log in with SSH (or check with WinSCP if you still have that open from uploading the ISO) and look for files named VCT_timestamp.log in root.
– Happy automating your VMware Horizon View deployment!