Flings
Apps and tools built by our engineers that are intended to be played with and explored.

Horizon View Configuration Tool

Horizon View Configuration Tool

Summary

The Horizon View Configuration Tool automates Horizon View 5.3 installation and deployment. It removes the complexities and manual steps required for setting up a basic Horizon View deployment.

Features

The vCT ships as a virtual appliance with all the required VMware components to set up your Horizon View environment. After providing a Windows Server 2008 R2 SP1 ISO, an ESX host (not managed by vCenter), a few parameters, and licenses, the tool will provision your environment dynamically and automatically. The vCT deploys the following components:

  • Virtual machine with Active Directory Domain Controller configured (or you may integrate with the existing DC in your environment)
  • Virtual machine with Horizon View Connection Server installed
  • Virtual machine with Horizon View Composer installed
  • vCenter Server Appliance virtual machine deployed and configured

For more information, see VMware Horizon View Configuration Tool Quick Start Guide.

vctblog-figure2

System Requirements

To run the View Configuration Tool, there are some basic networking requirements:

    • If you wish to deploy an Active Directory Server then you will require:
      • 1 IP range that is on a subnet not managed by DHCP
    • If you are deploying and will integrate with an existing Active Directory Server then you will require:
      • 1 IP range that is on a subnet managed by DHCP

Be sure to gather your network values so you have this information ready when running the tool. Network parameters required are: starting IP address, an ending IP address, a subnet mask, and gateway address.

ESX 5.1 U1 or newer, ESX 5.5+ recommended.  The host must not be managed by
vCenter.

Storage Requirements

At least one defined datastore (VMFS volume) with at least 250GB free for the management infrastructure virtual machines, plus any additional desired storage for desktop deployment.

Instructions

Download the required files:

  • VMware-viewconfigurationtool-v1.0-view5.3.0_ OVF10.ova– 5.1 GB
  • VMware_Studio-2.6.0.0-631426_OVF10.ova or VMware_Studio_2.6.0.1 .ova –
    1.5GB

You can download VMware® Studio from the VMware website:

For the rest of instructions, please see: VMware Horizon View Configuration Tool Quick Start Guide

Video

Change Log

Engineers

Marilyn Basanta

End User Computing - Solutions Management
Add Feedback

35 thoughts on “Horizon View Configuration Tool

  1. Mandar Surkund

    Is this tool being actively supported ?
    I have sent a couple of emails to vctsupport@vmware.com but recieved no responses
    the error is “unable to find the active directory OVA

    3/02/2015 01:52:34 [info] Transporting VM from Studio to provisioning host; this may take a few minutes…
    13/02/2015 01:53:19 [info] Checking if the 172.16.92.60 connection is still active…
    13/02/2015 01:53:23 [info] Powering on transient VM on at .
    13/02/2015 01:53:25 [info] Waiting for the transient VM to boot up.
    13/02/2015 01:53:25 [info] Transient VM is now active.
    13/02/2015 01:53:25 [info] Waiting for the OS and applications installation process to complete…
    13/02/2015 02:00:08 [warn] STUDIO ABORT: Package execution failed – smb://172.0.0.20/winrepo/addns/default.vsp
    Please consult the file /opt/vmware/www/build/POCAD-M/status/postinstall.log for more information

    13/02/2015 02:00:08 [warn] The following are the last 20 lines of the application install log:
    13/02/2015 02:00:08 [warn] Active Directory Domain Services binaries are being installed. Please wait…^M

    13/02/2015 02:00:08 [warn] Unable to erase password option SafeModeAdminPassword from the answer file P:\addns.txt. The file may still contain passwords. You should ensure that the file is deleted when the installation operation has completed. The error was:^M

    Reply
  2. spardue

    I can say I have not heard back from the developer in at least 2-3 months after multiple prior e-mail correspondences.

    Reply
  3. Jonathan Jabez

    Hi,

    I am trying to setup Horizon View lab my own purpose. Will this tool help me accomplish my task?

    Thanks,
    Jonathan.

    Reply
  4. Justin Field

    I thought I would add this in case it helps anyone else. On my second go round of doing a proof of concept for a customer and using this tool I ran into a new error that I didn’t have on my first attempt. The difference with this time was that I used the customers existing Active Directory instead of creating a new one with this tool. I also was given an admin account that had a username that wasn’t administrator. What I came across was that the View VM was built and shortly after would be deleted along with the vcenter VM. After digging through the verbose.log on the studio vm /opt/vmware/www/build/POCVIEW-M/status i soon realized that although the password was correct for what I typed into the webpage (answer file) it defaulted to the username of administrator for the commands of netdom to join the view (and soon to be) composer VM’s to active directory, which of course failed.

    The work around…. a few minutes after clicking finish on the webpage with the answer file info, go to /opt/vmware/vct/studiofiles/view_joindomain and edit the default.vsp file to change to the correct username. Do the same to /opt/vmware/vct/studiofiles/vcomp_joindomain.

    Hope this helps others avoid some frustration and wasted time.

    Reply
  5. Robert Simons

    I had the same issue with View_OVF10.ova not being found. After looking at some log files, determined it was from credentials that were being used to add the VM’s to AD.

    There is an error in the configuration tool with the Active Directory Username for adding a computer to the domain. I entered a different user name in this field (defaults to Administrator) and the tool still used “Administrator” as the user for adding the computer. Once I corrected this, the deployment was successful….well, somewhat.

    At the end I received a “Deployment Successful” message, but the View & Composer VM’s were not present in my host. I had to download the .OVA files that were created and then deploy these to the host. I also picked a different owner name for these VM’s, which I assumed it would use as the local administrator, but it used “Administrator” for these as well.

    Other than these few bugs, this tool worked great!

    Reply
  6. Marilyn Basanta

    Hi All,

    Could you all email me directly at vctsupport@vmware.com ?

    This means something went wrong during the Studio build, it could be a few different things. It will be easier to diagnose if you each email me individually.

    For the quick analysis, if you SFTP to the Studio VM and check out this file:

    /opt/vmware/www/build/POCVIEW-M/status/verbose.log

    You can usually see the error. It might be that it couldn’t join to the domain — that’s the main error for View VM build errors.

    Please feel free to reach out to me on the support alias. I am happy to help everyone individually.

    Thanks!

    – Marilyn

    Reply
  7. John

    Hello, it seems like a nice tool but I get an error about a missing View_OVF10.ova on VM studio. Any suggestions?
    INFO: Building View VM
    Apr 04, 2014 10:10:54 AM VCT_main buildView
    INFO: Pre-build file check: /opt/vmware/depot/winrepo/buildfiles/viewbuild.xml found
    Apr 04, 2014 10:27:53 AM VCT_main buildView
    INFO: I got this from console: [‘Using build instance name: POCVIEW-M\n’, ‘Cleaning up …Build/Validation process has successfully aborted.\n’]
    Apr 04, 2014 10:28:14 AM VCT_main fileExists
    INFO: I could not find /opt/vmware/www/build/POCVIEW-M/exports/ova/View_OVF10.ova on the desired system:172.16.4.27 (VM studio)
    Apr 04, 2014 10:28:14 AM VCT_main buildView
    INFO: I was not able to build the View machine. The OVA was not found.
    Apr 04, 2014 10:28:14 AM VCT_main main_run
    INFO: Failed to complete building View OVA. Please check the log and try again. VCT Status: Failed
    Apr 04, 2014 10:28:14 AM VCT_main cleanup_after_Failure
    INFO: ALERT: Cleaning up after VCT Failure. Deployed VMs to be removed from ESX host
    Apr 04, 2014 10:28:14 AM VCT_main connectToHost
    INFO: time taken:156
    Apr 04, 2014 10:28:14 AM VCT_main connectToHost
    INFO: root:ha-folder-root
    Apr 04, 2014 10:28:14 AM VCT_main findVMIndex
    INFO: null
    Apr 04, 2014 10:28:14 AM VCT_main delete_VM
    INFO: I could not remove VM: null

    Reply
    1. missing View_OVF10.ova

      Apr 08, 2014 6:48:46 AM VCT_main runSSHCommand
      INFO: I got to the SSH Command
      Apr 08, 2014 6:48:47 AM VCT_main runSSHCommand
      INFO: Exit value from SSH: 0
      Apr 08, 2014 6:48:47 AM VCT_main runSSHCommand
      INFO: Completed SSH Command: mkdir /opt/vmware/depot/winrepo/dotnet35 and got this output: []
      Apr 08, 2014 6:48:47 AM VCT_main createNewDirectory
      INFO: Create /opt/vmware/depot/winrepo/dotnet35 directory on Studio was successful
      Apr 08, 2014 6:48:47 AM VCT_main uploadFile
      INFO: Upload file: /opt/vmware/depot/winrepo/dotnet35/default.vsp was successful.
      Apr 08, 2014 6:48:47 AM VCT_main prepStudioBuildFiles
      INFO: /opt/vmware/depot/winrepo/dotnet35 was created and had all necessary files uploaded.
      Apr 08, 2014 6:48:47 AM VCT_main main_run
      INFO: Studio Prep: Completed uploadBuildFiles
      Apr 08, 2014 6:48:47 AM VCT_main main_run
      INFO: Building View VM
      Apr 08, 2014 6:48:48 AM VCT_main buildView
      INFO: Pre-build file check: /opt/vmware/depot/winrepo/buildfiles/viewbuild.xml found
      Apr 08, 2014 7:09:09 AM VCT_main buildView
      INFO: I got this from console: [‘Using build instance name: POCVIEW-M\n’, ‘Cleaning up …Build/Validation process has successfully aborted.\n’]
      Apr 08, 2014 7:09:10 AM VCT_main fileExists
      INFO: I could not find /opt/vmware/www/build/POCVIEW-M/exports/ova/View_OVF10.ova on the desired system:192.168.70.90
      Apr 08, 2014 7:09:10 AM VCT_main buildView
      INFO: I was not able to build the View machine. The OVA was not found.
      Apr 08, 2014 7:09:10 AM VCT_main main_run
      INFO: Failed to complete building View OVA. Please check the log and try again. VCT Status: Failed
      Apr 08, 2014 7:09:10 AM VCT_main cleanup_after_Failure
      INFO: ALERT: Cleaning up after VCT Failure. Deployed VMs to be removed from ESX host
      Apr 08, 2014 7:09:11 AM VCT_main connectToHost
      INFO: time taken:207
      Apr 08, 2014 7:09:11 AM VCT_main connectToHost
      INFO: root:ha-folder-root
      Apr 08, 2014 7:09:12 AM VCT_main findVMIndex
      INFO: null
      Apr 08, 2014 7:09:12 AM VCT_main delete_VM
      INFO: I could not remove VM: null
      Apr 08, 2014 7:09:12 AM VCT_main findVMIndex
      INFO: I could not find: View VM as part of the index.
      Apr 08, 2014 7:09:12 AM VCT_main delete_VM
      INFO: I could not remove VM: View
      Apr 08, 2014 7:09:12 AM VCT_main findVMIndex
      INFO: I could not find: Composer VM as part of the index.
      Apr 08, 2014 7:09:12 AM VCT_main delete_VM
      INFO: I could not remove VM: Composer
      Apr 08, 2014 7:09:12 AM VCT_main findVMIndex
      INFO: I found vm: VCENTER
      Apr 08, 2014 7:09:12 AM VCT_main delete_VM
      INFO: I was able to remove VM: VCENTER
      Apr 08, 2014 7:09:12 AM VCT_main cleanup_after_Failure
      INFO: I was able to disconnect.
      Apr 08, 2014 7:09:12 AM VCT_main cleanup_after_Failure
      INFO: Successfully able to remove stray VMs after a VCT failure.

      Reply
      1. Marilyn Basanta

        Hi All,

        Could you all email me directly at vctsupport@vmware.com ?

        This means something went wrong during the Studio build, it could be a few different things. It will be easier to diagnose if you each email me individually.

        For the quick analysis, if you SFTP to the Studio VM and check out this file:

        /opt/vmware/www/build/POCVIEW-M/status/verbose.log

        You can usually see the error. It might be that it couldn’t join to the domain — that’s the main error for View VM build errors.

        Please feel free to reach out to me on the support alias. I am happy to help everyone individually.

        Thanks!

        – Marilyn

        Reply
  8. Jan

    Hi Marilyn,

    just wanted to ask concerning the databases. What kind of databases will be created?
    Normally I need following databases for the whole environment:
    – RSA for vCenter
    – Composer
    – View Event database
    – Update Manager
    – …

    I read that for view-composer a sql express database will be created.
    Is it planned to integrate a complete SQL Server with scripted database-integration?

    Also insn’t the express database limited to 50 desktops?

    I’ll run a test installation on friday – really exited about the result!!

    Thanks

    Reply
    1. Marilyn Basanta

      SQL Express has a 4GB limit, and this instance is only for your View Composer deployment. I believe the 50 VM limit had to do when you deployed vCenter for Windows and used the integrated DB. We’re using the vCenter Server Appliance and its internal database can support 100hosts/3000 VMs.

      And yes we do plan to expand support to integrate with your existing full SQL DB deployment.

      Thanks,

      Marilyn

      Reply
  9. David Goh

    Very Incredible Tool!

    But Every time I use this tool, I got error message as below.

    INFO: Building AD VM on Studio. This step may take up to an hour. VCT Status: OK
    Mar 17, 2014 12:49:19 PM VCT_main buildAD
    INFO: Pre-build file check: /opt/vmware/depot/winrepo/buildfiles/adbuild.xml fou nd
    Mar 17, 2014 1:03:41 PM VCT_main buildAD
    INFO: I got this from console: [‘Using build instance name: POCAD-M\n’, ‘Cleanin g up …Build/Validation process has successfully aborted.\n’]
    Mar 17, 2014 1:03:42 PM VCT_main fileExists
    INFO: I could not find /opt/vmware/www/build/POCAD-M/exports/ova/AD_OVF10.ova on the desired system:192.168.88.114
    Mar 17, 2014 1:03:42 PM VCT_main buildAD
    INFO: Failed to build the AD machine. The OVA was not found.
    Mar 17, 2014 1:03:42 PM VCT_main run
    INFO: Failed to complete the build of the Active Directory OVA. Please check the log and try again. VCT Status: FAILED
    Mar 17, 2014 1:03:42 PM VCT_main cleanup_after_Failure
    INFO: ALERT: Cleaning up after VCT Failure. Deployed VMs to be removed from ESX host

    What is the problem?
    Is the AD_OVF10.ova default loaded image? or compiled when using this tool?

    Reply
      1. Jan

        I run into exact the same error David Goh has decribed.

        2014 10:54:24 AM VCT_main buildAD
        INFO: Failed to build the AD machine. The OVA was not found.
        Mar 21, 2014 10:54:24 AM VCT_main run
        INFO: Failed to complete the build of the Active Directory OVA. Please check the log and try again. VCT Status: FAILED
        Mar 21, 2014 10:54:24 AM VCT_main cleanup_after_Failure
        INFO: ALERT: Cleaning up after VCT Failure. Deployed VMs to be removed from ESX host
        Mar 21, 2014 10:54:24 AM VCT_main connectToHost
        INFO: time taken:84
        Mar 21, 2014 10:54:24 AM VCT_main connectToHost
        INFO: root:ha-folder-root
        Mar 21, 2014 10:54:25 AM VCT_main findVMIndex
        INFO: I could not find: SV-T-DC1 VM as part of the index.
        Mar 21

        Any suggestions till now?

        Reply
        1. Marilyn Basanta

          Hi Jan,

          Please send me an email at vctsupport@vmware.com.

          For the AD build error if you can email me this file I can help you diagnose what went wrong in the AD build.

          /opt/vmware/www/build/POCAD-M/status/verbose.log

          Thanks,

          Marilyn

          Reply
  10. Charles

    Nice tool, but kept on failed with error “”Failed to connect to ESXi Host: Please check the credentials and IP address. I could not connect to: 10.1.1.191 with this userid: root VCT Status: FAILED”

    ; where 10.1.1.191 is my standalone ESXi host (5.5.x)… I checked both DNS, AD and seems fine to me… any idea why?

    Reply
  11. Javier

    Hi Marilyn,
    Do you know where, I can get the file: VMware-viewconfigurationtool-v1.0-view5.3.0_ OVF10.ova
    btw, the solution, looks very nice!
    And extra question.. do you know if is possible to implement View with VCAC, I would like to setup a VDI with self service and charge back..

    Reply
  12. Forbes Guthrie (@forbesguthrie)

    Hi,
    How much RAM is required at a minimum to spin up the server components (not including desktops)? Might be to include in the System Requirements and Documentation.
    Thanks,
    Forbes

    Reply
    1. Marilyn Basanta

      Hi Forbes,

      VCT and Studio each take 512MB (but you can delete/turn off these VMs when you are done with deployment).

      For the rest of the components, if you decide to deploy an AD server, it will deploy using 2GB of RAM, which you can then adjust post deployment to whatever amount you see fit.

      VCVA deploys with 8GB RAM by default, adjustable to 4GB post deployment.

      View Connection Server and View Composer Server each deploy with 4GB RAM (which is the minimum supported amount for each and recommended to 10GB for over 50+ View Desktops).

      That means you can get away with 12GB (14GB with AD). I’ll add a chart to the documentation. Thanks!

      Reply
    1. Marilyn Basanta

      Hi Hans,

      I haven’t tested it but I just looked over the config file and it should be good. Let me know if you run into any issues and I can add it to the testing matrix for our next rev.

      – Marilyn

      Reply

Leave a Reply

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