check-circle-line exclamation-circle-line close-line

VMware Horizon DaaS Platform | 04 SEP 2014

Release notes last updated on 04 SEP 2014

Check for additions and updates to these release notes.

Links to release notes for other versions (* indicates DaaS Agent): 6.1.0 HF | 6.1.1 | 6.1.1* | 6.1.2 | 6.1.3 | 6.1.4 | 6.1.2* | 6.1.5 | 6.1.6 | 7.0.0 | 8.0.0

What's in the Release Notes

The release notes cover the following topics:

New Features

End Customer Features

Integration of the Horizon View 6.0 release including support for RDSH and Remote Apps with the Horizon View Client

Integration with Horizon View 6.0 has a number of benefits for Horizon DaaS users. The new client:

  • Delivers Hosted Apps and desktops (remote applications and desktops) through expanded integration with Microsoft Remote Desktop Services (RDS) on Windows Server operating systems.
  • Provides a robust way to access one or more remote applications seamlessly from any Horizon View Client 3.0 or later using PCoIP.
  • Provides the ability to remote shared session desktops from RDS hosts using PCoIP.

All mobile browsers, including Chrome and Safari, now able to launch a session using HTML Access

HTML Access supports the following Web browsers:

  • Chrome 33 and 34
  • Internet Explorer 10 and 11
  • Internet Explorer 9 (limited support)
  • Safari 7.0.3 and 6.1.3
  • Mobile Safari on iOS devices running iOS 6 or later
  • Firefox 28 and 29

Support for Windows 8.1 as a Guest OS

The Horizon DaaS Platform now supports Windows 8.1 as a guest operating system. Support includes:

  • Both 32-bit and 64-bit versions
  • Professional and Enterprise variants
  • VDI sessions

Service Provider Features

Support for vSphere 5.5 Update 1

The Horizon DaaS Platform now supports vSphere 5.5 Update 1, which was released earlier this year. For more information on new features available in this update, see the vCenter Server 5.5 Update 1 Release Notes.

Note: vSAN is not a supported storage solution for any Horizon DaaS environment at this time. In addition, the use of vSAN in multi-tenant environments is prohibited due to other considerations.

Template version now displays for appliances in Service Center

You can now see the Horizon DaaS management appliance template version on which a particular appliance is based. When you click the link the appliance list to view appliance details, there is a new From Template Version field.

Ability to post a maintenance notice in Enterprise Center

You can now set up a maintenance notice that displays at the top of the Dashboard page in Enterprise Center. There is a new tab on the Editing page for tenants where you can enter text for the notice and set time and date for the notice’s start and expiration.

When there is an active notice, a yellow box displays at the top of the Dashboard page in Enterprise Center with a link that displays the text of the notice.

Upgrade of appliance template to Ubuntu 12.04 LTS

The Horizon DaaS management appliance template is now based on Ubuntu 12.04 LTS. It is recommended that you migrate all appliances to the new Ubuntu 12 template. For more information, see the Horizon DaaS Platform 6.1 Upgrade document.

Memory dump file now created when an out of memory condition occurs on a Horizon DaaS management appliance

In the event that the core dtService runs out of memory, a memory dump will be saved to /data on the affected appliance. This will provide critical information to help analyze and troubleshoot any memory problems. The file can later be deleted, allowing a new file to be created if a future crash occurs.

Memory for Horizon DaaS Management Appliances Increased from 2 GB to 3GB

The standard memory for Horizon DaaS management appliances has been 2 GB. As the workload of the appliances has increased swap memory is being used more often and in some cases causing performance issues as memory gets paged to disk. In order to decrease the use of swap, all management appliances are now provisioned with 3 GB of memory.

Rest API Changes

The following changes have been made to the REST APIs. For more information, see the latest Javadoc or the Horizon DaaS Platform 6.1 REST API document.

Use of https Port

REST API invocations over the http protocol are now redirected to the https port on the appliance. Clients using the Java bindings against a Brighton appliance must import the appliance’s SSL certificate to the Java trust store or implement a custom trust store manager. The default protocol to invoke the REST APIs using the Java Bindings is now https.

New Interface

  • DtNetwork

New Enumeration

  • DtNetworkType

Method Changes

  • DtComputePool
    • New property: tenantDesktopManagerId
    • New links: Update, UpdateOverallocationRatios
  • DtHypervisorManager
    • New link: AssignToTenantDesktopManager
  • DtInfrastructureManager
    • New links: TenantNetworks, ApplianceTemplate, DiscoverHypervisorManagerByAddress

Fixed Defects

The following defects have been fixed in this version:

  • Users had been unable to select HTML Access as default protocol from the Mappings page. This selection can now be made successfully. (DT-5080)
  • Session warning had been occurring when Service Providers downloaded Appliance logs. This has been corrected so the warning no longer displays. (DT-4939)
  • When viewing the Mappings page using Microsoft Internet Explorer 10, users would see the Desktop dropdown in the wrong area, and any selection made would not commit to the database. This page now works correctly in Internet Explorer 10. (DT-4756)
  • Horizon View client configured with all connections through dtRAM was not showing allocator service failure in reporting_event table when failure occurred. This has been corrected so that the failure displays correctly. (DT-3669)
  • If you deselected the Allow Full Desktop radio button for your first pool and then deleted all of the applications for it, the button would no longer appear on the screen for that pool or any pool you created based on it. The system now automatically switches the setting on when there are no applications on the pool. (DT-5651)
  • The "Rename VM" button has been removed Dynamic Desktops. (DT-4193)

Product Support Notices

  • DaaS Agent: You must upgrade the DaaS Agent to at least to version 6.0.0 prior to upgrading a tenant to Horizon DaaS 6.1.0. The 6.1.0 DaaS Agent released with Horizon DaaS 6.1.0 is required to take advantages of new features such as RDSH and Remote Apps with the Horizon View Client. The upgrade to DaaS Agent 6.1.0 includes downloading SSH certificates as described in the “Update DaaS Agent” section of the Horizon DaaS Platform 6.1 Upgrade document.
  • View Agent & View Agent Direct Connect (VADC): It is recommended that you upgrade to View Agent 6.0.1 build 2089044 and VADC version 6.0.1 build 2088845. These versions are required to take advantage of RDSH and Remote Apps with the View Client. A new version of the dtRAM (3.0.3) is also required.
  • Linux Guest OS Support: Support for Linux as a virtual desktop guest OS is experimental since the NX v4.x components have not been qualified and v3.x has fallen out of support and are no longer publicly available or supported. There is a new Linux DaaS Agent with release 6.1.
  • ESXi: The ability to discover ESXi servers was deprecated in Horizon DaaS Platform v6.0 and has been officially removed in 6.1. It is no longer possible to manage ESXi servers directly. Migration away from direct ESXi must be completed before the 6.1 upgrade. The use of vCenter is now required. Please contact VMware support to plan for the migration to vCenter.
  • Microsoft Internet Explorer: Internet Explorer 11 is now supported; Internet Explorer 8 is no longer supported.
  • Horizon DaaS Management Appliance Memory: Memory for Horizon DaaS management appliances has been increased from 2 GB to 3 GB. For more information, see the item under New Features.
  • Billing Scripts: The retrieval of billing information via scripts that were provided in previous releases is no longer supported. All billing information retrieval must be done via REST APIs.
  • New Port: All appliances now use port 8443 to communicate with each other, and the DaaS Agent also uses port 8443 to communicate with the appliances. You must confirm that port 8443 is open, and may also need to open an additional firewall port to allow traffic using port 8443.

Known Issues and Workarounds

The following are known issues in this release.

  • PCoIP and HTML Access Users with expired passwords may be unable to change their passwords via the End Point client (View Client, Thin Client etc.). The recommended work around is to log into the desktop via RDP using the User Portal. The User is then prompted to change their password. (DT-4308)
  • When a list of virtual machines is over one page long, the second page does not display properly. If you have 250 results or fewer, you can work around this by selecting one of the options to display more virtual machines per page (Show 100, Show 250); otherwise, you can narrow your search enough that the results can be displayed on one page. (DT-5362)
  • Thin clients supporting PCoIP may not support Horizon View 6.0 functionality without software updates. Please refer to the thin clients’ manufacturer for complete list of supported Horizon View 6.0 functionality. (DT-5618)
  • It is no longer possible to connect to a session pool using RDP from a mobile device. If connections to session pools are required from mobile devices, you must create a new session pool with the PCoIP protocol enabled, and install the Horizon View Client 3.1 on the mobile devices. For more information, see the “Protocols” section of the Horizon DaaS 6.1 Technical Notes document. (DT-5906)
  • In Multi-DC configurations, adding additional Desktop Manager appliances to tenants that are extended across data centers is not supported. (DT-5927)
  • There is an issue around configuring RSA where the sdconf.rec file does not properly replicate between Tenant Appliances. Customers wishing to use RSA should log into each Tenant Appliance directly and upload the sdconf.rec to each one. (DT-5931)
  • The DaaS Agent reports the incorrect IP to the tenant when Juniper VPN client is installed. This blocks the user from being logging into a desktop until the Juniper VPN client is uninstalled. (DT-5932)
  • If a full inventory runs on a tenant while one of the service provider appliances is down, all desktops will be marked as deleted until the down appliance is up and running again and the next full inventory reconciliation runs (every 12 hours by default). To work around this issue, you can trigger a full inventory manually:
    1. Note the current setting for the element.monitor.element.fullInventory.interval policy (default value is 43200000 milliseconds).
    2. Change the setting to a number less than 100 and save changes.
    3. Change the setting back to the previous value.

    This will cause the full inventory to run and the desktops will reappear. (DT-5938)

  • When a user connects to a dynamic pool, the user’s session may not be reflected in the Enterprise Center for up to 5 minutes. (DT-5947)
  • Creating an entitlement for one tenant may cause quota functions not to work correctly for all tenants. For this reason, it is recommended that you not create any entitlements until this issue is resolved.

Monitoring Issues

  • Desktone_NTPService provider returns sync state FALSE even though the NTP daemon is in sync with the time source. The workaround is monitor “Jitter” value property instead of “SyncState” and “OperationalStatus” properties. (DT-5951)
  • Monitoring issue: CIM_FileSystem provider does not return any data in response from appliances in DaaS platform. Contact VMware Global Support Services for more information. (DT-5953)