VMware® Horizon Workspace™ 1.8.1 Release Notes
Horizon Workspace Server 1.8.1 | 18 APR 2014 | Build 1752537
Horizon Workspace for Windows 1.8.1 | 18 APR 2014 | Build 1751013
Horizon Workspace for Mac 1.8.1 | 18 APR 2014 | Build 1751014
Horizon Integration Broker 1.8 | 11 MAR 2014 | Build 1575004
Horizon Files for Android 1.8 (Application published on Google Play Store)
Horizon Files for iOS 1.8 (Application published on Apple App Store)
VMware Switch (Application published on Google Play Store)
Last updated: 18 APR 2014
What's in the Release Notes
The release notes cover the following topics:
What's New Beginning with Horizon Workspace 1.8
The following information describes some of the enhancements available in this Horizon Workspace 1.8 release:
- Citrix-based Application integration. From the Horizon Workspace User Portal, users can launch Citrix-based applications via XenApp 5.0, 6.0, and 6.5 using single sign-on. Note: Citrix Receiver must be installed on the client.
- VMware ThinApp package delivery to Windows desktops. Horizon Workspace provides delivery of ThinApp 5.0 packages with 32-bit/64-bit applications to all Windows devices. HTTP delivery is supported to non-domain member endpoints on Windows devices.
- Microsoft Office 365. Single sign-on from Horizon Workspace to Microsoft Office 365 applications. Web-based clients such as Outlook Web Access, rich client applications such as Lync, and email-rich clients such as ActiveSync are supported.
- Horizon Workspace User Portal and App Center. The User Portal has been enhanced to make application resource management easier. The App Center provides users with self-service category filtering, which shows the latest applications added.
- Web application links. IT administrators can now create Web application links that do not require user authentication, allowing administrators to create static Web links.
- Enterprise enhancements, including the following.
- Support for multi-forest Active Directory deployments. You can integrate Horizon Workspace with multiple Active Directory (AD) forests.
- Application access policy. IT administrators can apply access policies and select different authentication methods based on application type.
- Support for enterprise branding of Horizon Workspace.
- VMware Switch enhancements, including the following.
- Support for Android 4.2 (JellyBean) as the workspace operating system.
- Support for Android tablets.
- Enhanced Horizon Mail 1.7x.
Major Issues Resolved in Horizon Workspace 1.8.1
The following describes the major issues that were resolved in the Horizon Workspace 1.8.1 release.
Horizon Workspace Resolved Security Issues
- Horizon Workspace 1.8.1 contains security fixes published in VMware KB articles: VMware KB article 2076551 and VMware KB article 2076783. These articles address a vulnerability reported in CVE-2014-0160. You can find details about this vulnerability in VMware Security Advisory VMSA-2014-0004.
Note: If you already updated Horizon Workspace for Windows and Horizon Workspace for Mac to version 1.8.1 per KB article 2076783, you do not need to update them again.
Important: If you did not install the Horizon Workspace Server patch to fix the critical security vulnerability before updating to Horizon Workspace 1.8.1, after
the upgrade to 1.8.1, you must regenerate and install a new SSL certificate on the gateway-va virtual machine. Follow the post-installation steps in the VMware KB article 2076551.
Workspace for Windows Resolved Issues
ThinApp Integration. Fixed the issue that prevented 64-bit packages from loading the 64-bit version of HorizonPlugin.dll after restarting a machine or when the user logs in.
Workspace for Windows can now authenticate when multiple connectors are configured behind the gateway.
Previously, when using a UNC path for the Horizon Files data folder (e.g. when using the DATA_SYNC_FOLDER installer option), the root volume checking incorrectly detected the share as being down or inaccessible, causing some sync operations to fail. With Horizon Workspace 1.8.1, root volume checking is skipped for UNC paths. As long as the path is accessible, sync operations will succeed as normal.
ThinApp Integration. ThinApp packages are now deleted from Workspace for Windows when all the applications within the ThinApp packages are removed from a user's My Apps page.
Horizon Files Resolved Issues
Fixed the issue that prevented end users with a mixed-case e-mail address to preview or download files.
Office 365 Resolved Issues
Horizon Workspace administrators can now configure the "issuer_uri" attribute for Office 365 applications. Replace your existing Office 365 applications with the new versions published on the cloud application catalog.
Fixed Office 365 active profile authentication issues.
Citrix-based Application Resolved Issues
Added a new flag in the connector to enable or disable sync categories as part of application sync.
1. Log in to the Connector Web interface.
2. Go to Published Apps - Citrix page.
3. Check the box Sync categories from server farms to enable sync.
Horizon Workspace Server Resolved Issues
If a liquibase error occurs during an upgrade from Horizon Workspace 1.5 to Horizon Workspace 1.8, you can fix the error by upgrading to Horizon Workspace 1.8.1.
Change Set changelog-0005-2013-H2.xml::1::HW-31000 failed.
Error: Error executing SQL DELETE FROM saas."Workspace" WHERE "deviceinformation_id" in (SELECT "id" FROM "DeviceInformation" WHERE "platform" = 'fuji'): ERROR: update or delete on table "Workspace" violates foreign key constraint "FK_workspacecmd_workspaceId" on table "WorkspaceCommand" Detail: Key (id)=(50) is still referenced from table "WorkspaceCommand".
liquibase.exception.DatabaseException: Error executing SQL DELETE FROM saas."Workspace" WHERE "deviceinformation_id" in (SELECT "id" FROM "DeviceInformation" WHERE "platform" = 'fuji'): ERROR: update or delete on table "Workspace" violates foreign key constraint "FK_workspacecmd_workspaceId" on table "WorkspaceCommand"
Detail: Key (id)=(50) is still referenced from table "WorkspaceCommand"
Kerberos authentication now works in Workspace for Windows after FQDN is changed to include a port number.
If the error below occurs, you can fix the error by upgrading to Horizon Workspace 1.8.1.
hznAdminTool configureElasticSearch -ES_MULTICAST_ENABLED true Error :
Error : Configuration problem: Failed to import bean definitions from relative location [data-wireup.xml]
Offending resource: class path resource [spring/adminTools-wireup.xml]; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from relative location [authorization-wireup.xml]
Offending resource: class path resource [spring/data-wireup.xml]; nested exception is org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 40 in XML document from class path resource[spring/authorization-wireup.xml] is invalid; nested exception is org.xml.sax.SAXParseException; lineNumber: 40; columnNumber: 85; cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'amq:connectionFactory'
- You can fix the issue with servers not starting when multiple, "No proxy," domains are specified in the system proxy configuration.
Horizon Workspace 1.8.1 is available in the following languages:
- Simplified Chinese
Compatibility, Installation, and Upgrade Horizon Server 1.8.1
VMware® vCenter™ and VMware ESXi™ Compatibility
Horizon Workspace supports the following versions of vCenter and ESXi:
- vCenter 5.0 U2, 5.1, 5.1 U1, 5.5, and 5.5 U1
- ESXi 5.0 U2, 5.1, 5.1 U1, 5.5, and 5.5 U1
Browser Compatibility for the Administrator Web Interfaces
The following Web browsers can be used to view the Configurator Web interface, Connector Web interface, and Administrator Web interface:
- Mozilla Firefox (latest)
- Google Chrome (latest)
- Internet Explorer 9, 10, or 11
- Safari (latest)
For other system requirements, see Installing and Configuring Horizon Workspace on the Horizon Workspace landing page.
Horizon Workspace Component Compatibility
VMware Product Interoperability Matrix provides details about the compatibility of current and previous versions of VMware products and components, such as VMware vCenter Server, VMware ThinApp and VMware Horizon View™.
Upgrading from Horizon Workspace 1.0
Upgrading from Horizon Workspace 1.0 to Horizon Workspace 1.8.x is not supported. You must upgrade from Horizon Workspace 1.0 to Horizon Workspace 1.5 to Horizon Workspace 1.8.x.
Upgrading from Horizon Workspace 1.5
For information about system requirements and installation and upgrade instructions, see Installing and Configuring Horizon Workspace and Upgrading Horizon Workspace.
Upgrading from Horizon Workspace 1.8
If you are upgrading from Horizon Workspace 1.8.0 to Horizon Workspace 1.8.1, follow this procedure instead of the procedure in the Upgrading Horizon Workspace for 1.8.0 guide.
Note: During the upgrade, Horizon Workspace services might be stopped or restarted. Before you begin, plan for system downtime during the upgrade process.
Verify that you have an Internet connection and access to the VMware update server.
- Take a snapshot of each virtual machine in the vApp and the external database virtual machine.
- Go to the configurator-va virtual machine and log in as the root user.
- Run the updatemgr.hzn check command to see if an update is available.
- Run the updatemgr.hzn update command.
- Reboot the vApp.
Messages that occur during the upgrade are saved to the update.log file.
Adding Workspace Desktop Installers to Horizon Workspace
To enable users to download the desktop clients and to automatically update the desktop client for Window and
for Mac computers with a new version, you must add the desktop clients installer files to the downloads directory and
to the auto-update directory on the data-va virtual machines. See
Installing and Configuring Horizon Workspace, Adding Workspace Desktop Clients.
Configuring Horizon View Floating Desktops with Horizon Workspace
If Horizon Workspace for Windows is installed on your floating (non-dedicated) Horizon View Desktops and the Horizon Workspace
auto-update feature is not disabled, you need to install the new version (1.8) of Horizon Workspace for Windows app on the Horizon
View floating pool master image before you add the new 1.8 Workspace installer file to the auto-update directory on the Horizon
Workspace data-va virtual machine.
When you install Horizon Workspace on the View master image, make sure that the auto-update functionality is disabled via the
command line parameter for the Windows installer. See Better Performance with Horizon Workspace for Windows in View Desktop Pools
in these release notes for more information.
Better Performance with Horizon Workspace for Windows in View Desktop Pools
When Horizon Workspace for Windows is installed in a
non-dedicated (floating) Horizon View desktop, you need to make changes to the
Horizon Workspace for Windows installer program so that the client
desktop does not try to download the ThinApp packages or Horizon Files app every
time a new View pool session is created.
Because non-dedicated desktops are inherently stateless and
new sessions can be created when the desktops are recomposed or the user is given
a new desktop from the pool, if the Horizon Workspace for Windows
configuration is not modified, end user will notice slow or bad performance
when using these applications.
Beginning with Horizon Workspace for Windows 1.5.2, you
can modify the client installer program to make the following modification before
the View administrator installs the client to the View template.
- Turn off auto-updates of the Windows client. ENABLE_AUTOUPDATE=0
- If you are using ThinApp packages, enable streaming mode for ThinApp. INSTALL_MODE=RUN_FROM_SHARE
- If end users do not need to sync Horizon Files in these desktops,
disable the Files application. ENABLE_DATA=0
- If you plan to support Horizon Files in these desktops, redirect the
files to a network share that can be accessed from these desktops.
Where #: is a mapped network drive or UNC path. To set the path so that it is appropriately created
and mapped for each user, escape the environment variables. (that is with "^"
escape characters) in the key-value pair used in the command.
Download the EXE file for the Windows client installer program to a Windows system to make these changes.
The following is an example of the command where auto-updates is disabled, streaming mode for ThinApp packages is enabled and the Horizon Files
folders are saved to a network shared drive that users can access.
/v HORIZONURL=https://server.vmware.com ENABLE_AUTOUPDATE=0 INSTALL_MODE=RUN_FROM_SHARE DATA_SYNC_FOLDER=#:\^%username^%\Horizon
To access the full set of Horizon Workspace 1.8 documentation, go to
the Horizon Workspace landing page.
The Horizon Workspace issues added in the most recent release are marked with the * symbol. Other known issues have been carried
forward from previous releases. This section describes known issues for the following subject areas:
Horizon Workspace for Windows
* When users upgrade to the Workspace for Windows, the Horizon Files data sync folder directory location settings are changed from the
previous version's location to the default "C:\Users\%UserName%\Horizon".
Workaround: Users will need to reset the directory location from the Options page.
The time period after which ThinApp client installs fail can be configured
In some cases, the default timeout setting of 10 seconds might not be long enough to finish installing a ThinApp client and the install fails.
You can edit the Horizon Workspace for Windows installer program from the command line to change the value of THINREG_TIMEOUT. The time is measured in
milliseconds. For example to change the timeout to 30 seconds, type VMware-Horizon-Workspace-n.n.n-nnnnnnn /v THINREG_TIMEOUT=30000.
If Horizon Workspace for Windows is already installed, you can edit the Windows registry key entry. For Windows 32-bit this is registry
key HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\Horizon ThinApp\ThinregTimeout. For Windows 64-bit this is registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\Horizon ThinApp\ThinregTimeout (DWORD).
Horizon Files for Android
- On Android
devices, the previewer of the Horizon Files service does not accurately display plain text files that do not use UTF-8 encoding
When users open a file that does not use UTF-8 encoding, the content appears as broken non-ASCII characters.
Instruct users to either upload and preview plain text files with UTF-8 encoding or to open such files with a personal Android application.
Horizon Workspace for Mac
* Auto upgrade does not work for the Workspace for Mac.
Workaround: Send a notification to your users to have them manually upgrade their Workspace for Mac to the 1.8.1 version.
- Client displays message that the entered URL is not a valid Horizon
server address when there are problems with the Mac system's /etc/resolv.conf file
If the resolv.conf file in the /etc folder on the Mac system has problems, the Horizon Workspace client cannot resolve the Horizon Workspace server URL and displays
a message stating that the server address is invalid.
On the Mac system, in a terminal window, create a symbolic link from /etc/resolv.conf to /var/run/resolv.conf using the ln -s command: sudo ln -s /var/run/resolv.conf /etc/resolv.conf
If there is already a resolv.conf file in /etc, before running the ln -s command, delete the existing resolv.conf file or rename it (sudo mv resolv.conf resolv.conf.bak).
Users cannot use the
embedded Chinese input method editor on VMware Ready Android devices
Chinese Pinyin IME for Android is the embedded Chinese input method editor (IME) for VMware Ready devices. When Horizon Workspace users attempt to use this embedded
tool, they do not have access to a majority of the Chinese characters.
To change the Chinese IME on the managed mobile workspaces of VMware Ready Android devices, perform the following steps:
- Import a preferred simplified Chinese IME Android application. See Horizon Workspace documentation for information about importing a mobile application in to your catalog.
- Entitle VMware Ready Android device users to the new Chinese IME application.
The VMware Switch
client application ignores passcode policies that allow passcodes to be fewer than four characters
The Horizon Workspace Administrator Web interface allows you to set a policy to require a passcode with a minimum length of fewer than four characters. However, the
Switch client application on VMware Ready Android devices requires users to create passcodes with at least four characters.
Set passcode policies to require a minimum length of four characters.
Horizon Files on Internet Explorer 10 - uploading a file crashes browser
When working in Horizon Files, some add-ons can cause the browser to crash when uploading a file to the browser. One specific add-on that is a problem is WeDownload Manager.
In addition, some ActiveX related add-ons might cause the browser to crash when uploading a file.
Remove the WeDownload Manager add-on application from the computer.
For ActiveX related add-on, users will need to disable the add-on in the IE Tools > Manage Add-ons page.
Previewing Files in Chrome can cause the preview to freeze
When working in Horizon Files in the Chrome browser, preview a file does not work correctly because by default Chrome uses its own built-in PDF viewer.
Disable the Chrome built-in PDF viewer. To find the built-in viewer, in the Chrome browser address line, users type chrome://plugins. Then, in the page that opens,
they search for Chrome PDF Viewer and click Disable.
Horizon Workspace Server
Occasionally an application configured with a provisioning adapter throws an exception
If the service is restarted following a fresh install, accessing an application from the Administrator Web interface that has a provisioning adapter
configured throws a 500 internal server error.
Restart tcserver on the service-va virtual machine. /etc/init.d/horizon-frontend restart
Citrix Receiver cannot resolve to the IP-address of the servers hosting your Citrix Published Applications
The following situation serves as an example of how this issue might occur. Your Citrix servers are behind the DMZ and a Horizon Workspace user tries to
launch an application from home. Citrix Receiver on the user's device cannot reach the Citrix server behind the DMZ.
You must route the TCP traffic through an external gateway outside the DMZ, in front of the Citrix servers. To route the traffic, you must configure the Citrix
servers with an alternate external IP address that Horizon Workspace passes to the Citrix Receiver instance when a user attempts to launch an application.
In addition, you must edit the ICA properties on the Citrix Published Applications page using the Horizon Workspace Administrator Web interface.
- Configure the Citrix Servers.
- On the Citrix servers, set an alternate external IP address by typing the following command at the prompt:
altaddr / set external-gateway-hostname-FQDN
Where external-gateway-hostname-FQDN is the fully qualified hostname of your gateway server.
- Access the Horizon Workspace Administrator Web interface to add ICA properties.
- Log in to the Administrator Web interface.
- Select Settings > Citrix Published Applications.
- In the ICA Client Client Properties text box, add the following properties:
Where XMLport is the XML transport port number in the Citrix server and TCPport is the TCP traffic port number in the Citrix server.
- Click Save.
- Ensure that following three ports are open in the external-gateway-hostname-FQDN server.
Update your database to add a new row to the GlobalConfigParameters table to configure Horizon Workspace to use the external gateway.
- The port you provided as a value for the HttpBrowserAddress property, such as 80 or 8080.
- The port you provided as a value for the TcpBrowserAddress property, such as 1494.
- The port that the CGPAddress property uses for launch, such as 2598.
- Access the command-line-interface of the database.
The command-line-interface varies depending on which database you use, the internal PostgreSQL database or a supported external database.
- Type the following command:
INSERT INTO "GlobalConfigParameters" (id, "idEncryptionMethod", "strData", "timestamp") VALUES ('xenappSsoProperties',3,'ClearPassword,Domain,LogonTicket,
LogonTicketType,SessionsharingKey,SSLCiphers,SSLEnable, SSLProxyHost,SecureChannelProtocol', 0);
Citrix-based applications cannot be launched in Internet Explorer 8
Horizon Workspace does not support using Internet Explorer 8 to launch a Citrix-based application.
Tell users to upgrade to a newer version of Internet Explorer.
Auto-update of desktop clients does not work if any of the data-va virtual machines are in maintenance mode when the update script runs
If any data-va virtual machine in your Horizon Workspace environment is in maintenance mode when you run the check-client-update command, auto-update of desktop clients does not work.
Before running the check-client-update command on any of the data-va virtual machines, make sure that none of the data-va virtual machines are in maintenance mode.
- Documentation insufficiently describes how to add and resize a disk for buffering files
The "Add or Resize a Disk for Buffering Files " topic, which appears in both the Installing and Configuring Horizon
Workspace guide and the Upgrading Horizon Workspace guide, does not provide detailed instructions.
Use the following information to add or resize a disk for buffering files instead of the information provided in the guides.
When users upload files to folders in Horizon Workspace, Horizon Workspace uploads the files to the gateway-va virtual machine
first and then transfers the files to the appropriate data-va virtual machine. Therefore, the gateway-va virtual machine must have enough disk space
to store the transient files.
During the Horizon Workspace 1.8 installation, Horizon Workspace creates and configures an additional disk of 28 GB for the gateway-va
virtual machine to use to buffer files waiting to upload. During an upgrade to 1.8, Horizon Workspace does not create an additional disk. Therefore,
for an upgrade, you must create the additional buffer disk for the gateway-va virtual machine.
Procedure: Create and Configure an Additional Disk for the gateway-va Virtual Machine
This is an example procedure using vSphere Client 5.5. The steps might vary slightly for other versions of vSphere.
- In the vSphere Client, create an additional disk for the gateway-va virtual machine.
- Shut down the gateway-va virtual machine.
- Right click the gateway-va virtual machine and in the Hardware tab click Add.
- Click Hard Disk for the device type.
- Click Next.
- In the Create a new virtual disk tab, click Next.
- Change the disk size and select storage options as appropriate for your environment.
The disk size of 28 GB that Horizon Workspace uses during the installation process might not be appropriate for your deployment. Determine
the appropriate disk size given the specifics of your deployment. You can change the disk size at any time in the future if necessary.
- Click Next.
- On the Advanced Options page, accept the default settings.
- Click Next.
- On the Ready to Complete page, click Finish.
- Power on the gateway-va virtual machine.
- Log in to the gateway-va virtual machine as root.
- Stop the nginx proxy service.
- Change directories to /opt/vmware/nginx/buffer.
- Remove the existing sub-directories: rm -fr proxy_temp client_body_temp.
- Change directories to the next higher level.
- Mount the disk at /opt/vmware/nginx/buffer.
- Create a file system on the new disk.
mkfs -t ext3 /dev/sdb1
- Edit the /etc/fstab file by adding the following line to the end of the file.
/dev/sdb1 /opt/vmware/nginx/buffer ext3 rw,nosuid,nodev,exec,auto,nouser,async, 0 1
- Issue the mount command.
- Start the nginx proxy service.
What to do next
When the gateway-va virtual machine buffers large files, end user performance is not usually affected. If large files do affect performance,
increase the disk space allotted to the buffer.
Procedure: Resize the gateway-va Virtual Machine Buffer Disk
To resize the gateway-va virtual machine buffer disk, you must delete the disk, which is typically named Hard disk 2, and create a new one following
the steps in the preceding procedure.
- Documentation provides a potentially inaccurate storage
recommendation for the file-sharing service
The "Add VMDKs for Storage" topic in the Installing and Configuring Horizon Workspace guide recommends storage for the file-sharing service
that is 2.5 times the user's quota per account. This is a rough estimate that might be too large.
For this topic, in most cases you can use 1.0 times the user's quota per account as a rough estimate of storage size.
- Documentation about adding a data-va virtual machine back into rotation is unclear
The "Add a data-va Virtual Machine Back into Rotation" topic in the Installing and Configuring Horizon Workspace guide provides inaccurate information.
The topic addresses how to add the data-va virtual machine back after temporarily removing it for maintenance purposes.
Use the following information to add a data-va virtual machine back into rotation instead of the information provided in the guide.
When you finish maintenance on a data-va virtual machine, you can return it to the rotation. After it is back in rotation, you can provision users to it and
users can access the Web Client interface.
Documentation does not list all the supported RSA Authentication Manager versions
- Prepare the data-va virtual machine to be returned to the rotation.
- Log in as the root user.
- Change to the Zimbra user.
su - zimbra
- Add the mailbox service back.
zmprov -l +hzndataServiceEnabled mailbox
- Start the Jetty process.
- Go to the Configurator Web interface at https://ConfiguratorHostname.
- On the System Information page, find the virtual machine you are returning to the rotation and click Exit maintenance mode.
The "Prepare the RSA SecurID Server for the Connector" topic in the Installing and Configuring Horizon Workspace guide provides an incomplete list
of the RSA Authentication Manager versions that Horizon Workspace supports.
Documentation insufficiently describes how to upgrade Horizon Workspace without connecting to the Internet
Note that Horizon Workspace 1.8 supports the following expanded list of RSA Authentication Manager versions: 6.1.2, 7.1 SP2 and above,
and 8.0 and above.
The "Prepare a Local Web Server" topic in the Upgrading Horizon Workspace guide explains how to upgrade Horizon Workspace without an Internet
connection. A prerequisite step is missing and a subdirectory is incorrectly named.
Note the following required changes before you implement the instructions in this topic.
Configuring third-party provider access for View should be set to "allowed"
- Perform the following prerequisite prior to performing the procedure: Contact VMware technical support to obtain the files mentioned in this topic.
- For the service-va virtual machine, name the subdirectory "/svc" instead of "/srv".
The Installing and Configuring Horizon Workspace guide incorrectly states in a note for SAML authentication that "If you use a third-party identity provider
to access View desktops from Horizon Workspace, SAML authentication, on the View Connection server, must be set to "required"."
Documentation does not include a step that is required when you upgrade a Horizon Workspace 1.0 deployment
with multiple service-va instances to Horizon Workspace 1.5
Change the wording for this note.
It should read that SAML authentication on the View Connection server should be set to "allowed".
When your Horizon Workspace 1.0 deployment has more than one service-va instance and you upgrade to Horizon Workspace 1.5, the masterkeys.uber file
is not the same on all the service-va instances. At that point, the masterkeys.uber file exists on each service-va instance, but with different content.
This might result in Horizon Workspace login issues.
When you upgrade a Horizon Workspace 1.0 deployment that includes multiple service-va instances to 1.5 follow the Upgrading Horizon Workspace guide
while also implementing the following instructions:
- After running the updatemgr.hzn command in the configurator-va virtual machine as described in step 2 of "Upgrading Horizon Workspace to Version 1.5,"
use the command line of one of the service-va instances to log in and become the root user.
- Copy the /usr/local/horizon/bin/masterkeys.uber file from one of the service-va instances to all the other service-va instances in your deployment.
You can copy the file from any service-va instance as long as the masterkeys.uber file ends up being exactly the same on every service-va instance.
- Restart the appropriate servers.
If you perform this workaround after you upgraded to Horizon Workspace 1.5, issue the following command in each service-va instance to which
you copied the file to restart the front-end Web application:
service horizon-frontend start
If you perform the upgrade as part of this workaround, complete the rest of the steps in the procedure, which includes powering off and on the vApp.
Documentation provides insufficient information about modifying the Microsoft Windows Preview Server
The "Modifying the Preview Server localconfig File" topic in the Installing and Configuring Horizon Workspace guide does not provide a path to the localconfig
file and provides incorrect paths to the Temp and Log directories.
Note the following information before you implement the instructions in this topic in the guide.
The full path to the Microsoft Preview Server localconfig file is as follows.
C:\Program Files\VMware\Horizon Data Preview Server\localconfig.xml
The Temp and Log directories are incorrect in the topic. The correct path for both directories is as follows.
C:\ProgramData\Vmware\Horizon Data Preview Server.