How To: Install and Configure Citrix Web Interface 4.6 and Citrix Secure Gateway on the same server
[LEFT][CODE]http://www.virtualizationadmin.com/articles-tutorials/terminal-services/general/install-configure-citrix-web-interface-secure-gateway-part1.html[/CODE]
[SIZE=3][B]
PART-1[/B][/SIZE]
[B]Introduction[/B]
Citrix Web Interface 4.6 is an ASP.Net 2.0 application that provides access to Citrix Published Applications via a web browser. When deployed by itself, Internet Based users require direct ICA (TCP Port 1494) or Common Gateway Protocol (TCP Port 2598) Communication with each Citrix Server hosting their published applications. Since this involves allowing secure communications from the Public Internet into the Private Network and opening firewall ports. Additionally it requires that the client can successfully communicate over ports 1494 or 2598.
Citrix Secure Gateway 3.0 (CSG) is a Reverse Proxy that provides secure remote access to Citrix Published Applications over SSL (TCP Port 443). When deployed in a DMZ it solves the security and access problems previously listed, i.e. the client only needs to be able to contact the CSG over port 443 and the CSG communicates on behalf of the clients with the Citrix Servers on the Private Network. No communication happens between the Public Internet and Private/Corporate Network.
Both Citrix Web Interface and Secure Gateway are available to Citrix Presentation Server Customers via [URL="http://www.mycitrix.com/"]http://www.mycitrix.com[/URL].
[B]Software pre-requisites (for the machine to host Web Interface 4.6 and Secure Gateway 3.0):[/B]
[LIST=1][*]Windows Server OS, i.e. 2003 Web or 2003 Standard Edition.[*]IIS w/ ASP.Net[*]Net Framework 2.0[*]Microsoft Visual J# Version 2.0 Redistributable Package[*]Access Management Console for Presentation Server 4.5 (Framework only)[*]Web Interface 4.6 Access Management Console Extension[*]3rd Party SSL Server Certificate (i.e. from Verisign, Thawte, GeoTrust, GoDaddy...)[/LIST]
[B]Hardware Requirements:[/B]
[LIST=1][*]Server capable of running Windows Server OS w/ IIS[*]Firewall with DMZ an available DMZ Port[/LIST]
[B]Web Interface 4.6 for Windows - Installation and Configuration[/B]
The initial installation and configuration of the Web Interface / Secure Gateway Server should be performed on the Private Network, to ensure that all components are working properly before moving the server to the DMZ. Since the server’s final destination is in the DMZ, the server should NOT be a domain member.
After installing software pre-requisites 1 through 6, download and launch the Web Interface installation program (WebInterface.exe). Install Web Interface and accept the defaults.
Download the Citrix Web Client and place ica32web.msi in “[B]C:\Program Files\Citrix\Web Interface\4.6\Clients\ica32\[/B]”.
Download the Citrix Java Client and place the components in “[B]C:\Program Files\Citrix\Web Interface\4.6\Clients\icajava\[/B]”.
Launch the Access Management Console (AMC). The first time the AMC is run, discovery is performed to identify the components that will be managed.
[IMG]http://www.msterminalservices.org/img/upl/image0021189598036470.jpg[/IMG]
Select the option, “Do not contact servers running the configuration service”, unless you want to centrally store the Web Interface Configuration (refer to the Web Interface Administrators Guide).
[IMG]http://www.msterminalservices.org/img/upl/image0041189598271876.jpg[/IMG]
After the discovery process completes, right click on the Web Interface node on the left pane of the [B]AMC -> Select “Create Site”[/B].
[IMG]http://www.msterminalservices.org/img/upl/image0061189598271876.jpg[/IMG]
Select the default option for Site Type (Access Platform Site).
[IMG]http://www.msterminalservices.org/img/upl/image0081189598271876.jpg[/IMG]
On the Specify IIS Location step of the site creation, check the option “Set as the default page for the IIS site”. Accept the defaults for the rest of the Create Site process.
[IMG]http://www.msterminalservices.org/img/upl/image0091189598271892.jpg[/IMG]
After the site is created, the initial settings must be configured. On this screen, enter the name of the Citrix Farm, then enter at least one server from the Citrix Farm with which the Web Interface will communicate. The Web Interface communicates with the XML Service on the configured Citrix Server via the Farm XML Port (80 is the default). Refer to the Citrix Server Farm Properties in the Presentation Server Console if unsure what port number to enter.
Best practice would be to enter at least two XML Servers (for redundancy) and to enter Citrix Servers configured as Data Collectors. When a user enters their credentials to log on to the Web Interface, the Web Interface communicates with the XML Service to authenticate the user and return the Application Set for that user.
XML Servers can be entered as their NetBIOS, FQDN or IP Address, depending on which name resolution mechanism is in place. Since the server will end up in the DMZ, entering the IP Address requires the fewest open ports (between the DMZ and Private Network).
[IMG]http://www.msterminalservices.org/img/upl/image0101189598524595.jpg[/IMG]
On the “Select Application Type” screen, select “Remote”, unless you plan to use the Presentation Server 4.5 Application Streaming Feature to stream applications to client computers. Accept the defaults for the remainder of the Initial Configuration Wizard.
[IMG]http://www.msterminalservices.org/img/upl/image0111189598524595.jpg[/IMG]
At this point the Citrix Web Interface is ready to be tested, to ensure that it’s been configured correctly. To test that the Web Interface is working, open Internet Explorer on the Web Interface Server and browse to [U][url]http://localhost[/url][/U]. Without any further configuration, one should be able to successfully log on and launch applications from the configured Citrix Farm.
[IMG]http://www.msterminalservices.org/img/upl/image0131189598524595.jpg[/IMG]
After successfully entering logon credentials, one should be presented with the following Citrix Client Detection Wizard (if no Citrix Client is installed).
[IMG]http://www.msterminalservices.org/img/upl/image0151189598524610.jpg[/IMG]
Clicking the “Detect Client” button initiates a scan to check the client computer for an installed Citrix Client. If no client is detected, the user is presented with the following screen where the Citrix Web Client installation can be started.
[IMG]http://www.msterminalservices.org/img/upl/image0171189598524610.jpg[/IMG]
If the end user clicks the “Download” button, the Citrix Web Client installation package is loaded from “C:\Program Files\Citrix\Web Interface\4.6\Clients\ica32\ica32web.msi” on the Web Interface Server.
[IMG]http://www.msterminalservices.org/img/upl/image0191189598881470.jpg[/IMG]
Click “Run” and proceed with the Client Installation. After the installation is complete, the end user is presented with the following screen.
[IMG]http://www.msterminalservices.org/img/upl/image0211189598881485.jpg[/IMG]
Click “Successful” to be taken to the client’s application set.
[IMG]http://www.msterminalservices.org/img/upl/image0231189598881485.jpg[/IMG]
Click on one of the applications. If the application launches, the basic configuration of Citrix Web Interface was successful. The next step is to obtain an SSL Server Certificate which will be used by Citrix Secure Gateway.
[B]SSL Server Certificate Configuration[/B]
Since Citrix Secure Gateway is used to provide secure remote access, a Trusted 3rd Party SSL Server Certificate is required. To obtain the certificate, launch Computer Management and navigate to Services and Applications -> Internet Information Services (IIS) Manager -> Web Sites -> Default Web Site -> Properties -> Directory Security.
[IMG]http://www.msterminalservices.org/img/upl/image0241189598881485.jpg[/IMG]
Click on the “Server Certificate” button to start the “Web Server Certificate Wizard”. Select “Next -> Create a new certificate -> Prepare the request now, but send it later.
[IMG]http://www.msterminalservices.org/img/upl/image0251189598881485.jpg[/IMG]
In the name field, enter a friendly name that accurately describes what the certificate will be used for, i.e. “Citrix Secure Gateway”. Click Next.
[IMG]http://www.msterminalservices.org/img/upl/image0261189598913360.jpg[/IMG]
The information on the Organization Information page is what will display on the SSL Certificate when viewed by the end user.
[IMG]http://www.msterminalservices.org/img/upl/image0271189598913376.jpg[/IMG]
The Site Common Name is the most important piece of information that is entered. It MUST match the Fully Qualified Domain Name that will be addressed by the end user. It need not be the same as the NetBIOS Name of the Server, but DNS must be configured to resolve this name to the server being configured.
[IMG]http://www.msterminalservices.org/img/upl/image0281189599381142.jpg[/IMG]
On the Geographical Information Screen it is important that the “State/province” be completely spelled, as the request will not be accepted by the 3rd Party Certificate Authority if the State/province is abbreviated.
[IMG]http://www.msterminalservices.org/img/upl/image0291189599381142.jpg[/IMG]
The information entered in the IIS Certificate Wizard outputs to a text file, whose content is submitted to the 3rd Party Certificate Authority via their online certificate purchase form.
[IMG]http://www.msterminalservices.org/img/upl/image0301189599381142.jpg[/IMG]
After purchasing the SSL Server Certificate from your preferred Certificate Authority, the Certificate needs to be installed on the Web Interface / Secure Gateway Server. The following steps may differ slightly, depending on the vendor, but in this example we’ll use certificates from GoDaddy.com. GoDaddy supplies two certificates, an Intermediate Certificate Authority and the SSL Server Certificate that was purchased. Per the instructions from the vendor we open the Certificates Management Console via Start -> Run -> MMC -> File -> Add/Remove Snap-in -> Add -> Certificates -> Add -> Computer Account -> Next -> Local Computer -> Finish.
[IMG]http://www.msterminalservices.org/img/upl/image0321189599381157.jpg[/IMG]
Right click on the “Intermediate Certification Authorities”, navigate to All Tasks -> Import -> Browse and select the Root Certificate supplied by the vendor.
[IMG]http://www.msterminalservices.org/img/upl/image0331189599439345.jpg[/IMG]
Click Next and Accept the Default Location of Intermediate Certification Authorities.
[IMG]http://www.msterminalservices.org/img/upl/image0341189599439345.jpg[/IMG]
Click Next to Complete the Certificate Import.
[B] [IMG]http://www.virtualizationadmin.com/img/upl/image0401191847193595.jpg[/IMG][/B]
Open IIS Manager -> Web Sites -> Default Web Site -> Properties -> Directory Security -> Server Certificate.
[IMG]http://www.virtualizationadmin.com/img/upl/image0411191847193642.jpg[/IMG]
Click “Next” to continue with the Web Server Certificate Wizard.
[IMG]http://www.virtualizationadmin.com/img/upl/image0421191847193673.jpg[/IMG]
Select “Process the pending request and install the certificate”. Click “Next” to continue.
[IMG]http://www.virtualizationadmin.com/img/upl/image0431191847193673.jpg[/IMG]
Browse to, or enter the path to the downloaded SSL Server Certificate. Click “Next” to continue.
[IMG]http://www.virtualizationadmin.com/img/upl/image0441191847193689.jpg[/IMG]
Change the “SSL port this web site should use” from 443, to 444 or another unused port. It is very important NOT to accept the default port of 443, as this port will be used by Citrix Secure Gateway.
To test that the SSL Certificate has been properly installed and that IIS has been configured correctly, restart IIS via “Start -> Run -> cmd -> IISRESET”. After IIS restarts, browse to [U][url]https://FullyQualifiedDomainName:444[/url][/U]. This is NOT the URL clients will enter, as they will connect to the Citrix Secure Gateway on the standard HTTPS Port (443). This is only being done to ensure that the certificate was properly installed and that the Citrix Web Interface still works. A DNS Host (A) or Alias (Cname) record must be configured to resolve the Fully Qualified Domain Name to the IP Address of the server being configured for the web page to display correctly.
In part two of this article we’ll go over the installation and configuration of Citrix Secure Gateway, as well as the required firewall configuration
[/LEFT]
