Skip to main content

VMware Horizon 7.0.3


VMware Official Links for Horizon 7.0.3


Release Notes

Software Download

GA Announcement from VMware

Before you upgrade:

  • When upgrading VMware View Composer you have to upgrade Microsoft .NET framework to version 4.6.1 if you do not do this the install will fail.
  • Also keep in mind if you have older clients that do not support TLSv1.1 or 1.2 they will not work after upgrading to Horizon 7 by default.

New Features:

  • Flash Redirection 
    You can compile a black list to ensure that the URLs specified in the list will not be able to redirect Flash content. You must enable the GPO setting FlashMMRUrlListEnableType to use either a white list or black list.
  • Horizon Agent Policy Settings 
    • The VMwareViewAgentCIT policy setting enables remote connections to Internet Explorer to use the Client's IP address instead of the IP address of the remote desktop machine.
    • The FlashMMRUrlListEnableType and FlashMMRUrlList policy settings specify and control the white list or black list that enables or disables the list of URLs from using Flash Redirection.
  • Horizon PowerCLI
    • View PowerCLI is deprecated. Horizon PowerCLI replaces View PowerCLI and includes cmdlets that you can use with VMware PowerCLI.
    • For more information about Horizon PowerCLI cmdlets, read the VMware PowerCLI Cmdlets Reference.
    • For information on the API specifications to create advanced functions and scripts to use with Horizon PowerCLI, see the View API Reference at the VMware Developer Center
    • For more information on sample scripts that you can use to create your own Horizon PowerCLI scripts, see the Horizon PowerCLI community on GitHub.
  • Horizon 7 for Linux desktops enhancements
    • Audio input support
    • Ubuntu 16.04 support
    • Software H.264 Encoder to support multiple monitors
    • Clipboard redirection support on all distributions
    • vGPU support with NVIDIA M6 graphics card on RHEL 6.6/6.7/6.8/7.2 Workstation x64
  • Horizon Agent and Horizon Client can now leverage H.264 codec technology 
    Previously, Horizon Agent and Horizon Client supported only a single monitor. This feature has been enhanced to support multiple monitors.
  • Remote Desktop Operating System 
    The following remote desktop operating systems are supported:
    • Windows 10 version 1607 Long-Term Servicing Branch (LTSB)
    • Windows Server 2016
  • View Persona Management
    • View Persona Management supports guest operating systems that use the "v6" version of the user profile.
    • You can use the migration tool to migrate the "v2" and "v5" user profiles versions to the "v6" user profile version. The tool is installed with the Persona binary file.

Resolved Issues:

  • When the current user is logged in, the Horizon Client on a Windows 8.1 operating system takes 15 seconds to connect to the Horizon Connection Server.
  • A remote desktop fails in rare cases because the PCoIP server has an incorrect IPv6 address for an IPv4 environment when the virtual machine is configured for both the IPv6 and IPv4 environments but uses only the IPv4 environment.
  • When you use the Cloud Pod Architecture feature to access a desktop from another pod, the value of the Security Gateway field does not get populated in the Desktop Pool, Session, and Users and Groups tabs.
  • View Persona Management does not support any guest operating system that uses the "v6" version of the user profile.
  • In Horizon 7 version 7.0.x, the Horizon Agent ignores the value for the maximum frame rate registry setting.
  • Horizon Administrator performance decreases when you browse or import user data disks from the vCenter server to the Horizon Connection Server.
  • Horizon Administrator fails to enforce the maximum number of virtual machines in a desktop pool when a virtual machine gets stuck in a delete operation.
  • During a Horizon 7.0.2 Horizon Agent Hot Patch deployment, an internal error message appears when you try to upgrade the remote desktop agent that has USB components installed.
  • When you upgrade View Agent 6.1.1 to View Agent 6.2.x on an RDS host running on Windows Server 2012 or 2012 R2, the upgrade fails with an "Internal Error 25030" message. 
  • On rare occassions, initializing Cloud Pod Architecture on any Horizon Connection Server in a pod federation fails and the Horizon Administrator displays the error "no Global instance can be found".
  • There is no alphabetic or any other type of order for the OU and CN structures when you create linked-clone desktop pools in Horizon Administrator.
  • In the Horizon 7 environment, each client has to wait for two minutes to connect to the desktop, which is in a suspended state.

Comments

Post a Comment