VMware Horizon View 5.3.1 Release Notes
|Released 11 March 2014 | View Connection Server Build 1634134, View Composer Build 1634135
Last Updated: 26 March 2016
These release notes include the following topics:
What's New in Horizon View 5.3.1
VMware Horizon View 5.3.1 is a maintenance release that provides full support of the VMware Virtual SAN feature. When you create a pool in View Administrator, you can now select Virtual SAN datastores to store desktop virtual machines. This feature requires that the vSphere version is 5.5 Update 1 or later. For information on upgrading to Horizon View 5.3.1 and administering Virtual SAN in Horizon View, see KB 2073795: Horizon View 5.3.1 on VMware Virtual SAN - Quick Start Guide. For information on setting up Virtual SAN in vSphere, see vSphere Storage Guide. For information on Virtual SAN-related hardware compaitibility, see VMware Compatibility Guide.
Before You Begin
Important note about upgrading to ESXi 5.5 Update 3b or later
Virtual SAN support is the only new functionality in Horizon View 5.3.1 relative to Horizon View 5.3. If you do not plan to use Virtual SAN, there is no need to upgrade to Horizon View 5.3.1.
VMware View 5.1 and later releases include new configuration tasks and requirements that differ from past releases. Read the Horizon View Readme First document. This short overview can help you to avoid potential pitfalls when you install Horizon View 5.3.1 or upgrade to Horizon View 5.3.1 from Horizon View 5.0.x or earlier releases.
For compatibility information and upgrade instructions, see KB 2069327: Compatibility Matrix for Horizon View Components During an Upgrade to Horizon View 5.3 and the VMware Horizon View Upgrades document.
To take advantage of the latest Horizon View enhancements, be sure to use the latest View Client and vSphere releases.
- Install the latest Horizon View Client releases (2.3 as of January 23, 2014). This task includes installing the latest software/firmware updates for your Thin clients or Zero clients, as appropriate. The latest Horizon View Clients are available at Download VMware Horizon View Clients.
- Install the latest version of vSphere and subsequent patch releases to take advantage of the latest storage and graphics capabilities in Horizon View. If you plan to use the Virtual SAN feature, you must install or upgrade to vSphere 5.5 Update 1.
Top of Page
The View Administrator user interface and View Administrator online help are available in Japanese, French, German, simplified Chinese, traditional Chinese, and Korean.
The following Horizon View documents are also available in these languages: VMware Horizon View Readme, VMware Horizon View Administration, VMware Horizon View Installation,
VMware Horizon View Upgrades, VMware Horizon View Security, VMware Horizon View Architecture Planning, and VMware Horizon View Agent Direct-Connection Plug-in Administration.
Top of Page
- VMware Horizon View 5.3.1 is supported on the following versions of VMware vSphere:
- vSphere 5.5 Update 1
If you plan to use the Virtual SAN feature, you must install vSphere 5.5 Update 1.
- vSphere 5.5
To use View Storage Accelerator in a vSphere 5.5 or later environment, a desktop virtual machine must be 512GB or smaller. View Storage Accelerator is disabled on virtual machines that are larger than 512GB. Virtual machine size is defined by the total VMDK capacity. For example, one VMDK file might be 512GB or a set of VMDK files might total 512GB. This requirement also applies to virtual machines that were created in an earlier vSphere release and upgraded to vSphere 5.5.
- vSphere 5.1 with download patch ESXi510-201210001
Space efficient disk technology and the disk space reclamation feature require the use of vSphere 5.1 with download patch
ESXi510-201212001 or later.
- Earlier vSphere releases
See the VMware Product Interoperability Matrix for information about the compatibility of VMware Horizon View 5.3 with current and previous versions of VMware vSphere.
- For the supported browsers for View Administrator and View Portal, see the VMware Horizon View Installation document.
- For more system requirements, see the VMware Horizon View Installation document.
- For more compatibility guidelines, see the Horizon View Readme First document.
- In addition to the supported databases listed in the installation documentation, VMware Horizon View 5.3.1 supports Oracle 126.96.36.199 databases.
- The functionality of VMware Horizon View 5.3.1 is enhanced by an updated set of VMware Horizon View Clients and VMware Horizon View 5.3 Feature Pack 1.
- Multimedia Redirection (MMR) data is sent across the network without application-based encryption and might contain sensitive data, depending on the content being redirected. To ensure that this data cannot be monitored on the network, use MMR only on a secure network. To control access to MMR, you can enable or disable the Multimedia redirection (MMR) policy in View Administrator. You can set this policy globally or for an individual pool or user.
- VMware Horizon View does not support vSphere Flash Read Cache (formerly known as vFlash).
- VMware Horizon View does not support the Windows Server 2012 Active Directory Domain Services (AD DS) domain functional level. You can use Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 AD DS domain functional levels with VMware Horizon View.
Top of Page
Prior Releases of VMware Horizon View
Features that were introduced in prior releases of VMware Horizon View are described in the release notes for each release, along with existing known issues.
Top of Page
The known issues are grouped as follows:
Installation and Upgrade
If you upgrade View Agent 5.2 or 5.3 on a virtual machine that has Horizon View Feature Pack 1 or 2 installed, the installer removes the feature pack. As a result, some features may stop working.
Workaround: After you upgrade View Agent, run the Remote Experience Agent installer to install the latest Horizon View Feature Pack. Be sure to select the components that were installed before the upgrade. See the VMware Horizon View Feature Pack Installation and Administration document for installation instructions.
- The USB HUB device driver might not be installed properly when you install View Agent on a desktop in a manual desktop pool. This issue can occur if, during the View Agent installation, you restart the system before the USB HUB device driver is fully installed.
Workaround: When you install View Agent and you are prompted to restart the system, check the system tray to see if the USB HUB device driver software is still being installed. Wait until the device driver software is completely installed (typically about 30 seconds) before you restart the system.
If you use a command-line script to install View Agent silently, make sure to wait or sleep the script for long enough to allow the driver installation to complete before you restart the system.
If you encounter this issue after View Agent is installed, or you could not delay the system restart during a silent installation, update the USB HUB device driver by taking these steps:
1. In the Device Manager, under Other Devices, right-click VMware View Virtual USB Hub.
2. Click Update Driver Software > Browse my computer for driver software.
3. Go to C:\Program Files\VMware\VMware View\Agent\bin\drivers and click Next to let Windows install the driver.
- HTML Access stops working after you upgrade to View Connection Server 5.3.1.
Workaround: Upgrade the HTML Access software after you upgrade to View Connection Server 5.3.1. Upgrading the HTML Access software involves running the HTML Access installer on your View Connection Server instance and running the Remote Experience Agent installer on the applicable parent virtual machines or virtual machine templates for your desktop pools. For complete instructions, see the VMware Horizon View Feature Pack Installation and Administration document.
- To upgrade a desktop from Windows 8 to Windows 8.1, you must uninstall View Agent, upgrade the operating system from Windows 8 to Windows 8.1, and then reinstall View Agent. Alternatively, you can perform a fresh installation of Windows 8.1 and then install View Agent.
- If you upgrade to vSphere 5.5 or a later release, verify that the domain administrator account that you use as the vCenter Server user was explicitly assigned permissions to log in to vCenter Server by a vCenter Server local user.
When you install View Agent in a Windows 8.1 virtual machine, the installer allows you to select the View Persona Management feature, but this feature is not supported for Windows 8.1 desktops. If you select the View Persona Management feature in the View Agent installer, the feature is not installed.
USB redirection fails in linked-clone images after you upgrade the master image to View Agent 5.3.1.
Workaround: See KB 2062215: USB redirection fails in linked-clone images after you upgrade to View Agent 5.3.1.
When you run the View Agent installer on a Windows 8 virtual machine, the Windows desktop appears black when the video driver is being installed. The Windows desktop might appear black for several minutes before the installation completes successfully.
Workaround: Apply the Windows 8.0 May 2013 roll-up before you install View Agent. See Microsoft KB article 2836988.
When you run any Horizon View installer on a Windows 8.1 virtual machine, the installer can take an unusual amount of time to finish. This problem occurs if the virtual machine's domain controller, or another domain controller in its hierarchy, is unresponsive or unreachable.
Verify that the domain controllers have the latest patches, enough free disk space, and can communicate with each other.
Configuration and View Administrator
The View PCoIP ADM (pcoip.adm) group policy setting, Configure SSL connections to satisfy Security Tools, is not supported in Horizon View 5.3.1. If you attempt to implement certain options in this group policy setting, unexpected results might occur in your View deployment.
Workaround: Do not use this setting in Horizon View 5.3.1.
In View Administrator, if you enter a non-ASCII DNS server name in the network share path for a ThinApp repository, View fails to access
the network path and does not add it as a ThinApp repository.
Workaround: Create a DNS alias (CNAME) with ASCII characters to point to the server name. Use the CNAME in the network path.
An authentication error is displayed if a non-ASCII value for the external URL is entered when configuring a View Server in View Administrator.
Workaround: Use only ASCII characters in the View Server External URL.
Setting the size of the retry port range to 0 when configuring the Configure the UDP port to which PCoIP Server binds and listens group policy causes a connection failure when users log in to the desktop with the PCoIP display protocol. View Client returns the error message The Display protocol for this desktop is currently not available. Please contact your system administrator. The help text for the group policy, and the VMware Horizon View Administration guide, incorrectly state that the port range is 0 through 10.
Workaround: The correct port range is 1 through 10. Set the retry port range to a value between 1 and 10.
View Client and Remote Desktop Experience
Under certain conditions such as a heavy CPU load or network connections with high latency, the VMware Virtual Audio (DevTap) driver can experience a reduction in quality, ranging from distortion to audio drop-outs.
Workaround: See KB 2045764: Audio issues with the VMware Virtual Audio (DevTap) driver running on a Horizon View desktop
View clients cannot connect to View Connection Server if the server name or fully qualified domain name (FQDN) for View Connection Server contains non-ASCII characters.
On desktops that connect using PCoIP and are configured with multiple monitors, if a user plays a slide show in Microsoft PowerPoint 2010 or 2007, specifies a resolution, and plays the slides on the second monitor, part of each slide appears on each monitor.
Workaround: On the host client system, resize the screen resolution on the second monitor to the desired resolution. Return to the View desktop and start the slide show on the second monitor.
On desktops that connect using PCoIP, if users play slides in Microsoft PowerPoint 2010 or 2007 and specify a resolution, the slides are played at that chosen resolution and are not scaled to the current resolution.
Workaround: Choose "Use current resolution" as the playback resolution.
Although you can use multiple monitors for View desktops that have Windows XP and Windows Vista operating systems, some monitor configurations have issues. You must configure the maximum display resolution correctly. For example, to have a 1200x1920 monitor stacked on top of a 1920x1200 monitor, you must configure the maximum resolution to accommodate this combined height. A resolution of 2560x1600 would be appropriate in this case. This issue does not occur with Windows 7 View desktops.
When the PCoIP group policy setting, "Disable sending CAD when users press Ctrl+Alt+Del," is enabled, the Send Ctrl+Alt+Del option in the
Options menu in View Client does not work. This group policy setting is intended to disable sending CAD only when users press the Ctrl+Alt+Del keys in the View desktop, but it also disables sending CAD from the Options menu.
When certain codecs are installed on the client system and MMR is enabled, View Client might crash when playing a video in
Windows Media Player.
Workaround: Uninstall the codec.
If you redirect a local USB drive to a desktop session, and disconnect or log out of the desktop session while writing data to the drive, an exFAT file system
on the drive might be corrupted. You might see an error such as the following when you attempt to write to the USB drive: Error 0x80071AC3: The operation
could not be completed because the volume is dirty. Please run chkdsk and try again.
Workaround: Before you redirect a USB drive to a desktop session, back up the files on the USB drive to another local drive. If the file system
on the USB drive does become corrupted, you can try to copy any valuable data from the USB drive to another local drive, although this operation might fail.
Reformat the USB drive, and restore the data from the backup copy.
For some newer printers, if the color setting for the printer on the local machine is different from the color setting in the Virtual Printer settings for the
View desktop, the local client settings take precedence. For example, if the client computer setting is to print in color but the Virtual Printer setting is to print
gray-scale, the document is printed in color.
Multi-media redirection (MMR) does not play properly in a View Client PCoIP desktop when you connect a projector or external monitor to a laptop computer with
certain ATI graphics cards. Sometimes it displays only a black box.
If you try to connect to an NLA-enabled Vista machine from an NLA-enabled Windows XP client,
the connection fails with the error message An authentication error has occurred
(Code: 0x80090303). Remote Computer: <IP.Address>.
The same error occurs if you try to connect directly with RDP to the NLA-enabled Vista machine.
Workaround: You can connect from Windows Vista clients.
If you are running View Client on Windows Vista build 6.0.6000, you might encounter the following problems:
Workaround: Upgrade your client system to Windows Vista SP1 or higher.
- It is not possible to add a printer in the Control Panel.
- If you try to connect to a desktop using RDP, View Client hangs. The system log will include the error An internal communication error occurred.
Redirected printing will no longer function for a single user session. Check the status of the Terminal Services Device Redirector in the System folder of
If View Client is started from the command line using a command such as wswc.exe -serverURL <IP.Address> -domainName <domain_name>,
the user is prompted for a user name and password. If the user waits about 15 seconds and then clicks Cancel, the wswc.exe process
remains running until another View Client is launched interactively or from the command line.
Workaround: Manually stop the wswc.exe process.
View Client fails to connect to the View security server if a standard server FQDN with localized characters is specified during
security server installation.
Workaround: Specify the IP address of the standard server during security server installation.
You cannot use the virtual printing feature with a View desktop if the desktop source is a Windows Terminal Services server or a virtual machine whose guest operating system is any version of Windows Server.
- Time zone redirection mapping from non-Windows View Clients is not supported when you use the VMware Horizon View Agent Direct-Connection Plug-in to connect directly to View desktops.
After you install the VMware Horizon View Agent Direct-Connection Plug-in, Copy/Paste Clipboard functionality no longer works in existing View desktop sessions.
Workaround: Log off and then log back in to the View desktops.
The virtual printing feature is supported only when you install it from View Agent. It is not supported if you install it with VMware Tools.
When you play videos in Windows Media Player on a desktop, PCoIP disconnections might occur under certain circumstances.
Workaround: On the desktop, open the Windows registry and navigate to the HKLM\Software\Wow6432Node\Policies\Teradici\PCoIP\pcoip_admin_defaults registry key for 64-bit Windows or the
HKLM\Software\Policies\Teradici\PCoIP\pcoip_admin_defaults registry key for 32-bit Windows. Add the pcoip.enable_tera2800 DWORD registry value and set the value to 1.
On Windows 7 client machines, View Client exits when the smart card removal policy is triggered.
If users remove their smart cards while they are logged in, the View desktop exits as expected.
However, on busy Windows Vista desktops, the following informational message might be delayed for one or two minutes:
Your smart card was removed, so you have been logged out of the View Connection Server.
View Client with Local Mode and View Transfer Server
VMware View Client with Local Mode does not support virtual machines with virtual hardware version 10 (HWv10). You will not be able to check out these virtual machines. In vSphere 5.5, virtual machines are created with virtual hardware v10 by default.
Workaround: Create virtual machines with virtual hardware v9 (HWv9) when you create desktop pools for use in local mode.
When you first log in to a checked out local desktop, the desktop might display the following error: There are currently no logon servers available to service
the logon request. This issue is most likely to occur for a Windows Vista or Windows 7 guest operating system on a full virtual machine from a manual or
Workaround: Below the error message on the guest desktop, click OK and log in manually. The error does not reoccur on subsequent logins.
Occasionally with Windows 7 View desktops that have Windows Aero enabled, if you are using a laptop as a client system and you close the laptop, when you later open the laptop, the local mode desktop stops responding. Suspending the client system causes the local mode desktop to freeze.
Workaround: Resize the View Client window or minimize it and then restore it. The View desktop becomes locked and you can press Ctrl+Alt+Ins to log in again.
If you set an SSO timeout limit for View users in View Administrator, and a user checks out a desktop for use in local mode, a checkout operation that takes longer than
the SSO timeout value causes the user's SSO credentials to expire.
Workaround: Extend the SSO timeout limit in the SSO global setting in View Administrator. For details, see "SSO Timeout Limits and Local Mode Desktops" in the VMware Horizon View Administration document.
Do not reconfigure a powered off View Transfer Server using vSphere Client, for example to add memory. Reconfiguration
will cause View Transfer Server's required SCSI controllers to be removed.
Workaround: Make sure that View Transfer Server virtual machines do not require reconfiguration after
they are put into use. If reconfiguration is required, remove and re-add the View Transfer Server from View Administrator.
This will require a reboot.
View Persona Management
View Persona Management features such as folder redirection, offline file population during logon, background download, and replication of local profile files to the remote profile repository fail to function properly if the Windows Client-Side Caching system is in effect on the local system.
Workaround: Synchronize the local Windows client-side cache of profile data and disable the Windows Offline Files feature. For instructions, see KB 2016416: View Persona Management features do not function when Windows Client-Side Caching is in effect.
View Persona Management might not correctly replicate a user persona to the central repository if the desktop virtual machine is extremely low on disk space.
- The Contacts, Links, and Saved Games folders are shown duplicated when a user first logs in to the desktop. These folders are created as local folders rather than redirected folders. View Persona Management does not support redirecting of these three folders (Contacts, Links, and Saved Games).
Workaround: Save the Contacts, Links, and Saved Games folders as a part of the user profile.
- With View Persona Management, you can use group policy settings to redirect user profile folders to a network share. When a folder is redirected, all data is stored directly on the network share during the user session. Windows folder redirection has a check box called Grant user exclusive rights to folder-name, which gives the specified user exclusive rights to the redirected folder. As a security measure, this check box is selected by default. When this check box is selected, administrators do not have access to the redirected folder. If an administrator attempts to force change the access rights for a user's redirected folder, View Persona Management no longer works for that user.
Workaround: See KB 2058932: Granting domain administrators access to redirected folders for View Persona Management.
View Persona Management is not supported on Windows Server 2008 R2 or Windows 8.1 desktops.
Workaround: Install View Persona Management on Windows XP, Windows Vista, Windows 7, or Windows 8 desktops.
vSphere Platform Support
- View Storage Accelerator might take tens of minutes to generate or regenerate the digest files for large virtual disks (for example, a 100GB virtual disk). As a result, the desktop might be inaccessible for longer than expected.
Workaround: Use the blackout period to control when digest regeneration operations are allowed. Also, use the digest regeneration interval to reduce the frequency of these operations. Alternatively, disable View Storage Accelerator in desktop pools that contain very large virtual machines.
If you upgrade a virtual machine with an IDE controller from Windows XP to Windows 7, take a snapshot of the virtual machine, and create a linked-clone pool, the linked clones cannot be customized, and pool creation fails.
Workaround: Add a SCSI controller and a disk to the virtual machine. Next, launch VMware Tools and install a VMware SCSI controller driver on the virtual machine. Next, take a snapshot and create the linked-clone pool.
When you provision linked-clone desktops that are customized by Sysprep, some desktops might fail to customize.
Workaround: Refresh the desktops. If a small number of desktops still fail to customize, refresh them again.
Do not change the log on account for the VMware View Composer Guest Agent Server service in a parent virtual machine. By default, this is the Local System account. If you change this account, the linked clones created from the parent do not start.
vSphere optimizes virtual machine cloning by using the SCSI data mover extended-copy feature. However, a side effect of this
optimization is that linked clone pool provisioning can be slowed down by concurrent full cloning tasks.
Workaround: Do not concurrently provision a linked clone pool and a large full clone pool if the two pools are on
the same SCSI array, sharing the same data mover. Similarly, do not configure a linked clone pool to share a SCSI array
with a full clone pool that uses the delete-desktop-after-logoff policy.
Linked clones that use BusLogic controllers might become unusable when recomposed to a base image that uses an LSI Logic controller.
Linked clones affected by this issue are unable to boot their operating systems, and the administration interface shows errors such
as: View Composer agent initialization state error (-1): Illegal state (waited 360 seconds).
There is no workaround. Changing SCSI type during a recompose is not a supported operation.
Desktop pool provisioning fails with the error message Polling progress failure: Unable to connect to View Composer server <https://machine-name:18443>: java.net.ConnectException: Connection refused: connect.
Workaround: Restart the VMware vCenter Server service and then reprovision the desktop pool.
Windows 8 Support
Reconnecting to a Windows 8 desktop session over PCoIP can take up to 24 seconds. While waiting to reconnect, the user sees a black screen and a mouse pointer. This issue only occurs when a user reconnects to an active desktop session. It does not occur when a user logs off and logs in again.
Adobe Flash optimization settings that use high quality and aggressive throttling are not fully enabled when end users use Internet Explorer 10 on Windows 8 desktops.
Workaround: Use Internet Explorer 9 or earlier on Windows 8 desktops.
On a Windows 8 desktop, if you enable the View Persona Management setting, Remove local persona at logoff, and a user creates a PDF file, logs off of the desktop, and logs back in again, the user cannot open the offline PDF file. The Windows 8 Reader cannot download the offline PDF content.
Workaround: Manually download the file by right-clicking the file and selecting Properties or selecting Open with... Adobe Reader.
When using Internet Explorer 10 on a Windows 8 computer, if you set the browser locale to Traditional Chinese or Simplified Chinese, and you log in to View Administrator, the UI is displayed in English. Note: This issue occurs with IE 10 on Windows 8 and is not a VMware View issue.
Workaround: Use an alternate browser to log in to View Administrator.
- If a user of a Windows 8 View desktop logs in using Kerberos authentication, and the desktop is locked, the user account for unlocking the desktop that Windows 8 shows the user by default is the related Windows Active Directory account, not the original account from the Kerberos domain. The user does not see the account he or she logged in with.
This is a Windows 8 issue, not directly a View issue. This issue could, but does not usually, occur in Windows 7. It does not occur in Windows XP, which shows the correct user name from the Kerberos domain.
Workaround: The user must unlock the desktop by selecting "Other user." Windows then shows the correct Kerberos domain and the user can log in using the Kerberos identity.
When provisioning 64- or 32-bit Windows 8 desktops in a vSphere 5.1 or later environment, the Sysprep customization can fail. The desktops end up in an ERROR state with a Customization timed out error message. This issue occurs when anti-virus software is installed in the parent virtual machine or template. The issue applies to full clone and linked clone desktops. It does not apply to linked clone desktops customized with QuickPrep.
Workaround: Uninstall the anti-virus software on the parent virtual machine or template and recreate the pool.
When recomposing Windows 8.1 desktops, the Sysprep customization can fail with a Customization operation timed out error message. This problem is caused by a Windows 8.1 scheduled maintenance task that recovers disk space by removing unused features.
Workaround: Use the following command to disable the maintenance task immediately after completing Setup: Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"
- The Local Mode and View Persona Management features are not supported with Windows 8.1 desktops.
Windows Server 2008 R2 Support
- When you install View Agent in a Windows Server 2008 R2 virtual machine, the View Agent installer displays the message This product can only be installed on 32-bit Windows XP SP3 or Windows Vista Enterprise/Business, Windows 7, Windows 8, or 64-bit Windows 2008 Server.This error occurs because Service Pack 1 (SP1) is not installed in the Windows Server 2008 R2 virtual machine. The message should list 64-bit Windows 2008 SP2 or 64-bit Windows 2008 R2 SP1.
Workaround: Install SP1 in the Windows Server 2008 R2 virtual machine and rerun the View Agent installer.
You cannot connect to a Windows Server 2008 R2 desktop, or you encounter a black screen the first time that you use View Client, even though the desktop that you are connecting to is in the Available state.
Workaround: Shut down and power on the Windows Server 2008 R2 virtual machine. When the desktop is in the Available state, try to connect again. Note: Resetting or restarting the virtual machine does not solve this problem. You must shut down the virtual machine first and then power it back on.
Horizon Workspace Integration
If you change the default HTTPS port, 443, on a View Connection Server instance or security server, and Horizon users try to start their desktops from the Horizon User Portal, the desktops fail to launch. This issue occurs when users attempt to access their desktops via Horizon Workspace with either View Client or HTML Access.
Workaround: Keep the default HTTPS port 443.
When you add a SAML Authenticator in View Administrator, an "Invalid certificate detected" window might be displayed, even when the Metadata URL points to a trusted certificate in the Trusted Root Certificate Authorities folder in the Windows certificate store. This issue can occur when an existing SAML Authenticator with a self-signed certificate was using the same Metadata URL when the trusted certificate was added to the Windows certificate store.
- Remove any trusted certificates for the Metadata URL from the Trusted Root Certificate Authorities folder in the Windows certificate store.
- Remove the SAML Authenticator with the self-signed certificate.
- Add the trusted certificate for the Metadata URL to the Trusted Root Certificate Authorities folder in the Windows certificate store.
- Add the SAML Authenticator again.
Virtual SAN datastores do not support the Space Effecient Virtual Disk format. After a rebalance operation, the "VM disk space reclamation" setting of a pool may be shown as "Yes" in View Administrator. You can safely ignore this setting on the pool summary page as Virtual SAN datastores do not support space reclamation.
Virtual SAN is a tiered storage architecture with the following characteristics:
Since Virtual SAN provides automatic tiering and the caching of all I/O operations, there is no need for using replica tiering. Hence, the replica tiering feature is not supported.
- An SSD tier for caching reads and buffering writes.
- A magnetic disk tier for persistent virtual machine data.
Virtual SAN datastores are only accessible from hosts that belong to the Virtual SAN cluster, and not from hosts that belong to a different cluster. Therefore, rebalance of pools from one Virtual SAN datastore to another Virtual SAN datastore in a different cluster is not supported.
Adding a disk that contains data to a Virtual SAN cluster will cause pool or desktop deletion to fail.
Workaround: Before you add a disk to a Virtual SAN cluster, make sure that the disk does not contain any data.
Mixing Virtual SAN and Non-Virtual SAN Datastores
As a best practice, do not mix Virtual SAN and non-Virtual SAN datastores for storing View virtual machine virtual disks. Only Virtual SAN datastores should be used. In cases where non-Virtual SAN datastores are present, the only supported options for the non-Virtual SAN datastores are:
No other use case involving Virtual SAN and non-Virtual SAN datastores is supported in this release.
- Storing the virtual disks of View infrastructure components such as View Connection Server, View Composer, etc.
- The migration of View virtual machines from non-Virtual SAN datastores to Virtual SAN datastores using the rebalance operation.
On Windows 7, if you pin a View Connection Server or View Client desktop session in a jump list and reconnect to it with different connection settings,
the item might appear under both Pinned and Recent servers in the jump list.
To ensure that non-English versions of virtual applications that are captured by ThinApp display the correct language user interface,
during the ThinApp capture you must open the natively installed version on the capture machine before you start the post-scan
For virtual machines that have hardware version 8, the maximum allowed video RAM is 128MB. For virtual machines that have hardware version 9 and later, the maximum allowed video RAM is 512MB. If you configure a value from View Administrator that exceeds the video RAM limit for a virtual machine's hardware version, errors appear in the vSphere Client Recent Tasks pane and the configuration operation keeps repeating. This problem occurs only if you configure the video memory value through View Administrator (Pool Settings page) and not through vSphere Client.
Workaround: Either upgrade the hardware version of the virtual machines in vSphere Client, or use View Administrator to set the proper value for video memory based on the current virtual machine hardware version.
Top of Page