VMware

VMware Horizon FLEX 1.0 Release Notes

VMware Horizon FLEX 1.0 | 02 December 2014

Last updated: 27 January 2015

Check for additions and updates to these release notes.

These release notes include 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. VMware 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 VMware Horizon FLEX at: http://www.vmware.com/products/horizon-flex.

Known Issues

These known issues include the following topics:

Horizon FLEX Clients (Player Pro and Fusion Pro)

  • When you open a Horizon FLEX virtual machine in a Horizon FLEX Client, you might be prompted to take ownership of the virtual machine.
    Workaround: Click Take Ownership.
  • If you cancel the download of a virtual machine in a Horizon FLEX Client and then start 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 your Horizon FLEX Client to delete the virtual machine from your local computer and download the virtual machine again.

  • If your virtual machine was provided on a USB device, you might see the same virtual machine available for download when you connect to the Horizon FLEX server from your Horizon FLEX Client.
    Workaround: Ignore the virtual machine on the Horizon FLEX server. You do not need to download it.
  • It might take up to two minutes longer than usual for a Windows 8 virtual machine to restart after it joins an Active Directory domain for the first time.
  • If your virtual machine was provided on a USB device, and the virtual machine is configured to join an Active Directory domain, you must provide your login credentials twice. The first time you provide your credentials to open the virtual machine and register it with the Horizon FLEX Policy Server. The second time you provide your credentials to join the domain offline. If you cancel the second domain login dialog box, your virtual machine does not join the domain.
    Workaround: Type your login credentials each time you are prompted to do so.
  • In Player Pro, some certificates cause an invalid security certificate warning to appear. If the Horizon FLEX server uses self-signed certificates, your Horizon FLEX Client asks you to confirm whether the certificate presented by the host should be trusted when you connect to the Horizon FLEX server.
    Workaround
    : Verify that the certificate is a valid certificate for the host. Contact your Horizon FLEX administrator if you have questions and 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, your Horizon FLEX Client does not report instance status correctly to the Horizon FLEX server.
  • If you do not type a Horizon FLEX license key when you first log in to Player Pro, the Connect to VMware Horizon FLEX Server icon does not appear on the Player Pro toolbar.
    Workaround: Type the Horizon FLEX license and then exit and reopen Player Pro. The Connect to VMware Horizon FLEX Server icon appears on the Player Pro toolbar.

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 you change 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 the end user and it synchronizes with the Horizon FLEX Policy Server.
  • Horizon FLEX Client users cannot differentiate between virtual machines that have identical names and descriptions.
    Workaround: Give each Horizon FLEX virtual machine a unique name.
  • If Fusion Pro was used to store virtual machine files in a TAR file, the Horizon FLEX Client might prompt the end user to take ownership of the virtual machine.
    Workaround: Use Workstation to create the virtual machine and TAR file. Alternatively, extract the TAR file, remove the .lck directory, and create the TAR file again by running the tar -cf myvm.tar myvm/ command.
  • A new instance of a virtual machine might not be generated if a previous download of the virtual machine was cancelled by the end user and a new download was started. If end users cancel the download of a virtual machine in their Horizon FLEX Client and start a new download of the same virtual machine, the virtual machine might not power on and a warning appears that states the virtual machine has been revoked. This problem occurs if you delete the virtual machine from the Horizon FLEX server after the end user cancels the download and before the end user restarts the download.
    Workaround: Instruct end users to rename the folder of the downloaded virtual machine. Alternatively, instruct end users to use their Horzion FLEX Client to delete the virtual machine from their local computer and download the virtual machine again.
  • 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.

Authentication

  • The Domain Join reuse flag does not work across organizational units 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 a 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.
  • Workstation is not a supported Horizon FLEX Client. However, 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 you open the virtual machine in Workstation and opens again when you power on the virtual machine. If you choose to connect to the Horizon FLEX server, 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.
  • When Player Pro users download and run Horizon FLEX virtual machines, they encounter an Invalid security certificate warning.
    Workaround: If you plan to change server certificates after a virtual machine has already been registered and downloaded, notify your end users. End users need to ensure the changed certificates are trusted on their local computers. Instruct your end users to connect to the server from which they downloaded their virtual machine. If an Invalid security certificate warning appears, instruct your end users to either allow a one-time exception and connect to the server, or select Always trust this host with this certificate an click Connect Anyway to permanently store the exception. If your end users do not permanently store the exception for self-signed certificates, their Horizon FLEX Client does not report instance status correctly to the Horizon FLEX Policy Server.
  • If an end-user password includes a colon (:), authentication fails with the error The username and password is incorrect when the end user attempts to connect to the Horizon FLEX server from their Horizon FLEX Client.
    Workaround: Do not include a colon (:) in end-user passwords.
  • If you use the Horizon FLEX trial license key, you cannot join a virtual machine to an Active Directory domain. When using the Horizon FLEX trial license key, MMC blocks system configuration updates. In addition, the user account running the management service must have join domain privileges.
    Workaround: For join domain (user + password) accounts, use the relevant wizard to set the join domain account manually. For all other configurations, use the command line interface (CLI) tool in the Wanova.Server.Cli.exe folder on the management server to perform the following steps:
    1. Type Wanova.Server.Cli.exe <management-server-address> to connect to the management server.
    2. Type setConfigParam <config-key> <value> to set the configuration value that you want to change.
      You can find configuration keys in CommonServerConfiguration in the Mirage database.

Top of Page