Client for 32-bit Windows Administrator's Guide - Citrix Knowledge ...

More documents

Recommendations

Info

86 Client for 32-bit Windows Administrator’s Guide Go to Document CenterUsing Citrix SSL Relay with Non-Standard TCP PortsBy default, Citrix SSL Relay uses TCP port 443 on the server running MetaFramePresentation Server for SSL/TLS-secured communication. If you configure SSLRelay to listen on a port other than 443, you must make the Client aware of the nonstandardlistening port number.In Program Neighborhood, users can change the port number in the FirewallSettings dialog box. For step-by-step instructions, see the Program Neighborhoodonline help.To apply a different listening port number for all connections1. Make sure all Client components, including the Connection Center, are closed.2. Open the individual’s user-level Appsrv.ini file (default directory: %UserProfile%\Application Data\ICAClient) in a text editor.3. Locate the [WFClient] section.Set the value of the SSLProxyHost parameters as follows:SSLProxyHost=*:,where is the number of the listening port.4. Save and close the file.To apply a different listening port number to particular connections only1. Make sure all Client components, including the Connection Center, are closed.2. Open the individual’s user-level Appsrv.ini file (default directory: %UserProfile%\Application Data\ICAClient) in a text editor.3. Locate the particular [Connection_Section].Set the value of the SSLProxyHost parameters as follows:SSLProxyHost=*:,where is the number of the listening port.4. Repeat Step 3 for all connection sections for which you want to specify adifferent listening port number.5. Save and close the file.Configuring and Enabling Clients for SSL and TLSSSL and TLS are configured in the same way, use the same certificates, and areenabled simultaneously.When SSL and TLS are enabled, each time you initiate a connection the client triesto use TLS first, then tries SSL. If it cannot connect with SSL, the connection failsand an error message appears.
Go to Document Center Chapter 6 Securing Client Communication 87Forcing TLS Connections for all ClientsTo force the Clients (including the Web Client) to connect with TLS, you mustspecify TLS on the Secure Gateway server or SSL Relay service. See the SecureGateway Administrator’s Guide or SSL Relay service documentation for moreinformation.To configure Program Neighborhood to use SSL/TLS1. Make sure the client device meets all system requirements outlined in thisguide.2. Open Program Neighborhood.3. If you are configuring an application set to use SSL/TLS:Right-click the application set you want to configure and select ApplicationSet Settings. A Settings dialog box for the application set appears.If you are configuring an existing custom ICA connection to use SSL/TLS:Right-click the custom ICA connection you want to configure and selectProperties. The Properties dialog box for the custom connection appears.If you are configuring all future custom ICA connection to use SSL/TLS:Right-click in a blank area of the Custom ICA Connections window andselect Custom Connections Settings. The Custom ICA Connectionsdialog box appears.4. If you are configuring an application set or an existing custom ICA connection:From the Network Protocol menu, select SSL/TLS+HTTPS.If you are configuring all future custom ICA connections:From the Network Protocol menu, select HTTP/HTTPS.5. Add the fully qualified domain name of the SSL/TLS-enabled servers runningMetaFrame Presentation Server to the Address List.6. Click OK.To configure the Program Neighborhood Agent to use SSL/TLS1. Make sure the client device meets all system requirements outlined in thisguide.2. To use SSL/TLS to encrypt application enumeration and launch data passedbetween the Program Neighborhood Agent and the server running the WebInterface, configure the appropriate settings in the Program NeighborhoodAgent Console on the Web server. The configuration file must include themachine name of the server running MetaFrame Presentation Server that ishosting the SSL certificate.
Page 5:
Go to Document Center Contents 5Con
Page 8 and 9:
8 Client for 32-bit Windows Adminis
Page 10 and 11:
10 Client for 32-bit Windows Admini
Page 12 and 13:
Page 14 and 15:
Page 17 and 18:
Go to Document CenterDeploying Clie
Page 19 and 20:
Go to Document Center Chapter 2 Dep
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Go to Document CenterConfiguring th
Page 33 and 34:
Go to Document Center Chapter 3 Con
Page 35 and 36: Go to Document Center Chapter 3 Con
Page 37 and 38: Go to Document Center Chapter 3 Con
Page 39: Go to Document Center Chapter 3 Con
Page 42 and 43: 42 Client for 32-bit Windows Admini
Page 95 and 96: Go to Document CenterUpdating the C
Page 97 and 98: Go to Document Center Chapter 7 Upd
Page 105 and 106: Go to Document Center Index 105Inde
Page 107: Go to Document Center Index 107Sess
show all

Client for 32-bit Windows Administrator's Guide - Citrix Knowledge ...

Create successful ePaper yourself

Delete template?

Save as template?