3.1
Table Of Contents
- View Manager Administration Guide
- Contents
- About This Book
- Introduction
- Installation
- View Administrator
- Virtual Desktop Deployment
- Client Management
- View Client and View Portal
- Client Connections from the Internet
- Creating SSL Server Certificates
- Using Existing SSL Certificates
- Smart Card Authentication
- RSA SecurID Authentication
- View Client Command Line Options
- Virtual Printing
- Adobe Flash Bandwidth Reduction
- Client Device Information
- Enabling HP RGS Display Protocol
- View Composer
- Overview of View Composer
- Preparing VirtualCenter for View Composer
- Preparing a Parent VM
- Deploying Linked Clone Desktops from View Manager
- Refreshing, Recomposing, and Rebalancing Linked Clone Desktops
- Using an Existing View Composer Database
- Using the SviConfig Tool for View Composer
- Offline Desktop
- Component Policies
- Unified Access
- Troubleshooting
- locked.properties
- Glossary
- Index
View Manager Administration Guide
88 VMware, Inc.
View Client Policies
CertainViewClientfeaturescanbecontrolledthroughpolicies.Forinformationabout
configuringandapplyingpoliciestoViewClientattheglobal,pool,oruserlevelrefer
to“ClientPolicies”onpage 171.
Client Connections from the Internet
Forausertoaccessavirtualdesktop,theirclientsystemmustbeabletoresolvethehost
nameorIPaddressofthespecifiedViewConnectionServer.Initially—andby
default—ViewConnectionServercanonlybecontactedbytunnelclientsthatreside
withinthesamenetworkandarethereforeableto
locatetherequestedserver.
Manyorganizationsrequirethatuserscanconnectfromanexternallocationbyusing
agloballyresolvabledomainorsubdomainnameorIPaddress,orbyreassigning
specificportsonanexistingaddress,inordertorouteclientrequeststotheappropriate
location(typically,thesecurityserver).For
example:
https://view-example.com:443
https://view.example.com:443
https://example.com:1234
However,someadditionalconfigurationwithinViewConnectionServerisrequiredfor
addresseslikethesetowork.
Overview of Client Connections
ViewClientattemptstocreatetwoseparateTCPconnectionsbetweenitselfandView
ConnectionServer.Thefirstconnectionhandlesuseroperationssuchasauthentication,
desktopselection,andsoforth.Thesecondconnectionisinstantiatedafterlogonand
providesatunnelforcarryingRDPdata.
Thefirstconnectionismadeusingthe
URLorIPaddressenteredbytheuserintothe
client.Providingthefirewallandload‐balancingcomponentshavebeenconfigured
correctlyinyournetworkenvironment,thisrequestreachestheserver.Upon
authentication,theFQDNofViewConnectionServerisreturnedtotheclient.
Thesecondconnection(thetunnelconnection,which
isSSL‐encryptedbydefault)is
attemptedusingtheFQDN.However,theconnectionfailsiftheFQDNcannotbe
resolvedbytheexternalViewClient.Anexamplesequenceofexternalandinternal
clientinteractionswiththeserverisshowninFigure 5‐1.