Steps for configuring the test lab

  • Article

Applies To: Unified Access Gateway

The following steps describe how to configure the server and client computers, and configure the Forefront UAG DirectAccess server, in a test lab. Following these configurations you can verify DirectAccess connectivity from the Internet and Homenet subnets.

Note

You must be logged on as a member of the Domain Admins group or as 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.

  1. Step 1: Configure DC1—DC1 is the domain controller, network location server (NLS), Certificate server, DNS server, File Server and DHCP server for the corp.contoso.com domain.

  2. Step 2: Configure APP1—APP1 is a Windows Server 2008 R2 computer that acts in the role of the network location server on the network.

  3. Step 3: Configure APP3—APP3 is a Windows Server 2003 Enterprise Edition computer that acts as an IPv4-only host and is used to demonstrate DirectAccess connectivity to IPv4-only resources using the UAG DNS64 and NAT64 features. APP3 hosts both HTTP and SMB resources that the DirectAccess client computer will be able to access from the simulated Internet.

  4. Step 4: Configure UAG1—UAG1 acts as the first DirectAccess server and array manager in a Forefront UAG DirectAccess array.

  5. Step 5: Configure CLIENT1—CLIENT1 is a DirectAccess client that is used to test DirectAccess connectivity in several Internet network access scenarios.

  6. Step 6: Configure INET1—INET1 provides DNS and DHCP servers for CLIENT1 when CLIENT1 is connected to the Internet. INET1 also provides DNS services to NAT1 in NAT1’s role as Internet Connection Server (ICS).

  7. Step 7: Configure NAT1—NAT1 acts as a simulated NAT router that enables CLIENT1 access to the Forefront UAG DirectAccess server over the simulated Internet.

  8. Step 8: Test DirectAccess connectivity from the Internet—CLIENT1 is connected to the simulated Internet subnet to demonstrate DirectAccess connectivity using the 6to4 IPv6 transition technology.

  9. Step 9: Test DirectAccess connectivity from behind a NAT device—CLIENT1 is connected to the simulated private address network to demonstrate DirectAccess connectivity using the Teredo and IP-HTTPS IPv6 transition technologies.

  10. Step 10: Test connectivity when returning to the Corpnet—CLIENT1 is connected again to the Corpnet subnet to demonstrate how DirectAccess components are automatically disabled to connect to local resources.

  11. Step 11: Configure UAG2—UAG2 is configured as the second DirectAccess server in a Forefront UAG DirectAccess array.

  12. Step 12: Create a networked load balanced UAG DirectAccess array—UAG1 is configured as the array manager in a Forefront UAG DirectAccess array. UAG2 is joined to the array and network load balancing is configured for the array.

  13. Step 13: Configure and test remote management capabilities—CLIENT1 is connected to the Homenet and remote connectivity to the DirectAccess client is tested from DC1 on the Corpnet.