Using VMware Horizon Client for Mac OS X
September 2014
VMware Horizon
This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
EN-001482-01
Using VMware Horizon Client for Mac OS X
You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com
Copyright © 2010–2014 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com
2 |
VMware, Inc. |
Using VMware Horizon Client for Mac OS X |
5 |
||
1 Setup and Installation 7 |
|
|
|
System Requirements for Mac Clients |
7 |
|
|
System Requirements for Real-Time Audio-Video |
8 |
||
Supported Desktop Operating Systems |
8 |
|
|
Preparing View Connection Server for Horizon Client 9 |
|||
Configure the Client Download Links Displayed in View Portal 5.2 and Earlier Releases 9 |
|||
Install Horizon Client on Mac OS X |
11 |
|
|
Add Horizon Client to Your Dock |
12 |
|
|
Configuring Certificate Checking for End Users 12 |
|||
Configure Advanced SSL Options |
13 |
|
|
Configuring Log File Collection Values |
13 |
|
|
Horizon Client Data Collected by VMware 14 |
|
2 Using URIs to Configure Horizon Client |
17 |
|
|||||
|
Syntax for Creating vmware-view URIs |
17 |
|
|
|||
|
Examples of vmware-view URIs |
19 |
|
|
|
||
3 |
Managing Remote Desktop and Application Connections 23 |
||||||
|
Connect to a Remote Desktop or Application for the First Time 23 |
||||||
|
Hide the VMware Horizon Client Window 25 |
|
|
||||
|
Certificate Checking Modes for Horizon Client |
26 |
|
||||
|
Searching for Desktops or Applications |
27 |
|
|
|||
|
Select a Favorite Remote Desktop or Application 27 |
|
|||||
|
Switch Desktops or Applications |
28 |
|
|
|
||
|
Log Off or Disconnect |
28 |
|
|
|
|
|
|
Configure Reconnect Behavior for Remote Applications |
30 |
|||||
|
Remove a View Server Shortcut from the Home Screen |
30 |
|||||
|
Reordering Shortcuts |
30 |
|
|
|
|
|
|
Roll Back a Desktop |
31 |
|
|
|
|
|
4 |
Using a Microsoft Windows Desktop or Application on a Mac 33 |
||||||
|
Feature Support Matrix |
33 |
|
|
|
|
|
|
Internationalization |
34 |
|
|
|
|
|
|
Monitors and Screen Resolution |
34 |
|
|
|
||
|
Connect USB Devices |
35 |
|
|
|
|
|
|
Configuring USB Redirection on a Mac OS X Client |
37 |
|||||
|
USB Redirection Properties |
38 |
|
|
|
||
|
USB Device Families |
40 |
|
|
|
|
|
|
Turn on Logging for USB Redirection |
41 |
|
|
VMware, Inc. |
3 |
Using VMware Horizon Client for Mac OS X
Using the Real-Time Audio-Video Feature for Webcams and Microphones 42 |
|
|||
When You Can Use Your Webcam |
42 |
|
|
|
Select a Default Microphone on a Mac OS X Client System |
42 |
|
||
Configuring Real-Time Audio-Video on a Mac OS X Client |
43 |
|
||
Configure a Preferred Webcam or Microphone on a Mac OS X Client System |
44 |
|||
Copying and Pasting Text and Images |
46 |
|
|
|
Using Remote Applications 46 |
|
|
|
|
Saving Documents in a Remote Application 47 |
|
|
||
Printing from a Remote Desktop |
47 |
|
|
|
Enabling Virtual Printing on the Mac OS X Client 47 |
|
|
||
Set Printing Preferences for the Virtual Printer Feature on a Remote Desktop |
48 |
|||
Using USB Printers 49 |
|
|
|
|
PCoIP Client-Side Image Cache |
49 |
|
|
|
5 Troubleshooting Horizon Client 51
Reset a Remote Desktop or Application 51 Uninstalling Horizon Client 52
Index 53
4 |
VMware, Inc. |
Using VMware Horizon Client for Mac OS X provides information about installing and using VMware Horizon™ Client™ software on a Mac to connect to a remote desktop or application in the datacenter.
This information is intended for administrators who need to set up a View deployment that includes Mac client devices. The information is written for experienced system administrators who are familiar with virtual machine technology and datacenter operations.
VMware, Inc. |
5 |
Using VMware Horizon Client for Mac OS X
6 |
VMware, Inc. |
Setup and Installation |
1 |
Setting up a View deployment for Mac clients involves using certain View Connection Server configuration settings, meeting the system requirements for View servers and Mac clients, and downloading and installing Horizon Client for Mac from the VMware Web site.
This chapter includes the following topics:
n“System Requirements for Mac Clients,” on page 7
n“System Requirements for Real-Time Audio-Video,” on page 8
n“Supported Desktop Operating Systems,” on page 8
n“Preparing View Connection Server for Horizon Client,” on page 9
n“Configure the Client Download Links Displayed in View Portal 5.2 and Earlier Releases,” on page 9
n“Install Horizon Client on Mac OS X,” on page 11
n“Add Horizon Client to Your Dock,” on page 12
n“Configuring Certificate Checking for End Users,” on page 12
n“Configure Advanced SSL Options,” on page 13
n“Configuring Log File Collection Values,” on page 13
n“Horizon Client Data Collected by VMware,” on page 14
You can install Horizon Client for Mac OS X on all 64-bit Intel-based models that use the Mac OS X 10.6.8 or later operating system.
The Mac on which you install Horizon Client, and the peripherals it uses, must meet certain system requirements.
Model |
64-bit Intel-based Mac |
Memory |
At least 2GB of RAM |
Operating systems |
n Mac OS X Snow Leopard (10.6.8) |
|
n Mac OS X Lion (10.7) |
|
n Mac OS X Mountain Lion (10.8) |
|
n Mac OS X Mavericks (10.9) |
VMware, Inc. |
7 |
Using VMware Horizon Client for Mac OS X
View Connection
Server, Security Server,
and View Agent
Display protocol for View
Software Requirements for RDP
You must install Horizon Client on Mac OS X Mountain Lion (10.8) or later to use remote applications. Remote applications do not appear in
Horizon Client if the client system is running an earlier version of OS X.
Latest maintenance release of View 4.6.x and later releases
If client systems connect from outside the corporate firewall, VMware recommends that you use a security server. With a security server, client systems will not require a VPN connection.
Remote applications are available only on Horizon 6.0 with View servers.
PCoIP or RDP
Remote Desktop Connection Client for Mac from Microsoft, versions 2.0 through 2.1.1. You can download this client from the Microsoft Web site.
NOTE Horizon Client for Mac OS X does not work with Microsoft Remote Desktop 8.0 and later releases.
Real-Time Audio-Video works with standard webcam, USB audio, and analog audio devices, and with standard conferencing applications like Skype, WebEx, and Google Hangouts. To support Real-Time AudioVideo, your View deployment must meet certain software and hardware requirements.
View remote desktop
Horizon Client computer or client access device
Display protocol for View
The desktops must have View Agent 5.2 or later installed. The desktops must also have the corresponding Remote Experience Agent installed, if applicable. For example, if View Agent 5.3 is installed, you must also install the Remote Experience Agent from View 5.3 Feature Pack 1. See the
View Feature Pack Installation and Administration document for View. If you have View Agent 6.0 or later, no feature pack is required.
nReal-Time Audio-Video is supported on Mac OS X Mountain Lion (10.8) and later. It is disabled on all earlier Mac OS X operating systems.
nThe webcam and audio device drivers must be installed, and the webcam and audio device must be operable, on the client computer. To support Real-Time Audio-Video, you do not have to install the device drivers on the desktop operating system where View Agent is installed.
PCoIP
Real-Time Audio-Video is not supported in RDP desktop sessions.
Administrators create virtual machines with a guest operating system and install View Agent in the guest operating system. End users can log in to these virtual machines from a client device.
For a list of the supported guest operating systems, see the "Supported Operating Systems for View Agent" topic in the View 4.6., 5.x, or 6.x installation documentation.
8 |
VMware, Inc. |
Chapter 1 Setup and Installation
Administrators must perform specific tasks to enable end users to connect to remote desktops and applications.
Before end users can connect to View Connection Server or a security server and access a remote desktop or application, you must configure certain pool settings and security settings:
nIf you are using a security server, as VMware recommends, verify that you are using the latest maintenance releases of View Connection Server 4.6.x and View Security Server 4.6.x or later releases. See the View Installation document.
nIf you plan to use a secure tunnel connection for client devices and if the secure connection is configured with a DNS host name for View Connection Server or a security server, verify that the client device can resolve this DNS name.
To enable or disable the secure tunnel, in View Administrator, go to the Edit View Connection Server Settings dialog box and use the check box called Use secure tunnel connection to desktop.
nVerify that a desktop or application pool has been created and that the user account that you plan to use is entitled to access the pool. For View Connection Server 5.3 and earlier, see the topics about creating desktop pools in the View Administration document. For View Connection Server 6.0 and later, see the topics about creating desktop and application pools in the Setting Up Desktop and Application Pools in View document.
IMPORTANT If end users have Retina Display and will use the High Resolution Mode client setting while viewing their remote desktops in full screen mode, you must allocate sufficient VRAM for each Windows 7 or later remote desktop. The amount of vRAM depends on the number of monitors configured for end users and on the display resolution. To estimate the amount of vRAM you need, see the section "RAM Sizing for Specific Monitor Configurations When Using PCoIP" of the topic "Estimating Memory Requirements for Virtual Desktops," in the View Architecture Planning document.
nTo use two-factor authentication with Horizon Client, such as RSA SecurID or RADIUS authentication, you must enable this feature on View Connection Server. RADIUS authentication is available with View 5.1 or later View Connection Server. For more information, see the topics about two-factor authentication in the View Administration document.
If you use View Connection Server 5.2 or an earlier release, and you do not have HTML Access installed, by default, when you open a browser and enter the URL of a View Connection Server instance, the portal page that appears contains links to the VMware Download site for downloading Horizon Client. You can change the default.
The default Horizon Client links on the portal page ensure that you are directed to the latest compatible Horizon Client installers. In some cases, however, you might want to have the links point to an internal Web server, or you might want to make specific client versions available on your own View Connection Server. You can reconfigure the page to point to a different URL.
VMware, Inc. |
9 |
Using VMware Horizon Client for Mac OS X
When you make links for Mac OS X, Linux, and Windows client systems, the correct operating system specific link is shown on the portal page. For example, if you browse to the portal page from a Windows system, only the link or links for Windows installers appear. You can make separate links for 32-bit and 64bit installers. You can also make links for iOS and Android systems, but these operating systems are not automatically detected, so that if you browse to the portal page from an iPad, for example, you see the links for both iOS and Android, if you created links for both.
IMPORTANT If you customize the portal page links, as described in this topic, and later install HTML Access or View Connection Server 6.0 or a later release on the server, your customized portal page is replaced by a VMware Horizon Web portal page, and an icon for using HTML Access is added. For information about customizing that page, see Using HTML Access or see the View Upgrades 6.0 or later document.
Prerequisites
nDownload the installer files for the Horizon Client types that you want to use in your environment. The URL to the client download page is https://www.vmware.com/go/viewclients.
nDetermine which HTTP server will host the installer files. The files can reside on a View Connection Server instance or on another HTTP server.
Procedure
1On the HTTP server where the installer files will reside, create a folder for the installer files.
For example, to place the files in a downloads folder on the View Connection Server host, in the default installation directory, use the following path:
C:\Program Files\VMware\VMware View\Server\broker\webapps\downloads
The links to the files would then use URLs with the format https://server-name/downloads/client- installer-file-name. For example, a server with the name view.mycompany.com might use the following URL for Horizon Client for Windows: https://view.mycompany.com/downloads/VMware-Horizon- Client.exe. In this example, the folder named downloads is located in the webapps root folder.
2Copy the installer files into the folder.
If the folder resides on View Connection Server, you can replace any files in this folder without having to restart the VMware View Connection Server service.
3On the View Connection Server machine, copy the portal-links.properties file and the portal.properties file located in install-path\Server\Extras\PortalExamples.
4Create a portal folder the directory C:\ProgramData\VMware\VDM, and copy the portallinks.properties and portal.properties files into the portal folder.
5Edit the C:\ProgramData\VMware\VDM\portal\portal-links.properties file to point to the new location of the installer files.
You can edit the lines in this file and add to them if you need to create more links. You can also delete lines.
The following examples show properties for creating two links for Horizon Client for Windows and two links for Horizon Client for Linux:
link.win=https://server-name/downloads/VMware-Horizon-Client-x86_64-y.y.y-XXXX.exe#win link.win.1=https://server-name/downloads/VMware-Horizon-Client-y.y.y-XXXX.exe#win link.linux=https://server-name/downloads/VMware-Horizon-Client-y.y.y-XXXX.i386.rpm#linux link.mac=https://server-name/downloads/VMware-Horizon-Client-y.y.y-XXXX.dmg#mac
In this example, y.y.y-XXXX indicates the version and build number. The win text at the end of the line indicates that this link should appear in the browser if the client has a Windows operating system. Use win for Windows, linux for Linux, and mac for Mac OS X. For other operating systems, use unknown.
10 |
VMware, Inc. |
Chapter 1 Setup and Installation
6Edit the C:\ProgramData\VMware\VDM\portal\portal.properties file to specify the text to display for the links.
These lines appear in the section of the file called # keys based on key names in portallinks.properties.
The following example shows the text that corresponds to the links specified for link.win and link.win.1:
text.win=Horizon Client for Windows 32-bit client users text.win.1=Horizon Client for Windows 64-bit client users
7Restart the VMware View Connection Server service.
When end users enter the URL for View Connection Server, they see links with the text you specified. The links point to the locations you specified.
End users open Horizon Client to connect to remote desktops and applications from a Mac OS X physical machine. You install Horizon Client on Mac OS X client systems from a disk image file.
Prerequisites
nVerify that the client system uses a supported operating system. See “System Requirements for Mac Clients,” on page 7.
nVerify that you can log in as an administrator on the client system.
nIf you plan to use the RDP display protocol to connect to a remote desktop, verify that the Mac client system has Remote Desktop Connection Client for Mac from Microsoft, version 2.0 or later installed.
nVerify that you have the URL for a download page that contains the VMware Horizon Client installer. This URL might be the VMware Downloads page at http://www.vmware.com/go/viewclients, or it might be the URL for a View Connection Server instance.
When you browse to a View Connection Server URL, by default the links on that portal page point to the VMware Downloads page. You can configure the links to point to a different location. For more information, see “Configure the Client Download Links Displayed in View Portal 5.2 and Earlier Releases,” on page 9. Depending on how the page is configured, you might also see a link for
HTML Access. HTML Access allows you to connect to a remote desktop or application by using the browser, without installing any client software. Because VMware Horizon Client offers more features and better performance than the HTML Access client, VMware generally recommends that you install the client software.
Procedure
1From your Mac, browse to the URL for downloading the Horizon Client installer file.
For Horizon Client 3.0, the file name format is VMware-Horizon-View-Client-y.y.y-xxxxxx.dmg. For Horizon Client 3.1, the file name format is VMware-Horizon-Client-y.y.y-xxxxxx.dmg. xxxxxx is the build number and y.y.y is the version number.
2Double-click the .dmg file to open it and click Agree.
The contents of the disk image appear in a Horizon Client Finder window.
3In the Finder window, drag the VMware Horizon View Client (Horizon Client 3.0) or VMware Horizon Client (Horizon Client 3.1) icon to the Applications folder icon.
If you are not logged in as an administrator user, you are prompted for an administrator user name and password.
VMware, Inc. |
11 |
Using VMware Horizon Client for Mac OS X
What to do next
Start Horizon Client and verify that you can connect to a remote desktop or application. See “Connect to a Remote Desktop or Application for the First Time,” on page 23.
You can add Horizon Client to your Dock just as you do with any other application.
Procedure
1In the Applications folder, select VMware Horizon View Client (Horizon Client 3.0) or VMware Horizon Client (Horizon Client 3.1).
2Drag the VMware Horizon View Client (Horizon Client 3.0) or VMware Horizon Client ( Horizon Client 3.1) icon to the Dock.
3To configure the Dock icon to open Horizon Client at login or to show the icon in the Finder, select Options and select the appropriate command from the context menu.
When you quit Horizon Client, the application shortcut remains in the Dock.
Administrators can configure the certificate verification mode so that, for example, full verification is always performed.
Certificate checking occurs for SSL connections between View Connection Server and Horizon Client. Administrators can configure the verification mode to use one of the following strategies:
nEnd users are allowed to choose the verification mode. The rest of this list describes the three verification modes.
n(No verification) No certificate checks are performed.
n(Warn) End users are warned if a self-signed certificate is being presented by the server. Users can choose whether or not to allow this type of connection.
n(Full security) Full verification is performed and connections that do not pass full verification are rejected.
For details about the types of verification checks performed, see “Certificate Checking Modes for Horizon Client,” on page 26.
You can set the verification mode so that end users cannot change it. Set the "Security Mode" key in the /Library/Preferences/com.vmware.view.plist (Horizon Client 3.0)
or /Library/Preferences/com.vmware.horizon.plist (Horizon Client 3.1) file on Mac clients to one of the following values:
n 1 implements Never connect to untrusted servers.
n 2 implements Warn before connecting to untrusted servers.
n 3 implements Do not verify server identity certificates.
12 |
VMware, Inc. |
Chapter 1 Setup and Installation
You can select the security protocols that Horizon Client can use. You can also specify the cipher control string.
The advanced SSL options that you configure in Horizon Client are used to encrypt communications between Horizon Client and View Connection Server and View Agent. In Horizon Client 3.1 and later, these options are also used to encrypt the USB channel (communication between the USB service daemon and View Agent).
IMPORTANT If the only protocol you enable on the client is TLS v1.1, you must verify that TLS v1.1 is also enabled on the remote desktop. Otherwise, USB devices cannot be redirected to the remote desktop.
Prerequisites
Verify the security protocol that the View server can use. If you configure a security protocol for
Horizon Client that is not enabled on the View server to which the client connects, an SSL error occurs and the connection fails. For information about configuring the security protocols that are accepted by View Connection Server instances, see the View Security document.
Horizon Client and View Connection Server support TLS v1.0 and TLS v1.1 by default. You should change the security protocols in Horizon Client only if your View administrator instructs you to do so, or if your View server does not support the current settings.
Procedure
1Select VMware Horizon View Client > Preferences (Horizon Client 3.0) or VMware Horizon Client > Preferences (Horizon Client 3.1) from the menu bar and click Advanced in the Preferences dialog box.
2To enable or disable a security protocol, select the check box next to the security protocol name. TLSv1.0 and TLSv1.1 are enabled by default.
3To change the cipher control string, replace the default string in the text box.
The default cipher control string (AES:!aNULL:@STRENGTH) includes cipher suites that use either 128bit or 256-bit AES encryption, except for anonymous DH algorithms, and sorts them by strength.
NOTE In Horizon Client 3.1 and later, the USB service daemon adds RC4 (:RC4-SHA: +RC4) to the end of the cipher control string when it connects to a remote desktop.
4 (Optional) If you need to revert to the default settings, click Restore Defaults.
5Click Confirm to save your changes.
Your changes take effect the next time you connect to View Connection Server.
In Horizon Client 3.1, Horizon Client generates log files in the ~/Library/Logs/VMware Horizon Client directory on the Mac client. Administrators can configure the maximum number of log files and the maximum number of days to keep log files by setting keys in
the /Library/Preferences/com.vmware.horizon.plist file on a Mac client.
Table 1 1. plist Keys for Log File Collection
Key |
Description |
|
|
MaxDebugLogs |
Specifies the maximum number of log files. The maximum value is 100. |
|
|
MaxDaysToKeepLogs |
Specifies the maximum number of days to keep log files. This value has no limit. |
|
|
VMware, Inc. |
13 |
Using VMware Horizon Client for Mac OS X
Files that do not match these criteria are deleted when you launch Horizon Client.
If the MaxDebugLogs or MaxDaysToKeepLogs keys are not set in the com.vmware.horizon.plist file, the default number of log files is 5 and the default number of days to keep log files is 7.
If your company participates in the customer experience improvement program, VMware collects data from certain Horizon Client fields. Fields containing sensitive information are made anonymous.
NOTE This feature is available only if your View deployment uses View Connection Server 5.1 or later.
VMware collects data on the clients to prioritize hardware and software compatibility. If your company's administrator has opted to participate in the customer experience improvement program, VMware collects anonymous data about your deployment in order to improve VMware's response to customer requirements. No data that identifies your organization is collected. Horizon Client information is sent first to View Connection Server and then on to VMware, along with data from View servers, desktop pools, and remote desktops.
Although the information is encrypted while in transit to View Connection Server, the information on the client system is logged unencrypted in a user-specific directory. The logs do not contain any personally identifiable information.
The administrator who installs View Connection Server can select whether to participate in the VMware customer experience improvement program while running the View Connection Server installation wizard, or an administrator can set an option in View Administrator after the installation.
Table 1 2. Data Collected from Horizon Clients for the Customer Experience Improvement Program
|
Is This Field |
|
|
|
Made |
|
|
|
Anonymous |
|
|
Description |
? |
Example Value |
|
|
|
|
|
Company that produced the |
No |
VMware |
|
Horizon Client application |
|
|
|
|
|
|
|
Product name |
No |
VMware Horizon Client |
|
|
|
|
|
Client product version |
No |
(The format is x.x.x-yyyyyy, where x.x.x is the client version |
|
|
|
number and yyyyyy is the build number.) |
|
|
|
|
|
Client binary architecture |
No |
Examples include the following: |
|
|
|
n |
i386 |
|
|
n |
x86_64 |
|
|
n |
arm |
|
|
|
|
Client build name |
No |
Examples include the following: |
|
|
|
n VMware-Horizon-View-Client-Win32-Windows |
|
|
|
n VMware-Horizon-View-Client-Linux |
|
|
|
n VMware-Horizon-View-Client-iOS |
|
|
|
n VMware-Horizon-View-Client-Mac |
|
|
|
n VMware-Horizon-View-Client-Android |
|
|
|
n VMware-Horizon-View-Client-WinStore |
|
|
|
|
|
Host operating system |
No |
Examples include the following: |
|
|
|
n |
Windows 8.1 |
|
|
n Windows 7, 64-bit Service Pack 1 (Build 7601 ) |
|
|
|
n iPhone OS 5.1.1 (9B206) |
|
|
|
n |
Ubuntu 10.04.4 LTS |
|
|
n Mac OS X 10.8.5 (12F45) |
|
|
|
|
|
14 |
VMware, Inc. |
Chapter 1 Setup and Installation
Table 1 2. Data Collected from Horizon Clients for the Customer Experience Improvement Program (Continued)
|
Is This Field |
|
|
|
Made |
|
|
|
Anonymous |
|
|
Description |
? |
Example Value |
|
|
|
|
|
Host operating system kernel |
No |
Examples include the following: |
|
|
|
n |
Windows 6.1.7601 SP1 |
|
|
n Darwin Kernel Version 11.0.0: Sun Apr 8 21:52:26 PDT |
|
|
|
|
2012; root:xnu-1878.11.10~1/RELEASE_ARM_S5L8945X |
|
|
n |
Darwin 11.4.2 |
|
|
n Linux 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24 |
|
|
|
|
17:27:10 UTC 2012 |
|
|
n unknown (for Windows Store) |
|
|
|
|
|
Host operating system architecture |
No |
Examples include the following: |
|
|
|
n |
x86_64 |
|
|
n |
i386 |
|
|
n |
armv71 |
|
|
n |
ARM |
|
|
|
|
Host system model |
No |
Examples include the following: |
|
|
|
n Dell Inc. OptiPlex 960 |
|
|
|
n |
iPad3,3 |
|
|
n |
MacBookPro8,2 |
|
|
n Dell Inc. Precision WorkStation T3400 (A04 03/21/2008) |
|
|
|
|
|
Host system CPU |
No |
Examples include the following: |
|
|
|
n Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GH |
|
|
|
n Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GH |
|
|
|
n |
unknown (for iPad) |
|
|
|
|
Number of cores in the host system's |
No |
For example: 4 |
|
processor |
|
|
|
|
|
|
|
MB of memory on the host system |
No |
Examples include the following: |
|
|
|
n |
4096 |
|
|
n unknown (for Windows Store) |
|
|
|
|
|
Number of USB devices connected |
No |
2 (USB device redirection is supported only for Linux, |
|
|
|
Windows, and Mac OS X clients.) |
|
|
|
|
|
Maximum concurrent USB device |
No |
2 |
|
connections |
|
|
|
|
|
|
|
USB device vendor ID |
No |
Examples include the following: |
|
|
|
n |
Kingston |
|
|
n |
NEC |
|
|
n |
Nokia |
|
|
n |
Wacom |
|
|
|
|
USB device product ID |
No |
Examples include the following: |
|
|
|
n |
DataTraveler |
|
|
n |
Gamepad |
|
|
n |
Storage Drive |
|
|
n |
Wireless Mouse |
|
|
|
|
VMware, Inc. |
15 |
Using VMware Horizon Client for Mac OS X
Table 1 2. Data Collected from Horizon Clients for the Customer Experience Improvement Program (Continued)
|
Is This Field |
|
|
|
Made |
|
|
|
Anonymous |
|
|
Description |
? |
Example Value |
|
|
|
|
|
USB device family |
No |
Examples include the following: |
|
|
|
n |
Security |
|
|
n |
Human Interface Device |
|
|
n |
Imaging |
|
|
|
|
USB device usage count |
No |
(Number of times the device was shared) |
|
|
|
|
|
16 |
VMware, Inc. |
Using URIs to Configure |
2 |
Horizon Client |
Using uniform resource identifiers (URIs), you can create a Web page or an email with links that end users click to launch Horizon Client, connect to View Connection Server, and launch a specific desktop or application with specific configuration options.
You can simplify the process of connecting to a remote desktop or application by creating Web or email links for end users. You create these links by constructing URIs that provide some or all of the following information, so that your end users do not need to supply it:
nView Connection Server address
nPort number for View Connection Server
nActive Directory user name
nDomain name
nDesktop or application display name
nWindow size
nActions including reset, log off, and start session
nDisplay protocol
nOptions for redirecting USB devices
To construct a URI, you use the vmware-view URI scheme with Horizon Client specific path and query parts.
NOTE You can use URIs to launch Horizon Client only if the client software is already installed on end users' client computers.
This chapter includes the following topics:
n“Syntax for Creating vmware-view URIs,” on page 17
n“Examples of vmware-view URIs,” on page 19
Syntax includes the vmware-view URI scheme, a path part to specify the desktop or application, and, optionally, a query to specify desktop or application actions or configuration options.
URI Specification
Use the following syntax to create URIs for launching Horizon Client:
vmware-view://[authority-part][/path-part][?query-part]
VMware, Inc. |
17 |