| Now that you have implemented a SSL certificate, you will want to force users to use SSL encryption for the Web Interface portal. At the same time, you will be creating a friendlier name for the end-users to browse too (i.e., http://www.mycompany.com/portal). The following procedures document how to force the use of SSL on the Web Interface web site without forcing the end-users from being required to enter https// prior to entering the web address. 1. Browse to the root of the default web site and create a folder with the name of the portal. Make the name something that end-users will remember because it will be used on a daily basis. 2. Click Start Run type: notepad and click OK 3. Type the following: 
4. Save the file as default.asp in the folder you created in step 1. i.e., c:\inetpub\wwwroot\portal 5. Click Start Programs Administrative Tools Internet Services Manager Browse to the original (top level) Web Interface web site and right click on it and select Properties 
6. Click on the Directory Security tab and then click the Edit button. 
7. Click to check the Require secure channel (SSL) checkbox and then click the select the Require 128-bt encryption checkbox.. Click OK 
You are now ready to inststuct your end-users to browse the folder you created in step 1 and they will automaticly be redirected to the Web Interface web site using SSL. With Secure Gateway for MetaFrame (SG) administrators can supply a secure any device, any connection, any where solution to their end-users. In the design phase of the project you would have defined if you will be installing SG and on which servers. In this section you will learn how to install a basic Secure Gateway for MetaFrame solution to allow secure connections to MetaFrame XP and MetaFrame Secure Access Manager farms. |