Horizon Cloud - DaaS Agent 16.11.2 Release Notes

|

VMware Horizon Cloud Service | 13 APR 2017

As of February 7, 2017, the new brand name for VMware Horizon Air is VMware Horizon Cloud Service. In the current releases, customers will continue to find legacy references to previous names in the product documentation.

Release notes last updated on 14 NOV 2017

Check for additions and updates to these release notes.

Links to release notes for other versions (* indicates DaaS Agent): 15.3.2 | 15.3.3 | 16.6 | 16.6.1 | 16.6.2* | 16.11 | 16.11.1 | 17.1 | 17.1.1 | 17.2

What's in the Release Notes

The release notes cover the following topics:

Overview

This document describes the process for installing DaaS Agent 16.11.2 in a Horizon Cloud with Hosted Infrastructure environment. It is required that all tenants be running Horizon Cloud 16.11.x before you begin the process described below.

  • DaaS Agent 16.11.2 replaces earlier versions of the DaaS Agent for Horizon Cloud 16.11.x. It is recommended that you update to this version.

  • This version resolves an issue where the allocate state for a tenant appliance would be set as “untrusted” due to a communication problem between the DaaS Agent and Active Directory.

The install process varies depending on whether you are performing a new installation or an upgrade:

  • If you are performing a fresh install of Horizon Cloud 16.11, use the instructions below under New Install to perform the DaaS Agent installation.

  • If you are upgrading to Horizon Cloud 16.11, follow the instructions below under Upgrade.

For more information on installing and configuring DaaS Agents, see the topics under Install the DaaS Agent in the Horizon Cloud With Hosted Infrastructure 16.11 Administration guide.

New Install

To install the DaaS Agent on all VMs for all Tenants, you use a domain controller with a GPO policy.

See http://support.microsoft.com/kb/816102 for a detailed reference.

Upgrade

When the Tenant appliances have been upgraded, update the DaaS Agent using one of the methods described below.

Update Via GPO Policy

To update the DaaS Agent on all VMs for all upgraded Tenants, you typically use a domain controller with a GPO policy.

See http://support.microsoft.com/kb/816102 for a detailed reference.

Update Manually

  1. Download the VMware-DaaS-Agent-16.11.2-5204686.msi file.

    Note: This version of the DaaS Agent file is only compatible with Horizon Cloud 16.11.x.

  2. Install DaaS Agent by copying the file onto your VM and running the install.

  3. Confirm that tenant discovery has been configured. If it has not, this can be done 1 of 2 ways:

    • DaaS Agent Discovery (recommended): The tenant appliance addresses can be automatically discovered by the DaaS Agent via DHCP by utilizing option code 74. For more information, see instructions in the Configure Tenant Discovery for DaaS Agent section below.

    • Update of DaaS Agent configuration file: The tenant appliance addresses can be manually updated in the DaaS Agent configuration file. Open the file C:\Program Files (x86)\DaaS Agent\service\MonitorAgent.ini with a text editor like notepad (note: on 32-bit systems the path will be exclude the “(x86)”). Remove the semi-colon on the line containing the parameter standby_address and provide a comma separated list of the tenant appliance IP addresses. A restart of the DaaS Agent Windows service is required after making this change.

Configure Tenant Discovery for DaaS Agent

A DHCP helper/relay is required to deliver the DHCP requests over the VPN tunnel to the tenant network. A small Linux appliance can be configured in the tenant to perform this function.

  • Configure the DHCP scope for the desktop subnet, starting at x.x.x.30.

  • Configure DHCP option code 74 (IRC Chat) to point to the two IPs allocated for the tenant appliances. For example, if you are using a Windows server to provide DHCP service:

    1. Open the DHCP configuration client from Control Panel > Administrative Tools.

    2. Right-click Server Options and select Configure Options from the pop-up menu.

    3. If you have defined limited address scopes, you can confine the options configuration to a particular scope. Click on the scope and right-click on Scope Options to configure the 074 option code for that scope only. Configuration is the same as for the whole DHCP server.

    4. Scroll down to the 074 option for Internet Relay Chat (IRC) and check the box.

    5. Add IP addresses for tenant appliances.