Publishing Terminal Server through IAG 2007 – Part 1 of 3

1. Growing the Application Portal


The Application Portal that we configured on the last three sessions will grow now. This fictitious company wants to publish their Terminal Server to the authorized users be able to access from anywhere.


This article will be split in two parts, where each part will cover the following topics:

·         Part 1 – Configuring the Terminal Server in the Application Portal and testing the client connectivity.

·         Part 2 – Creating a New Endpoint Policy and Customizing the Application.

·         Part 3 – Testing and Monitoring the Access


2. Non-Web in the Web


Non-Web applications will be able to take advantage of the IAG 2007 SSL VPN capabilities. Using a mechanism called SSL Wrapper, IAG 2007 allows you to publish applications that were not developed to work natively on the web. The process below will happen when the client workstation launches the TS Application through the Portal:


Figure 1 – Traffic will pass encrypted through the Internet.


There will be more details during the configuration; however the core idea of the SSL Wrapper is to allow non-web protocols to secure transit through the web.


3. Adding a New Application to the Portal


Open the HTTPS Portal and under the Applications follow the steps below:


1) Click in Add and the window below will appear:



Figure 2 – Choosing the application that you want to publish.


2) Select the Microsoft Windows XP Terminal Services Client as showed above and click in Next. The window below will appear:



Figure 3 – Choose a name for the application.


3) Leave the default option selected and chooses a name for the application, after that click in Next. The window below will appear:



Figure 4 – Configuring the Terminal Servers.


4) On this window you should double click and add the Terminal Servers. On the Port, make sure that you have the correct port that will connect internally to the TS Server (3389 by default). Select the screen resolution that you want to be configured by default on the client side and then click Next.



Figure 5 – Adding the link to the Portal.


5) On this window you can change the name for the application; this is the name that will appear in the Portal. Click in Finish to conclude.

After finishing the configuration, press CTRL + G to Activate the configuration.


4. Testing


To test this, go to the client workstation and try to access the application portal. You will notice that the following window will appear if you click in the Details link:



Figure 6 – Error message that will appear if your computer is not compliant with the security policy.


Since on the step two we kept the default access policy we are facing this problem if the computer that is trying to access the portal is not complaint with this policy. The Terminal Server’s link is grayout and the details link explains clearly why we are unable to access it.


Next session we will understand how to create a new policy and customize the application.



Comments (0)

Skip to main content