VMware Horizon FLEX 1.6 Release Notes
VMware Horizon FLEX 1.6 | 8 SEP 2015
Last updated: 1 OCT 2015
Check for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
About VMware Horizon FLEX
VMware Horizon FLEX enables companies to provision and manage local, corporate virtual desktops to workers that were previously difficult or costly to support.
For more information, see the broader VMware Horizon FLEX documentation, or specifically the VMware Horizon FLEX 1.6 Documentation Center
- Flexible Deployment Options - Standardized virtual desktops for PC and Mac end users can be provisioned for customers, contractors, or remote employees through the corporate network or on a USB drive.
- Centralized Control - Centralized policy-based management provides a central point of entitlement and control. Device control can allow or deny use of peripheral devices, expiration control enables IT to set a timeframe for virtual desktops to expire, and remote kill can disable virtual desktops remotely in case of theft, termination, or lack of corporate compliance.
- Local Execution - End users receive access to a rich desktop experience through VMware industry-leading clients. Productivity is ensured, even when users are on the road or are disconnected from the network.
- Unified Image Management - Virtual desktops can be managed as a set of logical layers owned by IT or the end user. Dynamic layers for desktop and application management, provided by VMware Mirage technology, enable IT-managed layers to be updated while maintaining end-user files and personalization.
- IT Cost Reductions - Enable Bring Your Own PC (BYOPC) and support Macs in the enterprise without having to manage the entire Mac. This feature can reduce training needs by enabling employees to use their system of choice, expedite new employee onboarding, and eliminate the cost of deploying and managing a physical laptop.
Learn more about Horizon FLEX at: http://www.vmware.com/products/horizon-flex.
- Microsoft Windows 10 support
The following Microsoft Windows 10 support is featured in this release:
- Microsoft Windows 10 as a host
- Microsoft Windows 10 as a guest operating system
- Microsoft DirectX 10 support for guests
- Added USB 3.0 support to Windows 7 virtual machines (with the latest Intel USB driver)
- Support adding an incremental number to the Active Directory machine name
This feature allows users to download multiple copies of a virtual machine, where all copies are joined to Active Directory.
- Support virtual machine URL per entitlement
This feature allows different Active Directory groups to have different download sites.
- Although the Horizon FLEX clients, Fusion Pro and Workstation Player, have had a major upgrade, the Horizon FLEX licenses from the previous version continue to work if the user enters them.
- Although the Horizon FLEX clients support the Windows 10, Windows Server 2012, and Ubuntu 14.04 guest operating systems, you cannot use VMware Mirage to manage Windows 10, Windows Server 2012, or Ubuntu virtual machines.
Features and Known Issues from prior releases of VMware Horizon FLEX are described in the release notes for each release. To view release notes for prior releases of VMware Horizon FLEX, click the following links:
Users lose access to a Horizon FLEX virtual machine that is Active Directory password enabled when they change the password locally
The Active Directory password setting is managed by the policy associated with the Horizon FLEX virtual machine. When the Active Directory password setting is enabled, changing the password locally makes the virtual machine inaccessible. After a user changes the password locally and relaunches the Horizon FLEX Client, the user's password is rejected when attempting to access the virtual machine. The Horizon FLEX server rejects both the new and old passwords.
This issue is resolved. Accidentally breaking the association with the Active Directory password no longer occurs.
On VMware Player, after the Active Directory status of a user becomes unavailable, the user might not be able to access virtual machines
When the power on passphrase of the Horizon FLEX virtual machine is set to match the user's Active Directory passphrase on the FLEX server and the Active Directory account of the user is disabled, expired, or locked out, the next time the user powers on the virtual machine, a message might appear about the invalid account. The user clicks OK and the virtual machine is suspended and VMware Player closes. The next time the user powers on the virtual machine, the following message appears and the virtual machine is otherwise unresponsive:
This virtual machine appears to be in use.
If this virtual machine is not in use, press the "Take Ownership" button to obtain ownership of it. Otherwise press the "Cancel" button to avoid damaging it.
This issue is resolved.
In VMware Player, declining the disclaimer when downloading a virtual machine causes a problem during the next download attempt
When downloading a virtual machine, if you abort the process by declining the disclaimer, during the next download attempt, when you accept the disclaimer, VMware Player puts the virtual machine in the following folder, %appdata%\..\Local\Microsoft\Windows. During the first download attempt, you are prompted for the download location. During the second download attempt you are not. VMware Player selects the download location for you.
This issue is resolved.
The wipe operation might fail on an archived or locked out virtual machine that is Active Directory password enabled
When you attempt to perform the wipe operation on an archived or locked out Horizon FLEX virtual machine with the Active Directory password setting enabled, the virtual machine instance state might change from pending wipe to wiped. However, on the Horizon FLEX Client, the archived or locked out virtual machine is not deleted from the disk. Attempting to power on the machine fails with an error.
The Horizon FLEX Client user might receive a message saying the virtual machine will be revoked and deleted permanently. However, clicking OK in the message does not delete the virtual machine from the disk or the virtual machine library. To remove the message and continue, the user must close the Player UI process from the task manager. The virtual machine cannot be powered on again.
This issue is resolved.
VMware Player becomes unresponsive when you double click a virtual machine from the virtual machine library without entering the encryption password
This issue is resolved.
In some cases, a reactivated virtual machine's status shows the status of the virtual machine before it was archived. For example, a reactivated virtual machine's status changes to Expired if it
was expired before it was archived. The Expired status remains, even if a Horizon FLEX administrator changes the virtual machine's expiration date to a future date during reactivation.
This issue is resolved. For the example provided, when you, as an administrator, change the virtual machine expiration date to a future date during reactivation, the status of the virtual machine changes to Pending Sync. When the user powers the virtual machine on in Workstation Player, the Horizon FLEX server displays the status of the virtual machine as Active.
If a Horizon FLEX virtual machine is archived or deleted on the Horizon FLEX server while it is being downloaded by an end user, the download continues and the virtual machine is extracted on the end user's computer, but the virtual machine fails to power on. This problem occurs because the Horizon FLEX Client does not know about the changes on the Horizon FLEX server until the end user tries to power on the virtual machine.
This issue is resolved. Currently, when you use the Horizon FLEX server to archive or delete a Horizon FLEX virtual machine that a user is downloading, the download is cancelled.
The Horizon FLEX server might fail to join a virtual machine to an Active Directory domain if the domain already contains a virtual machine that has the same name, but is in a different OU or subdomain. End users receive an error message that states the domain join operation failed when first starting a Horizon FLEX virtual machine. Horizon FLEX administrators see the status of the virtual machine is "Domain join failed" in the Horizon FLEX Admin Console.
This issue is resolved in that in the FLEX server, a running number pattern is now the default method for naming virtual machines, which prevents naming collisions from occurring. However, if you do not use the running number pattern to name virtual machines, this issue will continue to occur.
Workstation might display two logs in dialog boxes when a user opens a Horizon FLEX virtual machine
If the Use machine name configuration option is configured for a Horizon FLEX virtual machine, the Connect to Server dialog box opens twice, once when the end user opens the Horizon FLEX virtual machine in VMware Workstation and again when the user powers on the Horizon FLEX virtual machine. VMware Workstation is not a supported Horizon FLEX Client. However, VMware Workstation can open a Horizon FLEX virtual machine that is distributed on a USB device. According to the policies of your organization, you might prefer that users not use VMware Workstation to join Horizon FLEX virtual machines to the domain.
This issue is resolved.
The following issues might occur in this version of Horizon FLEX. The known issues are grouped as follows:
Using Horizon FLEX Virtual Machines
New When using certain versions of Firefox to connect to the Horizon FLEX Admin Console, the connection fails and an error page appears
If you are using Firefox v39.0 or later, you cannot connect to the Horizon FLEX Admin Console. Firefox displays an error page that provides you with the option to report the error to Mozilla.
Workaround: Disable TLS 1.0 and enable TLS 1.1 or TLS 1.2. See https://support.mozilla.org/en-US/kb/tls-error-reports.
Powering on a Horizon FLEX virtual machine that is in a Pending Wipe state might lead to an error message
When you perform a Wipe operation from the Horizon FLEX server and then power on the Horizon FLEX virtual machine while it is in a Pending Wipe state, an internal error message dialog box appears in the Horizon FLEX Client host, both for VMware Workstation Player and VMware Fusion. The Horizon FLEX virtual machine is usually deleted from the file system as expected. However, sometimes, Workstation Player stops responding and the virtual machine is not deleted.
Workaround: The workaround varies according to the Horizon FLEX Client.
- VMware Fusion - Ignore the error message dialog box.
- VMware Workstation Player - Click OK in the error message dialog box to dismiss it. If Workstation Player stops responding, use Windows Task Manager to end the Workstation Player process.
Preparing Horizon FLEX Virtual Machines
Fusion Pro cannot create Horizon FLEX virtual machines in Japanese and Simplified Chinese
The virtual disk file name, placeholder.vmdk, prepared by Fusion Pro in Japanese and Simplified Chinese contains non-ASCII characters. Due to the tar creation process, Horizon FLEX only supports file names containing English characters.
Workaround: Use either of the following workarounds:
- If you create a Horizon FLEX virtual machine in Japanese or Simplified Chinese with Fusion Pro, you must distribute the virtual machine to end users without employing the tar creation process. For example, with a USB flash drive.
- Use Workstation Pro instead of Fusion Pro to create a Horizon FLEX virtual machine in Japanese or Simplified Chinese, and keep the virtual machine name without non-ASCII characters.