| MetaFrame offers you a choice of three ICA Win32 Clients, and an ICA Java Client for use on 32-bit Windows systems and other java compliant devices. The following is a little about each of the clients: ICA Win32 Program Neighborhood Agent The state-of-the-art ICA Win32 Client Transparent integration of published resources with the client desktop Native support for the full feature set of MetaFrame XP Native support for the Windows 2000 and Windows XP operating systems Requires Citrix NFuse Classic 1.71 ICA Win32 Web Client The lean ICA Win32 Client for quick distribution Web browser-based access to published resources from links on your Web page No user interface, completely hands-off user experience Limited support for the full feature set of MetaFrame XP Native support for the Windows 2000 and Windows XP operating systems Requires Citrix NFuse Classic or Application Launching and Embedding (ALE) ICA Win32 Program Neighborhood Client Program Neighborhood user interface Requires initial user configuration Native support for MetaFrame XP features Native support for the Windows 2000 and Windows XP operating systems Does not require NFuse Classic ICA Java Client The platform-independent, zero-install ICA Client No user interface, completely hands-off user experience Limited support for the full feature set of MetaFrame XP The ICA Win32 Program Neighborhood Agent allows you to seamlessly add published application content directly to the users local desktop. With the Program Neighborhood Agent, users can access remote applications by clicking icons on the Windows desktop, in the Start menu, in the Windows system tray, or a combination of these. The Program Neighborhood Agent operates in the background. It has no user interface, except for a shortcut menu in the system tray. Therefore, working with remote applications has the look and feel of working with local applications. The default properties for all Program Neighborhood Agents on your network are controlled by a single, editable configuration file called Config.xml. This file is placed on the NFuse Classic server during NFuse Classic installation. You can edit Config.xml to dynamically manage and control the clients on your network. For example, you can edit Config.xml to prevent users from editing certain settings and the changes are automatically configured on the local client device. The Program Neighborhood Agent communicates with the NFuse Classic web server over HTTP or HTTPS protocols, which makes it easy to pass through firewalls using port 80 or 443. The PN Agent client can be deployed both automatically and manually. If you will be using the PN Agent exclusively then you can set NFuse Classic to automatically push the Program Neighborhood Agent client by editing the NFuse.conf file as defined below. 1. Open the NFuse.conf file, by default located in the c:\Program Files\Citrix\NFuse\Conf folder. 2. Edit the Win32Client parameter and change the ica32.exe to ica32a.msi. For example: Win32Client=Click here for the Client&/Citrix/ICAWEB/en/ica32/ica32a.msi 3. Click Start click Run type: IISRESET and click OK. The following defines how to manually install the Program Neighborhood Agent on a local workstation. 1. Download the Program Neighborhood Agent Client from http://www.citrix.com/download. When finished run the downloaded ICA32a.MSI file and click Next to start the installation.  2. Click to select the I accept the license agreement radio button and click Next.  3. Click Next to accept the default ICA client location.  4. Enter the server address of an NFuse-enabled web server. You can use http: or https:. If you have followed my recommendations and installed CSG and have secured the NFuse web server with an SSL certificate then enter https://nfuse_enabled_webserver and click Next with finished.  5. Click Next to accept the default program folder name.  6. Enter a name to be assicated with the local workstation. Remember that this name must be unique to the network. Click Next when finished.  7. The next screen asks if you would like to enable Single Sign-On. If you are installing the PN Agent of a workstation that you will be logging on to with the same username and password as the Citrix users account then click Yes, othewise click No. Click Next with finished.  8. Click Next to install the Program Neighborhood Agent.  9. Click Finish.  You have now successfully installed the Program Neighborhood Agent and are ready to take advantage of seamlessly adding published applications to the end-users desktop, programs group and or system tray not to mention client to server content redirection. The ICA Win32 Web Client is used if you want users to launch published resources from within their familiar Web browser. This ICA Client requires the use of NFuse Classic or ALE (Application Launching and Embedding) The Web Client is available as a self-extracting executable. At approximately 1.8MB in size, this package is significantly smaller than the other ICA Win32 Clients. The smaller size allows quicker downloads and installation. You can configure the ICA Win32 Web Client for silent user installation. The ICA Win32 Web Client (ica32t.exe) can also be automatically deployed. Keeping with the goal of limited client touch, I recommend using the ICA32 Web Client and NFuse Classic to automatically deploy it. One method of deploying ICA Clients on your users devices is to use the Web-based ICA Client installation, which is a default component of NFuse Classic. This feature uses HTML documents and ICA Client installation files, stored on a Web server, to determine the type of client device and Web browser, and display the user with a link to the appropriate ICA Client installation file. When users click on a link, the ICA Client is installed on their client device. The following shows the default installation option:  In order to take advantage of Web-based ICA Client installation you will need to verify that the ICA clients are installed to the NFuse web server. (/webroot/Citrix/ICAWEB/language/platform, i.e., C:\inetpub\wwwroot\citrix\icaweb\en\i386\). If during the installation of NFuse use did not choose to install the ICA Client to the ICAWEB directory then you will need to copy them now. 1. Create a directory called \Citrix\ICAWEB off the root of your Web server. 2. Insert the MetaFrame XP with Feature Release 2 Components CD in your Web servers CD-ROM. 3. Change directories to the CDs ICAWEB directory and copy the contents of the ICAWEB directory on the CD into the /Citrix/ICAWEB directory on the web server. Make sure you copy the contents of the directory and not the ICAWEB directory itself. For more information about the utilize NFuse to automatically deploy ICA Clients please refer to the Client Download Settings section of the ICA Client Deployment section of this document. If the design calls for deploying ICA Clients over a low-bandwidth network or you are not sure what platform your users are on, consider using the ICA Java Client. The ICA Java Client is a Java applet that is cross-platform compatible and can be deployed by the NFuse Classic server to any Java-compatible Web browser. Using NFuse Classic, you can configure the ICA Java Client to be a small download (as small as 300K) by removing unwanted components. You can also allow users to control which ICA Java Client components they require. The ICA Java Client is configured and optimized for zero-residence download-and-run deployment, which gives you the ability to connect from anywhere without the need to install an ICA Client. For information on how to configure NFuse Classic 1.71 to utilize the ICA Java Client, please refer to the Embedded Application in the ICA Client Deployment section of the Implementation Phase in this document. For information of how the end-user would configure NFuse to use the ICA Java Client please refer to Sample end-user training document in the End-User Training section of the Readiness Phase in this document. The following defines how to deliver your private CA root certificate to clients using the ICA Java client in NFuse Classic 1.71. If you created your own digital certificates for use with Citrix Secure Gateway or the SSL Relay Service, you need to deliver your private CA root certificate to all client devices. Windows ICA clients read root certificates from the client certificate store in the Windows operating system, but the ICA Java client does not have access to that certificate store. Therefore, by default, you will find that the Win32 ICA client connects successfully using SSL but the ICA Java client fails to connect. In order to use a private root certificate with the ICA Java client in NFuse Classic 1.71, your root certificate must be exported to a file, copied to your web server, and then changes must be made to the template.ica and guest_template.ica files: 1. Export your private root certificate to a DER-encoded binary file named myroot.crt. 2. Copy this file to the NFuse Classic 1.71 web server in the document root beneath /Citrix/ICAWEB/en/icajava. For example, http://NFuse17-server-name/Citrix/ICAWEB/en/icajava/myroot.crt should be a valid URL. 3. On the NFuse Classic 1.71 web server, locate the template.ica and guest_template.ica files. On Windows/IIS servers running NFuse Classic 1.71, these files are located beneath %ProgramFiles%\Citrix\NFuse. Edit each the files and add the following two lines just below the [NFuse_IcaEncryption] tag: SSLNoCACerts=1 SSLCACert0=myroot.crt Changes should take effect immediately and ICA Java client users should now be able to connect using SSL. If you are running Suns Java plug-in changes to to appembed.asp are required in NFuse Classic 1.71 in order to support Windows Internet Explorer. Users who have installed the Java Virtual Machine (JVM) plug-in from Sun Microsystems and opt to use the Sun JVM for applet tags will not be able to connect to MetaFrame applications using the ICA Java client in NFuse Classic 1.71. The error message users receive is: java.lang.ClassNotFoundException: com.citrix.JICA.class NFuse Classic 1.71 renders improper applet HTML for Windows/IE users because it assumes these users will use the Microsoft JVM. To resolve this issue, either 1) disable the option in Internet Explorer to use Sun JVM for applets, or 2) edit the appembed.asp file to accomodate these users: Disable the Sun JVM in Internet Explorer: In Internet Explorer select the Tools > Options menu and click the Advanced tab. Locate the option that says "Use Sun JVM for <applet>" and clear that checkbox. or Edit the appembed.asp file: On your NFuse Classic 1.71 web server, edit the /Citrix/NFuse17/appembed.asp file: o Locate the following line of code, around line 408: o hange this line so that it reads: o Locate the following line of code, around line 414: | jicaPackages = Replace(jicaPackages, ",", packageSuffix & ",") | Replace this line with the following three lines: | jicaCabFiles = jicaPackages jicaPackages = Replace(jicaPackages, ",", packageSuffix & ",") jicaCabFiles = Replace(jicaCabFiles, ",", "M.cab,") | o Locate the applet tag, starting aroud line 435: | <applet code=com.citrix.JICA width="<%=DesiredHRES%>" height="<%=DesiredVRES%>" codebase="/Citrix/ICAWEB/<%=langCode%>/icajava" archive="<%=jicaPackages%>" name="javaclient" > <param name=cabinets value="<%=jicaPackages%>"> | o Edit the tag so that it reads as follows: | <applet code=com.citrix.JICA width="<%=DesiredHRES%>" height="<%=DesiredVRES%>" codebase="/Citrix/ICAWEB/<%=langCode%>/icajava" archive="<%=jicaPackages%>" name="javaclient" MAYSCRIPT > <param name=cabinets value="<%=jicaCabFiles%>"> | Changes should take effect immediately. When you install MetaFrame, the ICA Win32 Program Neighborhood Client is installed on the MetaFrame server. To overcome the lack of Published Application support on alternative devices (Mac, Linux, Thin Terminals) and to give users the benefits of Program Neighborhood, you can publish the ICA Win32 Client application on your MetaFrame XP servers. Users of the ICA Client on other platforms can create one connection in their connection managers to the Program Neighborhood application. After they connect to Program Neighborhood, they can use the interface to launch all other applications that are published on all the servers in the server farm. Use Citrix Management Console to publish the application, the executable file to publish is Pn.exe. This program file is located at %SystemRoot%\Program Files\Citrix\Ica PassThrough. The following defines hbow to install the ICA Client on a Redhat Linux 7.1 client. 1. Download the client from www.citrix.com/dowload or Navigate to a pre-configured NFuse site which has the client available for download  2. Log on as root at the client workstation. 3. Open a command window. 4. If you are installing the ICA Client from a CD-ROM, insert the CD-ROM in the drive. Mount the CD-ROM using the appropriate instructions for your workstation. Change to the ICAinst/IcaUNIX directory (ICAclient/IcaUNIX for Version 3.0 installations) on the mounted CD-ROM. or If you are installing the ICA Client from a tar file, uncompress the tar file and extract the contents into a temporary directory.  5. Run the setup program by typing ./setupwfc and press ENTER. or If file names on the CD-ROM are displayed in uppercase and are followed by other characters (such as ;1), use the command ./SETUPWFC* and press ENTER. The following menu options appears.  6. To install the ICA Client, type 1 and press ENTER. The installation procedure prompts: | Please enter the directory in which Citrix ICA Client is to be installed [default /usr/lib/ICAClient] or type quit to abandon the installation: | 7. To install in the default location, press ENTER. The installation procedure allows you to confirm that you want to proceed. 8. To proceed, type y and press ENTER. To cancel the installation, type n and press ENTER. The installation procedure displays the Client Software License Agreement and then prompts for confirmation to proceed. 9. To proceed, type y and press ENTER. To cancel the installation, type n and press ENTER. If you have Netscape Navigator installed you will prompted to choose installation of the plug in. If you require the plug in, press y. 10. When the installation is complete, the main installation menu is displayed again. To exit from the setup program, type 3 and press ENTER.  The following defines how to start the ICA UNIX Client through the remote application manager and or to launch a application using NFuse. To start the UNIX client (remote application manager) At the UNIX prompt, type /usr/lib/ICAClient/wfcmgr and press ENTER Note: /usr/lib/ICAClient is the directory in which you installed the ICA Client. Note: If the ICA Client has not been installed in the default installation directory, ensure that the environment variable $ICAROOT is set to point to the actual installation directory. To open a connection using a Web browser (NFuse) If you are using Netscape Navigator, Web browser configuration to enable Citrix ICA session connection is normally carried out automatically during installation. If you need to set up mailcap and MIME files for Netscape Navigator manually, use the following file modifications so that .ica files start up the ICA Client executable, wfica. (To use other browsers, you will need to modify the .mailcap and MIME files accordingly.) The .mailcap file modification is: In $HOME, create ormodify the .mailcap file and add the line: For Version 3.0 Citrix ICA for UNIX Clients: | application/x-ica; wfica %s | For Version 6.0 and later Citrix ICA for UNIX Clients: | application/x-ica; /usr/lib/ICAClient/wfica -file %s; x-mozillaflags= plugin:Citrix ICA | The application wfica must be in the path. The %s indicates that the full filename of the .ica file is passed to the application. The additional text in the Version 6.0 mailcap file is to make use of the Netscape Citrix Client plug-in. For Version 3.0 Citrix ICA for UNIX Clients only, the mime file modification is: In $HOME, create ormodify the .mime.types file and add the line: The x- in front of the format ica indicates that ica is an unofficial MIME type not supported by the Internet Assigned Numbers Authority (IANA). Checking the Browser Plug-in:  Client may be launched via browser plug-in or local Citrix client application using NFuse.    The Netscape plug-in for UNIX clients was introduced in the Version 6.0 clients. Normally, it is integrated with Netscape when the client is installed. However some operating systems or distributions may have Netscape installed in a location that the installer doesn't know about, in which case the plug-in may not work properly. The Netscape UNIX plug-in launches an embedded client session if the <embed> tag is used with an .ica file on an HTML page, and a separate session if the <A HREF> tag is used. Things to look for if this does not function properly (that is, the browser simply displays the contents of an .ica file or asks if you want to save it to disk): 1. Is ICAROOT set correctly to the location where the client is installed? 2. Has the user exited and restarted Netscape after the client was installed? 3. Does the plug-in show up when the user clicks About > Plugins? 4. Does the plug-in show up from the Edit > Preferences > Navigator > Applications dialog box? It should be seen as Citrix ICA Plugin:Citrix ICA Client. If the user edits this section, is the MIME type shown as application/x-ica, Suffixes ica, and Handled by Plugin: Citrix ICA Client? 5. What's in the /usr/local/lib/netscape/plugins directory? There should be a symlink npica.so to the npica.so in the client installation directory. 6. What's in the /usr/local/lib/netscape/mime.types directory? There should be something like application/x-ica; /wfica -file %s; x-mozilla-flags=plugin:Citrix ICA. What happens if the user removes the x-mozilla-flags part? 7. What's in the /usr/local/lib/netscape/mime.types directory? There should be something like type=application/x-ica exts=ica desc=Citrix ICA. 8. Is the user using any user-specific Netscape mailcap/mime.types/plugin settings (that is, ~/.mailcap, ~/.mime.types and ~/.netscape/plugins). What happens if these files are removed? 9. Has the user installed more than one copy of Netscape on the system? If so, is environment variable MOZILLA_HOME pointing to the correct Netscape installation directory? To register application/x-ica as a Netscape Navigator MIME type: 1. Install the ICA Client on the client machine. 2. Start Netscape Navigator. 3. From the toolbar, select Edit, then Preferences. Under Navigator, select Applications. 4. Click the New Type button. 5. In the Description field, type ICA file. 6. In the File field, type .ica. 7. In the MIME type field, type application/x-ica. 8. In the Application to field, type or browse to the location of the ICA Client. 9. Click OK. Most browsers have a long list of trusted Certificate authorities. If you purchase a server certificate for your NFuse or CSG server from one of these CAs then the client inherently trusts your server to connect via SSL.  The following defines how to use private CA root certificates with UNIX-based ICA clients in order to make SSL connections to MetaFrame through the Citrix SSL Relay Service or a Citrix Secure Gateway server. When using a private certification authority (e.g. Microsoft Certificate Services) to issue server certificates for use with the Citrix SSL Relay service or Citrix Secure Gateway, you assume the responsibility for distributing your private root certificate to all clients who will connect to published applications using SSL. For UNIX ICA Clients, the root certificate must be exported to a DER-encoded file and saved with a .crt extension on the ICA Client workstation in the following directory: /usr/lib/ICAClient/keystore/cacerts  The 6.30 ICA Clients for UNIX-based operating systems create this directory during installation and populate it with the following well-known root certificates: | Filename | Certifying Authority | | BTCTRoot.crt | Baltimore CyberTrust Root | | Class3PCA_G2_v2.crt | VeriSign Trust Network | | Class4PCA_G2_v2.crt | VeriSign Trust Network | | GTECTGlobalRoot.crt | GTE CyberTrustGlobal Root | | GTECTRoot.crt | GTE CyberTrust Root | | Pcs3ss_v4.crt | VeriSign Class 3 Public Primary Certification Authority | | SecureServer.crt | RSA Data Security, Inc. Secure Server Certificateion Authority | To use a privately-issued certificate, you must add your CA root certificate to this list. The root certificate file... must end with the extension .crt, for example: myroot.crt may be DER-encoded or Base64 encoded, and must be readable by all users of the ICA Client (444 permissions) Example using Microsoft Certificate Services If your certificate authority is a Microsoft Windows server running Certificate Services, you would use the following procedure to place your root certificate on UNIX workstations running the ICA Client: 1. From a Windows machine running Internet Explorer, point your browser to http://your-certificate-server/certsrv/ and authenticate with your domain credentials. 2. Select Retrieve the CA certificate or certificate revocation list and click Next. 3. Keep the DER Encoded option chosen and click the link that reads Download CA certificate. You are prompted to save the file as certnew.cer. Save the file as myroot.crt instead. 4. Using FTP, NFS, Samba or any other means, copy the myroot.crt file to your UNIX workstation. Save the file as /usr/lib/ICAClient/keystore/cacerts/myroot.crt. 5. Your UNIX workstation should now be able to connect using SSL through CSG servers or SSL Relay Services which are using server certificates that were issued by your Microsoft Certificate Server. For more information please visit: Using Private SSL Certificates with the ICA Java Client and NFuse Classic 1.7 (CTX552703) Example: Deploying the cert via the web site       Key size Non-windows ICA clients connecting with SSL enabled are limited to public key sizes of 2048 bits or less. When connecting to a published application through Citrix Secure Gateway or the Citrix SSL Relay Service, non-Windows clients may receive an error such as the following (from the ICA Java client): There was a problem reading a security certificate. Check your certificate settings are correct. ICA-SSL connections to the same server succeed without issue when using the 32-bit Windows ICA client. Cause The cause of this error is a limitation in the size of public keys that may be used in CA certificates when making an ICA-SSL connection. While the Win32 ICA client is capable of connecting with CA key sizes of up to 4096 bits, non-Windows ICA clients permit a maximum key size of 2048 bits. To verify the key size in use by your SSL server, inspect the CA root certificate and any intermediate CA certificates in the certification path by double-clicking the certificate file. On the Details tab, locate the Public Key field. The number of bits shown should be shown in parentheses, for example: RSA (1024 bits) Resolution To resolve this issue, all certificates in the certificate path must be re-issued with public key sizes of 2048 bits or less. In order to use the Citrix ICA Client 6.20 for the Macintosh, it is first necessary to install it. The following instructions guide you through the process of installation, and then how to create a connection file used to establish connections with the server or farm. Begin the installation by either downloading the client from the Citrix website (recommended to ensure the most current release), or copy it from another source. Once the file is downloaded, Stuffit Expander will create a folder titled Citrix ICA Client 6.2. Open the Citrix ICA Client 6.2 folder.  1. Double-click on the program titled Installer to begin the installation procedure. When prompted, click CONTINUE.  2. Click Yes to accept the license agreement.  3. Determine which folder you will store the Citrix ICA Client into. In this example, the Citrix ICA Client will be stored in the Citrix ICA Client folder, within the Applications folder on the hard drive. The procedure to select this folder is as follows. Click the Select Folder option. Youll be presented with a folder browser window.  4. Select Applications, and then press the button labeled Select Applications.  5. Select the NEW folder button and create a folder named Citrix ICA Client. Click Create to make the new folder.   6. When you return to the Select the installation folder: dialog box, click Select Citrix ICA Client to continue.  7. You will now be returned to the main installer screen. Click Install to complete the installation.  8. After the file copy operation is complete, you should receive a message indicating such. Click Quit to finish and close the installer.  You have now successfully installed the Citrix ICA Client for the Macintosh. At this point, if you are using NFuse to deploy your applications, nothing further is required. If, however, you would like to use the traditional configuration method to access your Citrix Server farm, the following steps will guide you through creating a connection. Creating a connection to a Citrix server or server farm is very easy. The principal of the tools differs slightly from that of the Windows based client. To start with, the Citrix ICA Client for the Macintosh does not have Program Neighborhood functionality. Instead it is more of a fixed configuration using connection files to establish connections. If Program Neighborhood functionality is desired, it is recommended to use Citrix NFuse Classic or Elite to deliver the application set. However, it is still required that you install the client through the aforementioned series of steps. The following defines how to create a connection file in order to launch an ICA session. 1. To launch the Citrix ICA Client for the Macintosh and connect to a server, it is necessary to create a connection file first. To do this, navigate to the folder it was stored into during the installation. If you followed the aforementioned installation instructions, open your hard disk, then the Applications folder, followed by the Citrix ICA Client folder.  2. Launch the Citrix ICA Client Editor by double clicking on it. This will bring up a tool that will allow you to configure your connection, and then save the settings to a file that will launch a session.  3. The Network Connection property page allows you select a server or a published application, and optionally, your username, domain, and password. Depending on your situation, you may need to adjust your server location parameters in order to enumerate and connect to the Citrix server farm.  4. To change your Server Location values, click on the pull down list at the top of the page. Select Server Location.  5. The default settings are for TCP/IP+HTTP, or otherwise refered to as XML browsing. The default server for XML browsing is a DNS alias to your server farm named ICA. (however, it is not displayed. If either of these values needs to be adjusted, uncheck the Use Default option.  6. Once you have adjusted your Server Location settings, return to the Network Connection property page to select your server or published application. If your server location settings are correct, you should be able to click on the pull down list next to the Server: text box and enumerate your servers or published applications depending upon which radio button is selected.  7. When you have finished selecting the settings for your connection, click Save to store your connection parameters to a connection file. You will be prompted to select a location to save the settings to. In this example, the connection to the published application named Desktop is being saved as Desktop on the the Macintosh Desktop.  8. After saving your parameters, exit from the Citrix ICA Client Editor. You should now have a new icon on your desktop with the same name as was given in the previous step. Double click to launch a connection and test the configuration.  If you are able to connect, congratulations! You have finished installing and configuring the Citrix ICA Client for the Macintosh. For further instructions, details on the auxiliary utilities, and advanced configurations, refer to the Macintosh Client Admin Guide, available from the Citrix web site in the same location as the client download files. The recently released Citrix ICA Client 6.30 for OS 10.X is Citrixs first native 10.X Macintosh client. While it functions very similarly to the 6.20 client, both installation and configuration are slightly different. The first step to install the Citrix ICA Client 6.30 for the Macintosh is to aquire the appropriate archive. It is recommended to download the software directly from Citrix to ensure the most current release. If downloaded, the file will come as a disk image format, or referred to as a .dmg file.   1. Double click on the .dmg file to extract a disk image which is then mounted onto the desktop as an accessible drive as seen above. 2. The contents of the mounted drive will reveal a folder titled Citrix ICA Client. Copy this folder to your desired location. In the following image, the folder is copied into the Applications folder.   That concludes the installation procedure for the Citrix ICA Client for the Macintosh. It is safe to close the folders opened from the mounted drive, select the mounted drive icon, and from the pull down menu, select eject to dismount it. The .dmg file can be stored for future use, or eliminated if it is unneeded. The Citrix ICA Client for the Macintosh OS X functions on the same principal that the OS 9 compatible client version 6.2 operates. Both clients allow you to use the Citrix ICA Client Editor tool to create a connection file which, when executed, initiate a connection to the desired server using the Citrix ICA Client application. While they both operate similarly, the OS X Client Editor looks slightly different, but works much the same. 1. Begin configuring the connection to the Citrix server by opening the Citrix ICA Client folder, and launching the Citrix ICA Client Editor.  2. The editor can be seen below. The first page of the editor contains the server or published application name, as well as the Network Protocol settings used to connect with the application. This combined screen cuts down on time typically required to create a connection file.  3. After setting the Network Protocol options, if necessary, click on Browse to enumerate your servers or published applications.  4. Pick your desired server or published application. At this point, enough information has been configured to actually make a connection, however, we will go through the remaining screens to indicate where additional options can be configured. 5. Clicking on the Security tab you are presented with the following screen.  6. Here you can select your level of encryption, the address of a proxy server for client side connections through a compatible proxy server, and set the Firewall Settings for connecting to servers that traverse a server side firewall. (note that many of these features are new to the Citrix ICA Client for Macintosh in version 6.30)  7. In the Firewall Settings dialog box, you can change various settings such as the Use Alternate Address and the type of proxy server the client is connecting through. 8. Additionally, if your Macintosh client is connecting to a server secured by Citrix Secure Gateway services, you can configure the gateway address here. 9. The next tab, titled Connection Properties allows you to set features such as sound quality, compression, and resource mapping. It is here that you can modify Speedscreen Latency Reduction options.  10. The Window tab allows you to configure the window size, and number of colors.  11. When you are through selecting the options, you can either try connecting or saving your changes to a connection file. To connect, simply select Connect. Otherwise, select Save to store your options in a configuration file.  12. After providing a title for the connection file, select the destination. In the previous example, it is shown that the connection file will be titled Desktop and will be saved to the Desktop as seen below.  13. Double click on Desktop to launch a connection to the server. If you connect, Congratulations, you have successfully installed and configured the Citrix ICA Client 6.3 for the Macintosh. |