The Private Cloud Man

Private Cloud Technologies, Architecture and more!

Test Lab Guide: Demonstrate Forefront UAG SP1 RC DirectAccess with Secure Socket Tunneling Protocol (SSTP) and Remote Desktop Gateway (RDG)–Blog Version

Test Lab Guide: Demonstrate Forefront UAG SP1 RC DirectAccess with Secure Socket Tunneling Protocol (SSTP) and Remote Desktop Gateway (RDG)–Blog Version

  • Comments 1
  • Likes

Hey folks – since the TLGs are typically put up only in the download center, it makes discoverability of some of the cool content inside of them hard when it comes to search engines. Therefore, I’m going to post the full text of the TLGs on the Edge Man blog. However, I recommend that you download the Word .doc version of the TLGs when you actually put together your Test Lab using the Test Lab Guides.

For a downloadable version of the Test Lab Guide – Demonstrate UAG SP1 RC DirectAccess with Secure Socket Tunneling Protocol (SSTP) and Remote Desktop Gateway (RDG) check out:

http://go.microsoft.com/fwlink/?LinkId=206505

==================================================

Introduction

DirectAccess is a new feature in the Windows 7 and Windows Server 2008 R2 operating systems that gives users the experience of being seamlessly connected to their intranet any time they have Internet access. With DirectAccess enabled, requests for intranet resources (such as e-mail servers, shared folders, or intranet Web sites) are securely directed to the intranet, without requiring users to connect to a VPN. DirectAccess provides increased productivity for a mobile workforce by offering the same connectivity experience both inside and outside the office.

Forefront Unified Access Gateway (UAG) SP1 RC extends the value of the Windows DirectAccess solution by adding features that meet the requirements of many enterprise deployments:

  • Support for arrays of up to 8 UAG DirectAccess servers where configuration is done once on an array master and is automatically deployed to all other members of the array
  • Support for Network Load Balancing, which enables the UAG DirectAccess SP1 RC array to be highly available without requiring the use of an external hardware load balancer
  • Support for IPv4-only networks, network segments, or server or application resources with the help of NAT64/DNS64 IPv6/IPv4 transition technologies.

To learn more about UAG DirectAccess, see the following resources:

· Forefront UAG DirectAccess Design Guide

· Forefront UAG DirectAccess Deployment Guide

UAG SP1 RC supports hosting multiple roles on a single UAG server or UAG array. For example, you might want to host both the DirectAccess server and SSTP VPN server roles on the same server or array. Windows 7 clients that are configured DirectAccess clients will automatically use DirectAccess to connect to intranet resources. Windows 7 clients that are not domain members, or who are not configured as DirectAccess clients can use SSTP to connect to the intranet using a network level VPN connection. Windows 7, Windows Vista and Windows XP clients can connect to Remote Desktop and RemoteApps through a UAG server that is configured to host the Remote Desktop Gateway role. In this guide, we demonstrate how a UAG server can support the combined, DirectAccess, SSTP and Remote Desktop Gateway server roles.

In this guide

This guide provides step-by-step instructions for configuring UAG DirectAccess SP1 RC with SSTP and Remote Desktop Gateway in a test lab so that you can see how it works. You will set up and deploy UAG DirectAccess SP1 RC using five server computers, two client computers, Windows Server 2008 R2 Enterprise edition, and Windows 7 Ultimate Edition. The Test Lab simulates intranet, Internet, and a home networks, and demonstrates a co-located Forefront UAG DirectAccess and SSTP VPN server role deployment. The starting point for this paper is the Test Lab Guide: Demonstrate UAG SP1 RC DirectAccess .

clip_image001Important:

These instructions are designed for configuring a test lab using the minimum number of computers. Individual computers are needed to separate the services provided on the network, and to show clearly the required functionality. This configuration is not designed to reflect best practices, nor does it reflect a required or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed to work only on a separate test lab network. For more information on planning and deploying DirectAccess with Forefront UAG, please see the Forefront UAG DirectAccess design guide and the Forefront UAG DirectAccess deployment guide

Overview of the test lab scenario

In this test lab scenario, Forefront UAG DirectAccess SP1 RC is deployed with:

  • One computer running Windows Server 2008 R2 Enterprise Edition (DC1), that is configured as an intranet domain controller, Domain Name System (DNS) server, Dynamic Host Configuration Protocol (DHCP) server, and an enterprise root certification authority (CA).
  • One intranet member server running Windows Server 2008 R2 Enterprise Edition (UAG1), that is configured as a Forefront UAG SP1 RC DirectAccess, SSTP VPN and Remote Desktop Gateway server.
  • One intranet member server running Windows Server 2008 R2 Enterprise Edition (APP1) that is configured as a general application server and network location server.
  • One intranet member server running Windows Server 2003 SP2 (APP3) that is configured as an IPv4 only web and file server. This server is used to highlight the UAG’s NAT64/DNS64 capabilities.
  • One standalone server running Windows Server 2008 R2 Enterprise Edition (INET1) that is configured as an Internet DNS and DHCP server.
  • One standalone client computer running Windows 7 Ultimate Edition (NAT1), that is configured as a network address translator (NAT) device using Internet Connection Sharing.
  • One roaming domain member client computer running Windows 7 Ultimate Edition (CLIENT1) that is configured as a DirectAccess client.

The test lab consists of three subnets that simulate the following:

  • A home network named Homenet (192.168.137.0/24) connected to the Internet subnet by NAT1.
  • The Internet subnet (131.107.0.0/24).
  • The Corpnet subnet (10.0.0.0/24) separated from the Internet by the Forefront UAG DirectAccess server.

Computers on each subnet connect using either a physical or virtual hub or switch, as shown in the following figure.

clip_image003

Configuration component requirements

The following components are required for configuring Forefront UAG DirectAccess in the test lab:

  • The product disc or files for Windows Server 2008 R2 Enterprise Edition.
  • The product disc or files for Windows Server 2003 Enterprise SP2
  • The product disc or files for of Windows 7 Ultimate.
  • Five computers or virtual machines that meet the minimum hardware requirements for Windows Server 2008 R2 Enterprise; two of these computers has two network adapters installed (UAG1).
  • One computer or virtual machine that meets the minimum hardware requirements for Windows Server 2003 SP2
  • Two computers or virtual machines that meet the minimum hardware requirements for Windows 7 Ultimate; one of these computers has two network adapters installed (NAT1).
  • The product disc or a downloaded version of Microsoft Forefront Unified Access Gateway (UAG) SP1 RC.

This Test Lab Guide demonstrates a combined UAG SP1 RC DirectAccess and SSTP deployment.

clip_image004Important

The following instructions are for configuring a test lab using the minimum number of computers. Individual computers are needed to separate the services provided on the network and to clearly show the desired functionality. It is important to remember that this configuration is neither designed to reflect best practices nor does it reflect a desired or recommended configuration for a production network. The configuration, including IP addresses and all other configuration parameters, is designed only to work on a separate test lab network.

Attempting to adapt this test lab configuration to a pilot or production deployment can result in configuration or functionality issues. To ensure proper configuration and operation of UAG DirectAccess and SSTP, please refer to the Forefront UAG DirectAccess Deployment Guide for the steps to configure the UAG DirectAccess server and supporting infrastructure servers.

Steps for configuring the test lab

The following sections describe how to configure UAG1 as a DirectAccess, SSTP VPN and Remote Desktop Gateway server. After UAG1 is configured, this guide provides steps for demonstrating the DirectAccess, SSTP VPN and Remote Desktop Server functionality for CLIENT1 when it is connected to the Homenet subnet.

clip_image005Note

You must be logged on as a member of the Domain Admins group or a member of the Administrators group on each computer to complete the tasks described in this guide. If you cannot complete a task while you are logged on with an account that is a member of the Administrators group, try performing the task while you are logged on with an account that is a member of the Domain Admins group. For all tasks described in this document you can use the CONTOSO\User1 account created when you went through the steps in the UAG DirectAccess Test Lab Guide: Demonstrate UAG SP1 RC DirectAccess.

The following procedures are performed to enable and allow you to test the UAG SP1 RC DCA:

· Step 1: Complete the Demonstrate UAG SP1 RC DirectAccess with SSTP Test Lab Guide – The first step is to complete all the steps in the Test Lab Guide: Demonstrate Forefront UAG SP1 RC DirectAccess with Secure Socket Tunneling Protocol (SSTP).

· Step 2: Install and Configure the RDS Session Host on APP1. In order to test UAG1 publishing of Remote Desktops and RemoteApps we need an RDS Session Host server on the corpnet subnet. In this step you will install the RDS Session Host Role on APP1.

· Step 3: Generate the RemoteApp Configuration File on APP1. You will publish a RemoteApp on UAG1. In order to publish the RemoteApp, you need to generate a RemoteApp configuration file on APP1. In this step you will generate the RemoteApp configuration file and copy it to UAG1.

· Step 4: Publish Remote Desktops on UAG1. To publish Remote Desktops you need to add the Remote Desktops Application to the portal. In this step you will add the Remote Desktop applications to the UAG1 portal page.

· Step 5: Publish RemoteApps on UAG1. To publish RemoteApps you need to add the RemoteApps application to the portal. In this step you will add the RemoteApps application to the portal page.

· Step 6: Test DirectAccess, SSTP and Remote Desktop Connectivity from CLIENT1. After the portal configuration is completed, you can test connectivity to resources through the UAG portal. In this step you will confirm DirectAccess and SSTP connectivity, and test Remote Desktop and RemoteApp connectivity through the portal.

· Step 7: Snapshot the configuration. After completing the Test Lab, take a snapshot of the working UAG DirectAccess, SSTP and Remote Desktop Gateway Test Lab so that you can return to it later to test additional scenarios.

clip_image005[1]Note

You will notice that there are several steps that begin with an asterisk (*). The * indicates that the step requires that you move to a computer or virtual machine that is different from the computer or virtual machine you were at when you completed the previous step.

STEP 1: Complete the Demonstrate UAG SP1 RC DirectAccess with SSTP Test Lab Guide

The first step is to complete all the steps in the Test Lab Guide: Demonstrate Forefront UAG SP1 RC DirectAccess with Secure Socket Tunneling Protocol (SSTP). After completing the steps in that Test Lab Guide you will have the core infrastructure required to complete this Test Lab Guide on how to configure UAG DirectAccess with SSTP and RDG. If you have already completed the steps in that Test Lab Guide and saved a snapshot or disk image of the Test Lab, you can restore the snapshot or image and begin with the next step.

STEP 2: Install and Configure the RDS Session Host on APP1

In order to test UAG1 publishing of Remote Desktops and RemoteApps we need an RDS Session Host server on the corpnet subnet. In this step you will install and configure the RDS Session Host Role on APP1.

Install the RDS Session Host on APP1:

  1. At the APP1 computer or virtual machine, log on as CORP\User1. Open the Server Manager. In the left pane of the Server Manager console, click the Roles node. In the right pane of the console, click Add Roles.
  2. On the Before You Begin page, click Next.
  3. On the Select Server Roles page, select Remote Desktop Services and click Next.
  4. On the Introduction to Remote Desktop Services page, click Next.
  5. On the Role Services page, select Remote Desktop Session Host and click Next.
  6. On the Application Compatibility page, click Next.
  7. On the Authentication Method page, select Require Network Level Authentication and click Next.
  8. On the Licensing Mode page, select Configure later and click Next.
  9. On the User Groups page, confirm Administrators is in the User or User Groups list and click Next.
  10. On the Client Experience page, put a checkmark in the Audio and video playback, Audio recording redirection, and Desktop composition (provides the user interface elements of Windows Aero) checkboxes and click Next.
  11. On the Confirmation page, click Install. When you see the message Restart Pending, click Close. In the Add Roles Wizard dialog box, click Yes. The machine will restart to complete installation. Log on as CORP\User1. After you log on the installation will continue. On the Results page, click Close.

Configure the RDS Session Host on APP1:

  1. Click Start and point to Administrative Tools. Point to Remote Desktop Services and click Remote Desktop Session Host Configuration.
  2. In the Remote Desktop Session Host Configuration console, in the right pane of the console, right click RDP-Tcp and click Properties.
  3. In the RDP-Tcp Properties dialog box, on the General tab, click the Select button. In the Windows Security dialog box, click APP1.corp.contoso.com and click OK. In the RDP-Tcp Properties dialog box, click OK.
  4. Close the Remote Desktop Session Host Configuration console.

STEP 3: Generate the RemoteApp Configuration File on APP1

You will publish a RemoteApp on UAG1. In order to publish the RemoteApp, you need to generate a RemoteApp configuration file on APP1. In this step you will generate the RemoteApp configuration file and copy it to UAG1.

  1. Click Start and point to Administrative Tools. Point to Remote Desktop Services and click RemoteApp Manager.
  2. In the RemoteApp Manager console, in the Actions pane, click Add RemoteApp Program.
  3. On the Welcome to the RemoteApp Wizard page, click Next.
  4. On the Choose programs to add to the RemoteApp Programs list page, select WordPad and click Next.
  5. On the Review Settings page, click Finish.
  6. In the Actions pane, click Export RemoteApp Settings.
  7. In the Export RemoteApp Settings dialog box, select Export the RemoteApp Programs list and settings to a file and click OK.
  8. In the Save As dialog box, in the File name text box, enter WordPadRemoteApp and save the file to the C:\Files folder. In the RemoteApp Manager dialog box click OK. Close the RemoteApp Manager console.
  9. *Log on to the UAG1 computer or virtual machine as CORP\User1. Click Start and in the Search box enter \\APP1\Files and press ENTER. Copy the WordPadRemoteApp.tspub file to the desktop on UAG1. Close the Windows Explorer window.

STEP 4: Publish Remote Desktops on UAG1

To publish Remote Desktops you need to add the Remote Desktops Application to the portal. In this step you will add the Remote Desktop application to the UAG1 portal page.

  1. At the UAG1 computer or virtual machine, click Start and then click All Programs. Click Microsoft Forefront UAG and then click Forefront UAG Management. In the User Account Control dialog box, click Yes.
  2. In the left pane of the Microsoft forefront Unified Access Gateway Management console, expand HTTPS Connections and click on HTTPSTrunk. In the right pane of the console, in the Applications section, click Add.
  3. On the Welcome to the Add Application Wizard page, click Next.
  4. On the Step 1 – Select Application page, select the Terminal Services (TS)/Remote Desktop Services (RDS) option. From the drop down box, select Remote Desktop (Predefined). Click Next.
  5. On the Step 2 – Configuration Application page, in the Application name text box, enter Predefined Remote Desktop. Click Next.
  6. On the Step 3 – Select Endpoint Policies page, from the Access policy drop down list, select Always. We select Always in this lab because the default policy requires that the client system have antivirus software installed in order to launch the application. CLIENT1 does not have antivirus software installed, so we need to select the Always option for the Test lab. Click Next.
  7. On the Step 4 – Configure Server Settings page, in the UAG SP1 RC Session Host (IP address or FQDN) text box, enter app1.corp.contoso.com. Click Next.
  8. On the Step 5 – Configure Client Settings page, accept the default settings and click Next.
  9. On the Step 6 – Portal Link page, accept the default settings and click Next.
  10. On the Step 7 – Authorization page, accept the default settings and click Next.
  11. On the Completing the Add Application Wizard page, click Finish.

STEP 5: Publish RemoteApps on UAG1

To publish RemoteApps you need to add the RemoteApps application to the portal. In this step you will add the RemoteApps application to the portal page.

  1. In the right pane of the Microsoft Forefront Unified Access Gateway Management console, in the Applications section, click the Add button.
  2. On the Welcome to the Add Application Wizard page, click Next.
  3. On the Step 1 – Select Application page, select the Terminal Services (TS)/Remote Desktop Services (RDS) option. From the drop down box, select RemoteApp. Click Next.
  4. On the Step 2 – Configuration Application page, in the Application name text box, enter Remote WordPad. Click Next.
  5. On the Step 3 – Select Endpoint Policies page, from the Access policy drop down box, select Always. Click Next.
  6. On the Step 4 – Import RemoteApp Programs page, click the Browse button. Navigate to the Desktop and open the WordPadRemoteApp.tspub file. In the UAG SP1 RC Session Host (IP address or FQDN) text box, confirm that it says APP1.corp.contoso.com. Click Next.
  7. On the Step 5 – Select Publishing Type page, in the Available RemoteApps section, select
    WordPad
    and click the right-pointing double-arrow. This moves the WordPad application to the Published RemoteApps section. Click Next.
  8. On the Step – 6 Configure Client Settings page, accept the default settings and click Next.
  9. On the Step – 7 Portal Link page, accept the default settings and click Next.
  10. On the Step 8 – Authorization page, accept the default settings and click Next.
  11. On the Completing the Add Application Wizard page, click Finish.
  12. Click the File menu and click Activate.
  13. On the Activate Configuration page, click the Activate button.
  14. Click Finish on the Activation completed successfully page.

STEP 6: Test DirectAccess, SSTP and Remote Desktop Connectivity from CLIENT1

After the portal configuration is completed, you can test connectivity to resources through the UAG portal. In this step you will confirm DirectAccess and SSTP connectivity, and then test Remote Desktop and RemoteApp connectivity through the portal.

Confirm DirectAccess Connectivity to the Corpnet subnet:

  1. *Move the CLIENT1 computer or virtual machine to the Homenet subnet. Log on to CLIENT1 as CORP\User1.
  2. Open an elevated command prompt. In the command prompt window, enter ping dc1 and press ENTER. You should see four responses from DC1. This indicates that the IPv6 transition technology that connects CLIENT1 to UAG1 is working correctly.
  3. In the command prompt window, enter net view \\dc1 and press ENTER. You should see a list of shares on DC1. This indicates that the infrastructure tunnel is working correctly.
  4. In the command prompt window, enter net view \\app1 and press ENTER. You should see a list of shares on APP1. This indicates that the intranet tunnel is working correctly.
  5. You have demonstrated that DirectAccess connectivity is successful over both the intranet and infrastructure tunnels. Close the command prompt window.

Confirm SSTP Connectivity to the Corpnet subnet:

  1. On the CLIENT1 computer or virtual machine, open Internet Explorer. In Internet Explorer, in the address bar, enter https://uag1.contoso.com and press ENTER. Click the information bar that informs you that the Website wants to run the following add-on: Microsoft Remote Desktop Services Web Access Con…” from “Microsoft Corporation:… click Run Add-on. In the Internet Explorer – Security Warning dialog box that asks Do you want to run this ActiveX control? click Run.
  2. Enter the username and password for CORP\User1 in the Application and Network Access Portal page. If the page times out and you see a message that says The logon process cannot be completed. User credentials were not submitted within the time limit, click the Back link and log on as CORP\User1.
  3. In the right pane of the portal page, click SSTP VPN. After you see the balloon in the system notification area that says that network connectivity is started, open an elevated command prompt.
  4. In the command prompt window, enter ping APP3 and press ENTER. You should see four responses from the IPv4 address of APP3. This indicates that DirectAccess has been disabled and the IPv4 SSTP connection to the Corpnet subnet is active. Close the elevated command prompt window.
  5. Right click the Remote Network Access icon in the system notification area and click Disconnect remote Network Access command. You will see a balloon in the system notification area that says that the connection is ended.

Confirm Remote Desktop Connectivity to the Corpnet subnet:

  1. In the right pane of the portal page, click the Predefined Remote Desktop link. If the Message from webpage dialog box appears, click OK. If the Information bar appears saying that the website wants to run Remote Desktop Services ActiveX Client, click the information bar and click Run Add-on. In the Internet Explorer – Security Warning dialog box, click Run.
  2. Click the Predefined Remote Desktop link in the right pane of the portal page. In the Remote Desktop Connection dialog box, click Connect. In the Windows Security dialog box, enter credentials for CORP\User1. .
  3. The Desktop now appears in the RDC client window. Close the RDC window. In the Remote Desktop Connection dialog box, click OK.

Confirm RemoteApp Connectivity to the Corpnet subnet:

  1. In the right pane of the portal, click the WordPad link.
  2. In the RemoteApp dialog box, click Connect.
  3. In the Document – WordPad window, enter This is a RemoteApp document. Click the Save icon in the Title Bar, and save the document to the desktop with the name My RemoteApp Doc. Close the WordPad window.
  4. Click the Log Off button in the upper right corner of the portal page. Close Internet Explorer.

STEP 7: Snapshot the Configuration

This completes the UAG SP1 RC DirectAccess with SSTP and Remote Desktop Gateway test lab. To save this configuration so that you can quickly return to a working UAG SP1 RC DirectAccess with SSTP and Remote Desktop Gateway configuration from which you can test other DirectAccess modular TLGs, TLG extensions, or for your own experimentation and learning, do the following:

  1. On all physical computers or virtual machines in the test lab, close all windows and then perform a graceful shutdown.
  2. If your lab is based on virtual machines, save a snapshot of each virtual machine and name the snapshots TLG UAG DirectAccess SP1RC SSTP+RDG. If your lab uses physical computers, create disk images to save the DirectAccess test lab configuration.

Additional Resources

For more information on UAG and SSTP, see Setting up Remote Network Access.

For more information on UAG and Remote Desktop Gateway, see Remote Desktop Services publishing solution guide.

For procedures to configure the Base Configuration test lab on which this document is based, see the Test Lab Guide: Base Configuration.

For procedures to configure UAG SP1 RC DirectAccess on which this document is based, see the Test Lab Guide: Demonstrate Forefront UAG SP1 RC DirectAccess.

For procedures to configure UAG SP1 RC DirectAccess on which this document is based, see Test Lab Guide: Demonstrate Forefront UAG SP1 RC DirectAccess with Secure Socket Tunneling Protocol (SSTP)

For a comprehensive list of Test Lab Guides, please see Test Lab Guides.

For a list of UAG DirectAccess related Test Lab Guides, please see UAG DirectAccess Test Lab Guide Portal Page

For the design and configuration of your pilot or production deployment of DirectAccess, see the Forefront UAG DirectAccess design guide and the Forefront UAG DirectAccess deployment guide.

For information about troubleshooting DirectAccess, see the DirectAccess Troubleshooting Guide.

For information on troubleshooting UAG DirectAccess in a Test Lab, see Test Lab Guide: Troubleshooting UAG DirectAccess.

For more information about DirectAccess, see the DirectAccess Getting Started Web page and the DirectAccess TechNet Web page.

==================================================

Tom Shinder
tomsh@microsoft.com
Knowledge Engineer, Microsoft DAIP iX/Forefront iX 
UAG Direct Access/Anywhere Access Group (AAG)
The “Edge Man” blog (DA all the time):
http://blogs.technet.com/tomshinder/default.aspx
Follow me on Twitter:
http://twitter.com/tshinder
Facebook:
http://www.facebook.com/tshinder

Comments
  • Hi dear how are you m sam parker. i read yourblog. very first thing is that the design of your blog is very good i like that. m also working on that type of sites <a href="www.labtestportal.com/"> blood testing  </a>

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment