VMware Horizon FLEX 1.1 Release Notes

VMware Horizon FLEX 1.1 | 03 March 2015

Last updated: 03 March 2015

Check for additions and updates to these release notes.

These release notes include the following topics:

Key Features

VMware Horizon FLEX enables companies to provision and manage local, corporate virtual desktops to workers that were previously difficult or costly to support. Horizon FLEX provides key benefits, which include:

  • 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.

What's New

Horizon FLEX 1.1 adds the following new features:

  • Active Directory organizational unit (OU) sync - Horizon FLEX administrators can synchronize entities in a specific OU instead of synchronizing the entire Active Directory infrastructure.
  • RVM Setup Service usability improvements - Horizon FLEX administrators can run install-rvmsetup.cmd to install the VMware RVM Setup Service in a Horizon FLEX source virtual machine.
  • Pause/Resume virtual machine download - End users can pause and resume a Horizon FLEX virtual machine download operation.
  • Unrestricted modification of virtual machine memory and processor settings - With VMware Fusion Pro 7.1.1 or VMware Player Pro 7.1.0, end users can modify memory and processor settings for a Horizon FLEX virtual machine without having to enter the restrictions password.
  • Mass deployment with VMware Fusion - Horizon FLEX administrators can create a VMware Fusion mass deployment package to install VMware Fusion Pro on any number of end-user Macs.
  • Windows Server 2012 R2 guest operating system support - Horizon FLEX administrators can create Horizon FLEX source virtual machines that have a Windows Server 2012 R2 guest operating system.

Upgrade Notes

To upgrade from Horizon FLEX 1.0 to Horizon FLEX 1.1, perform these tasks:

  1. Go to the VMware Horizon FLEX Download page and download the VMware Horizon FLEX Server and VMware Horizon FLEX Clients installation files for version 1.1.
  2. Upgrade the VMware Horizon Server component.
    • Upgrade the Mirage Management Server.
    • If you use Mirage to manage your Windows virtual machines, upgrade all Mirage Servers.
    • Upgrade the Mirage Web Manager (Web Management Console).
  3. For complete upgrade instructions, see the VMware Mirage Administrator's Guide on the VMware Mirage Documentation page.

  4. Upgrade the VMware Horizon FLEX Clients to the latest versions.
    • For Mac, upgrade to VMware Fusion Pro 7.1.1.
      For upgrade instructions, see Getting Started with VMware Fusion on the VMware Fusion Documentation page.
    • For Windows, upgrade to VMware Player Pro 7.1.0.
      For upgrade instructions, see Getting Started with VMware Player on the VMware Player Documentation page.

Resolved Issues

The following issues were resolved in this version of Horizon FLEX.

  • If Fusion Pro was used to store virtual machine files in a TAR file, the Horizon FLEX Client (Fusion Pro or Player Pro) sometimes prompted the end user to take ownership of the virtual machine. This issue has been resolved.
  • If an end-user password included a colon (:), authentication failed with the error The username and password is incorrect when the end user attempted to connect to the Horizon FLEX server from their Horizon FLEX Client. This issue has been resolved.
  • If an end user did not type a Horizon FLEX license key when first logging in to Player Pro, the Connect to VMware Horizon FLEX Server icon did not appear on the Player Pro toolbar. This issue has been resolved in Player Pro 7.1/Horizon FLEX 1.1.
  • If end users used the Horizon FLEX trial license key, they could not join a virtual machine to an Active Directory domain. When using the Horizon FLEX trial license key, MMC blocked system configuration updates. This issue has been resolved.

Known Issues

The following issues might occur in this version of Horizon FLEX. The known issues are grouped as follows:

Using Horizon FLEX Virtual Machines

  • If an end user cancels the download of a virtual machine in a Horizon FLEX Client and then starts a new download of the same virtual machine, the virtual machine might not power on. A warning states that the virtual machine is revoked.
    Workaround: Rename the folder of the downloaded virtual machine. Alternatively, use the Horizon FLEX Client to delete the virtual machine from the local computer and download the virtual machine again.

  • When a virtual machine is provided on a USB device, end users might see the same virtual machine available for download when they connect to the Horizon FLEX server from the Horizon FLEX Client.
    Workaround: Ignore the virtual machine on the Horizon FLEX server. It does not need to be downloaded.
  • If a virtual machine is downloaded by different end users and all virtual machines power on, end users receive a warning message and might not have network connectivity because all of the virtual machines have the same MAC address. For example: MAC address ******** of adapter Ethernet0 is within the reserved address range or is in use by another virtual adapter on your system. Adapter Ethernet0 may not have network connectivity.
    Workaround: Use the Horizon FLEX Client to manually change the MAC address of the virtual machine. For example, in Fusion Pro, shut down the virtual machine, select VM Settings > Network Adapter > Advanced Options, and click Generate to generate a new MAC address.
  • When end users connect to a Horizon FLEX server, they might see that they are entitled to the same virtual machine multiple times. Users cannot differentiate the virtual machines because the user interface does not identify the entitlement with which a virtual machine is associated.
    Workaround: None
  • 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.
    Workaround: None

Preparing Horizon FLEX Virtual Machines

  • 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.
    Workaround: The virtual machine's status changes to Active after it is powered on by an end user and the virtual machine synchronizes with the Horizon FLEX Policy Server.
  • End users cannot differentiate between virtual machines that have identical names and descriptions.
    Workaround: When preparing virtual machines, give each Horizon FLEX virtual machine a unique name.
  • When preparing a virtual machine for use with Horizon FLEX, if the name of the virtual machine or file name of the virtual machine contains non-ASCII characters, the Horizon FLEX Client might not be able to download, extract, or open the virtual machine.
    Workaround: Copy the virtual machine to end user computers, or make sure the virtual machine's name or file name does not contain non-ASCII characters.

  • When preparing a virtual machine for use with Horizon FLEX, if the location of one of the virtual machine disks is on a different drive than the .vmx file (for example, a virtual machine disk is on the D: drive and the .vmx file is in the default location), the Horizon FLEX Client cannot start the virtual machine after it is downloaded. An error similar to the following message appears when an end user attempts to start the downloaded virtual machine: File not found: D:\Virtual Machines\Win7EntX64\Windows 7 x64.vmdk. The file is required to power on this virtual machine. If this file was moved, specify the new location.
    Workaround: Create all the virtual disks on the same drive as the .vmx file. All the disks should be in the same folder as the .vmx file.
  • The RVM Setup Service is not removed when you uninstall VMware Tools from a source virtual machine. After VMware Tools is uninstalled, the guest operating system reports the following error message: Application or service 'VMware RVM Setup Service' could not be restarted
    Workaround: Stop the RVM Setup Service (net stop rvmsetup) and then run rvmsetup -u to uninstall it.
  • The Horizon FLEX server cannot handle the virtual machine display name defined in the .vmx file for a virtual machine if the case of the displayName property is not as it expects.
    Workaround: Edit the .vmx file for the virtual machine so that the N in displayName is uppercase and all the other letters are lowercase.
  • A Windows 8 virtual machine might take up to two minutes longer than usual to restart after it joins an Active Directory domain for the first time.
    Workaround: None
  • The Domain Join reuse flag does not work across OUs or subdomains.
    Workaround: Delete the current computer object from Active Directory and restart the virtual machine.
  • Only a single machine that has a given name can be a member of an Active Directory domain. Adding additional machines that have the same name overrides the previous machine's trust relationship with the domain.
    Workaround: None. This behavior is normal for Active Directory.
  • 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. If the Use machine name configuration option is configured for a virtual machine, the Connect to Server dialog box opens when an end user opens the virtual machine in VMware Workstation and opens again when the user powers on the virtual machine. If the user chooses to connect to the Horizon FLEX server, VMware Workstation joins the virtual machine to the appropriate domain.
    Workaround: To prevent the virtual machine from joining the domain, choose not to connect to the Horizon FLEX server in the second Connect to Server dialog box.
  • If a virtual machine is provided on a USB device, and the virtual machine is configured to join an Active Directory domain, end users must provide their login credentials twice. The first time they provide their credentials to open the virtual machine and register it with the Horizon FLEX Policy Server. The second time they provide their credentials to join the domain offline. If they cancel the second domain login dialog box, their virtual machine does not join the domain.
    Workaround: End users should type login credentials each time they are prompted to do so.
  • 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. 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.
    Workaround: A Horizon FLEX administrator should use the entitlement wizard in the Horizon FLEX Admin Console to change the machine naming pattern for the virtual machine.

Certificate Authentication Errors

  • In Player Pro, some certificates cause an Invalid Security Certificate warning to appear. If the Horizon FLEX server uses self-signed certificates, the Horizon FLEX Client asks users to confirm whether the certificate presented by the host should be trusted when they connect to the Horizon FLEX server.
    : End users should verify that the certificate is a valid certificate for the host. Use extreme caution when trusting self-signed certificates. If you understand the security risks, you can allow a one-time exception and connect to the Horizon FLEX server, or you can select Always trust this host with this certificate and click Connect Anyway to permanently store the exception. If you do not permanently store the exception for self-signed certificates, the Horizon FLEX Client does not report instance status correctly to the Horizon FLEX server.

Top of Page