Step By Step Guide: Demonstrate VPN NAP Enforcement in a Test Lab

Microsoft Corporation Published: February 2008

Abstract
Network Access Protection (NAP) is a new policy enforcement technology in Windows Vista, Windows Server 2008, and Windows XP with Service Pack 3 (SP3). NAP provides components and an application programming interface (API) set that help administrators enforce compliance with health requirements for network access and communication. This paper contains an introduction to NAP and instructions for setting up a test lab to deploy NAP with the VPN enforcement method.

Copyright Information
This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2008 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are property of their respective owners.

Contents
Step By Step Guide: Demonstrate VPN NAP Enforcement in a Test Lab.......................................1 Abstract....................................................................................................................................1 Copyright Information......................................................................................................................2 Contents..........................................................................................................................................3 Step-by-Step Guide: Demonstrate NAP VPN Enforcement in a Test Lab.......................................5 In this guide.................................................................................................................................5 Scenario overview.......................................................................................................................6 NAP enforcement processes....................................................................................................6 Policy validation....................................................................................................................6 NAP enforcement and network restriction.............................................................................7 Remediation..........................................................................................................................7 Ongoing monitoring to ensure compliance............................................................................7 NAP VPN enforcement overview.................................................................................................8 Hardware and software requirements..........................................................................................8 Steps for configuring the test lab.................................................................................................9 Configure DC1...........................................................................................................................10 Install the operating system on DC1.......................................................................................10 Configure TCP/IP on DC1......................................................................................................10 Configure DC1 as a domain controller and DNS server.........................................................11 Install an enterprise root CA on DC1......................................................................................11 Create a user account in Active Directory..............................................................................13 Add user1 to the Domain Admins group.................................................................................13 Grant remote access permission to user1..............................................................................13 Create a security group for NAP client computers..................................................................14 Configure VPN1.........................................................................................................................14 Install Windows Server 2008..................................................................................................15 Configure TCP/IP properties on VPN1...................................................................................15 Join VPN1 to the Contoso.com domain..................................................................................16 User Account Control.............................................................................................................16 Install the Routing and Remote Access server role................................................................16 Configure Routing and Remote Access..................................................................................17 Configure authentication methods on VPN1..........................................................................21 Allow ping on VPN1................................................................................................................21 Configure NPS1.........................................................................................................................22 Install Windows Server 2008 or Windows Server 2008 R2....................................................22 Configure TCP/IP properties on NPS1...................................................................................23 Join NPS1 to the Contoso.com domain..................................................................................23

Install the NPS server role......................................................................................................24 Install the Group Policy Management feature.........................................................................24 Configure NAP client settings in Group Policy........................................................................25 Configure security filters for the NAP client settings GPO...................................................26 Obtain a computer certificate on NPS1..................................................................................26 Configure NPS as a NAP health policy server........................................................................27 Configure NAP with a wizard..............................................................................................28 Configure system health validators.....................................................................................30 Configure VPN1 as a NAP-capable RADIUS client............................................................31 Allow ping on NPS1................................................................................................................33 Configure CLIENT1...................................................................................................................33 Install Windows Vista or Windows 7 on CLIENT1..................................................................34 Configure TCP/IP for the intranet network segment...............................................................34 Enable Run on the Start menu...............................................................................................35 Verify network connectivity for CLIENT1................................................................................35 Join CLIENT1 to the Contoso.com domain............................................................................35 Add CLIENT1 to the NAP client computers security group.....................................................36 Verify Group Policy settings...................................................................................................36 Configure CLIENT1 for the Internet network segment............................................................37 Configure TCP/IP on CLIENT1...........................................................................................37 Verify network connectivity for CLIENT1.............................................................................37 Configure and test a VPN connection....................................................................................38 Configure a VPN connection...............................................................................................38 Test the new VPN connection.............................................................................................39 Verifying NAP functionality.........................................................................................................40 Verification of NAP auto-remediation......................................................................................40 Verification of NAP policy enforcement..................................................................................42 Configure WSHV to require an antivirus application...........................................................42 Connect to VPN1 from CLIENT1........................................................................................43 Remove the antivirus health requirement so that CLIENT1 can become compliant...........44 See Also....................................................................................................................................44 Appendix.......................................................................................................................................45 Set UAC behavior of the elevation prompt for administrators....................................................45 Review NAP client events..........................................................................................................45 Review NAP server events........................................................................................................46

Step-by-Step Guide: Demonstrate NAP VPN Enforcement in a Test Lab

Network Access Protection (NAP) is a new technology introduced in Windows Vista and Windows Server 2008. (NAP can also be deployed on computers running Windows Server 2008 R2 and Windows 7). NAP includes client and server components that allow you to create and enforce health requirement policies that define the required software and system configurations for computers that connect to your network. NAP enforces health requirements by inspecting and assessing the health of client computers, limiting network access when client computers are deemed noncompliant, and remediating noncompliant client computers for unlimited network access. NAP enforces health requirements on client computers that are attempting to connect to a network. NAP also provides ongoing health compliance enforcement while a compliant client computer is connected to a network. In addition, NAP provides an application programming interface (API) set that allows nonMicrosoft software vendors to integrate their solutions into the NAP framework. NAP enforcement occurs at the moment client computers attempt to access the network through network access servers, such as a virtual private network (VPN) server running Routing and Remote Access, or when clients attempt to communicate with other network resources. The way in which NAP is enforced depends on the enforcement method you choose. NAP enforces health requirements for the following: Internet Protocol security (IPsec)-protected communications Institute of Electrical and Electronics Engineers (IEEE) 802.1X-authenticated connections VPN connections Dynamic Host Configuration Protocol (DHCP) configuration Terminal Services Gateway (TS Gateway)

The step-by-step instructions in this paper will show you how to deploy a NAP VPN enforcement test lab so that you can better understand how VPN enforcement works.

In this guide
This paper contains an introduction to NAP and instructions for setting up a test lab and deploying NAP with the VPN enforcement method using three server computers and one client computer. You create and enforce client health requirements using NAP and VPN. Important 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. This configuration is neither designed to reflect best practices nor does it reflect a desired or recommended
5

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.

Scenario overview
In this test lab, NAP enforcement for VPN network access control is deployed with a server running Network Policy Server (NPS), a server running Routing and Remote Access, and a VPN enforcement client component. NAP-capable client computers with valid authentication credentials will be provided VPN access to an intranet based on their compliance with network health requirements.

NAP enforcement processes

Several processes are required for NAP to function properly: policy validation, NAP enforcement and network restriction, remediation, and ongoing monitoring to ensure compliance.

Policy validation
NAP policy validation is performed by NPS in its role as a NAP health policy server and a Remote Authentication Dial-in User Service (RADIUS) server. System health validators (SHVs) are used by NPS to analyze the health status of client computers. SHVs are incorporated into network polices that determine actions to be taken based on client health status, such as the granting of full network access or the restricting of network access. Health status is monitored by client-side NAP components called system health agents (SHAs). NAP uses SHAs and SHVs to monitor, enforce, and remediate client computer configurations. Windows Security Health Agent (WSHA) and Windows Security Health Validator (WSHV) are included with the Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems, and enforce the following settings for NAP-capable computers: The client computer has firewall software installed and enabled. The client computer has antivirus software installed and running. The client computer has current antivirus updates installed. The client computer has antispyware software installed and running. The client computer has current antispyware updates installed. Microsoft Update Services is enabled on the client computer.

In addition, if NAP-capable client computers are running Windows Update Agent, NAP can verify that the most recent software security updates are installed based on one of four possible values that match security severity ratings from the Microsoft Security Response Center (MSRC). This test lab will use the WSHA and WSHV to require that client computers have turned on Windows Firewall, and have an antivirus application installed.

NAP enforcement and network restriction

NAP enforcement settings allow you to limit network access of noncompliant clients to a restricted network, to defer restriction to a later date, or to merely monitor and log the health status of NAPcapable client computers. The following settings are available: Allow full network access. This is the default setting. Clients that match the policy conditions are granted unrestricted access to the network if the connection request is authenticated and authorized. The health compliance status of NAP-capable client computers is logged. Allow limited access. Client computers that match the policy conditions are placed on the restricted network. Allow full network access for a limited time. Clients that match the policy conditions are temporarily granted full network access. NAP enforcement is delayed until the specified date and time. You will create two network policies in this test lab. A compliant policy will grant full network access to an intranet network segment. A noncompliant policy will demonstrate network restriction by applying IP filters to the VPN tunnel interface that only allow client access to a single remediation server.

Remediation
Noncompliant client computers that are placed on a restricted network might undergo remediation. Remediation is the process of updating a client computer so that it meets current health requirements. If additional resources are required for a noncompliant computer to update its health state, these resources must be provided on the restricted network. For example, a restricted network might contain a File Transfer Protocol (FTP) server that provides current virus signatures so that noncompliant client computers can update their outdated signatures. You can use NAP settings in NPS network policies to configure automatic remediation so that NAP client components automatically attempt to update the client computer when it is noncompliant. This test lab includes a demonstration of automatic remediation. The Enable auto-remediation of client computers setting will be enabled in the noncompliant network policy, causing Windows Firewall to be turned on without user intervention.

Ongoing monitoring to ensure compliance

NAP can enforce health compliance on compliant client computers that are already connected to the network. This functionality is useful for ensuring that a network is protected on an ongoing basis as health policies change and the health of client computers change. Client computers are monitored when their health state changes, and when they initiate requests for network resources. This test lab includes a demonstration of ongoing monitoring when Windows Firewall on the client computer is turned off. The NAP client computer sends a new statement of health (SoH) that indicates it is noncompliant with network requirements, causing a change in the VPN tunnel interface that restricts network access.
7

NAP VPN enforcement overview

The NAP VPN enforcement method depends on a NAP VPN enforcement server running Routing and Remote Access, a NAP client with the Remote Access Quarantine Enforcement Client enabled, and a server running NPS that contains NAP policies and settings. Using VPN enforcement, VPN servers can enforce health policy requirements any time a computer attempts to make a VPN connection to the network. VPN enforcement provides strong limited network access for all computers accessing the network through a VPN connection. The test lab consists of an intranet network segment assigned a private IP address range of 192.168.0.0/24 that is connected to "hub1" and an Internet network segment assigned a public IP address range of 131.107.0.0/24 that is connected to "hub2," as shown in the following figure.

In the test lab, CLIENT1 will initiate a VPN tunnel connection from the Internet segment to the intranet network segment through VPN1. If valid authentication credentials are provided by CLIENT1, the VPN server will request a SoH from the CLIENT1. The SoH is forwarded to NPS1, which serves as a NAP health policy server by evaluating the health status of client computers attempting to connect to the intranet network segment. Based on client health status contained in the SoH, and the current configuration of NAP health policies, NPS1 will instruct VPN1 to either authorize full intranet network access, or restrict access to a limited network.

Hardware and software requirements

The following are required components of the test lab: The product disc for Windows Server 2008 or Windows Server 2008 R2. The product disc for Windows Vista Business, Windows Vista Enterprise, or Windows Vista Ultimate. You can also use the product discs for Windows 7 Home Premium, Windows 7 Professional, or Windows 7 Ultimate. The product disc for Windows Server 2003 Standard Edition operating system with Service Pack 2 (SP2). One computer that meets the minimum hardware requirements for Windows Server 2003 Enterprise Edition operating system with SP2.

Note This lab demonstrates NAP support for the Active Directory directory service in Windows Server 2003. You can also make the domain controller in this lab run Windows Server 2008 or Windows Server 2008 R2. Two computers that meet the minimum hardware requirements for Windows Server 2008 or Windows Server 2008 R2. One computer that meets the minimum hardware requirements for Windows Vista or Windows 7. Two Ethernet hubs or layer 2 switches.

Steps for configuring the test lab

There are four steps to follow when setting up this test lab. 1. Configure DC1. DC1 is a server computer running Windows Server 2003 Standard Edition. DC1 is configured as a domain controller with Active Directory and the primary DNS server for the intranet subnet. DC1 will also serve as an enterprise root certification authority (CA) for the domain. 2. Configure VPN1. VPN1 is a server computer running Windows Server 2008 or Windows Server 2008 R2. VPN1 is configured with Routing and Remote Access as a VPN server. VPN1 has two network adapters installed and is connected to both subnets. 3. Configure NPS1. NPS1 is a server computer running Windows Server 2008 or Windows Server 2008 R2. NPS1 is configured with NPS and functions as a NAP health policy server for the test lab. 4. Configure CLIENT1. CLIENT1 is a client computer running Windows Vista or Windows 7. CLIENT1 will be configured as a VPN client and a NAP client. Note 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. After the NAP components are configured, this guide will provide steps for a demonstration of NAP enforcement and auto-remediation. The following sections provide details about how to perform these tasks.

Configure DC1
DC1 is a computer running Windows Server 2003 Standard Edition with SP2, providing the following services: A domain controller for the Contoso.com Active Directory domain. A DNS server for the Contoso.com DNS domain. The enterprise root CA for the Contoso.com domain.

Note Auto-enrollment of user certificates for EAP-TLS authentication is available with Windows Server 2003 Enterprise Edition. For this test lab deployment, the Certificates Request Wizard will be used to obtain a computer certificate for NPS1. DC1 configuration consists of the following steps: Install the operating system. Configure TCP/IP. Install Active Directory and DNS. Install an enterprise root CA. Create a user account and group in Active Directory. Create a NAP client computer security group.

The following sections explain these steps in detail.

Install the operating system on DC1

Install Windows Server 2003 Standard Edition with SP2 as a stand-alone server. To install the operating system on DC1 1. Start your computer using the Windows Server 2003 product disc. 2. When prompted for a computer name, type DC1.

Configure TCP/IP on DC1

Configure the TCP/IP protocol with a static IP address of 192.168.0.1, the subnet mask of 255.255.255.0, and a default gateway of 192.168.0.3. To configure TCP/IP on DC1 1. Click Start, click Run, and then type ncpa.cpl. 2. Right-click Local Area Connection, and then click Properties. 3. Click Internet Protocol (TCP/IP), and then click Properties. 4. Select Use the following IP address, and type 192.168.0.1 next to IP address, 255.255.255.0 next to Subnet mask, and 192.168.0.3 next to Default gateway.
10

5. Verify that Preferred DNS server is blank. 6. Click OK, click Close, and then close the Network Connections window.

Configure DC1 as a domain controller and DNS server

DC1 will serve as the only domain controller and DNS server for the Contoso.com domain. To configure DC1 as a domain controller and DNS server 1. To start the Active Directory Installation Wizard, click Start, click Run, type dcpromo, and then press ENTER. 2. In the Active Directory Installation Wizard dialog box, click Next. 3. Operating system compatibility information is displayed. Click Next. 4. Verify that Domain controller for a new domain is selected, and then click Next. 5. Verify that Domain in a new forest is selected, and then click Next twice. 6. On the Install or Configure DNS page, select No, just install and configure DNS on this computer, and then click Next. 7. Type contoso.com next to Full DNS name for new domain, and then click Next. 8. Confirm that the Domain NetBIOS name shown is CONTOSO, and then click Next. 9. Accept the default Database Folder and Log Folder directories, and then click Next. 10. Accept the default folder location for Shared System Volume, and then click Next. 11. Verify that Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems is selected, and then click Next. 12. Leave the Restore Mode Password and Confirm Password text boxes blank, and then click Next. 13. Review the summary information provided, and then click Next. 14. Wait while the wizard completes configuration of Active Directory and DNS services, and then click Finish. 15. When prompted to restart the computer, click Restart Now. 16. After the computer has been restarted, log in to the CONTOSO domain using the Administrator account.

Install an enterprise root CA on DC1

The NAP VPN enforcement method requires the use of a computer certificate to perform Protected Extensible Authentication Protocol (PEAP) authentication of VPN clients. The root CA for the public key infrastructure will be installed as an enterprise root CA running on DC1. To install an enterprise root CA on DC1 1. Click Start, click Control Panel, and then double-click Add or Remove Programs.
11

2. Click Add/Remove Windows Components. 3. In the Windows Components Wizard dialog box, select the Certificate Services check box. 4. If a Microsoft Certificate Services dialog box appears warning you that the domain name and computer name cannot be changed, click Yes. 5. In the Windows Components Wizard dialog box, click Next. 6. Select Enterprise root CA, and then click Next. 7. In Common name for this CA, type Root CA. The following figure shows an example.

8. Click Next, and then click Next again. 9. If a Microsoft Certificate Services dialog box appears warning you that Internet Information Services (IIS) is not installed, click OK. You do not need to install IIS on DC1 for certificate Web enrollment support. 10. Click Finish. 11. Close the Add or Remove Programs window.

12

Create a user account in Active Directory

Next, create a user account in Active Directory. This account will be used when logging in to NPS1, VPN1, and CLIENT1. To create a user account in Active Directory 1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers. 2. In the console tree, double-click Contoso.com, right-click Users, point to New, and then click User. 3. In the New Object - User dialog box, next to Full name, type User1 User, and in User logon name, type User1. 4. Click Next. 5. In Password, type the password that you want to use for this account, and in Confirm password, type the password again. 6. Clear the User must change password at next logon check box, and select the Password never expires check box. 7. Click Next, and then click Finish. 8. Leave the Active Directory Users and Computers console open for the following procedure.

Add user1 to the Domain Admins group

Next, add the newly created user to the Domain Admins group so this user can be used for all configuration activities. To add a user to the Domain Admins group 1. In the Active Directory Users and Computers console tree, click Users. 2. In the details pane, double-click Domain Admins. 3. In the Domain Admins Properties dialog box, click the Members tab, and then click Add. 4. Under Enter the object names to select (examples), type User1, the user name that you created in the preceding procedure, and then click OK twice. 5. Leave the Active Directory Users and Computers console open for the following procedure.

Grant remote access permission to user1

Because user1 will be accessing the network through a VPN connection, this account must be granted remote access permission.

13

To grant remote access permission to user1 1. In the Active Directory Users and Computers console tree, double-click Contoso.com, and then click Users. 2. In the details pane, double-click User1 User. 3. In the User1 User Properties dialog box, click the Dial-in tab. 4. Under Remote Access Permission (Dial-in or VPN), select Allow access, and then click OK. 5. Leave the Active Directory Users and Computers console open for the following procedure.

Create a security group for NAP client computers

Next, create a security group for use with Group Policy security filtering. This security group will be used to apply NAP client computer settings to only the computers you specify. CLIENT1 will be added to this security group after it is joined to the domain. To create a security group for NAP client computers 1. In the Active Directory Users and Computers console tree, right-click Contoso.com, point to New, and then click Group. 2. In the New Object - Group dialog box, under Group name, type NAP client computers. 3. Under Group scope, choose Global, under Group type, choose Security, and then click OK. 4. Leave the Active Directory Users and Computers console open for the following procedure.

Configure VPN1
For the test lab, VPN1 will be running Windows Server 2008, and will host Routing and Remote Access, which provides a VPN access point for CLIENT1. VPN1 has two network adapters so that it can be connected to both the intranet and Internet network segments. VPN1 is configured in the following steps: Install the operating system. Configure TCP/IP. Join the computer to the domain. Install and configure Routing and Remote Access. Allow ping on VPN1.

The following sections provide details about how to perform these tasks.

14

Install Windows Server 2008

To install Windows Server 2008 1. Start your computer using the Windows Server 2008 or Windows Server 2008 R2 product CD. 2. When prompted for the installation type, choose Custom. 3. Follow the instructions that appear on your screen to finish the installation.

Configure TCP/IP properties on VPN1

To configure TCP/IP properties on VPN1 1. Click Close in the Initial Configuration Tasks window, and then use Server Manager, which is automatically displayed, to perform this procedure. 2. In Server Manager, under Server Summary, click View Network Connections. 3. In the Network Connections dialog box, right-click the network adapter connected to the intranet network segment (hub1), and then click Properties. 4. In the Local Area Connection Properties dialog box, clear the Internet Protocol Version 6 (TCP/IPv6) check box. This will reduce the complexity of the lab, particularly for those who are not familiar with IPv6. 5. In the Local Area Connection Properties dialog box, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 6. Select Use the following IP address. In IP address, type 192.168.0.3. In Subnet mask, type 255.255.255.0. 7. Select Use the following DNS server addresses. In Preferred DNS server, type 192.168.0.1. 8. Click OK, and then click Close. 9. Next, right-click the network adapter attached to the Internet network segment (hub2), and then click Properties. 10. In the Local Area Connection Properties dialog box, clear the Internet Protocol Version 6 (TCP/IPv6) check box. 11. In the Local Area Connection Properties dialog box, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 12. Select Use the following IP address. In IP address, type 131.107.0.1. In Subnet mask, type 255.255.255.0. 13. Click OK, and then click Close. 14. Close the Network Connections window. 15. Do not close Server Manager. It will be used in the next procedure. 16. Next, run the ping command from VPN1 to confirm network communication between
15

VPN1 and DC1. 17. Click Start, click Run, type cmd, and then press ENTER. 18. In the command window, type ping DC1. 19. Verify that the response reads Reply from 192.168.0.1." 20. Close the command window.

Join VPN1 to the Contoso.com domain

To join VPN1 to the Contoso.com domain 1. In Server Manager, under Server Summary, click Change system properties. 2. In the System Properties dialog box, on the Computer Name tab, click Change. 3. In the Computer Name/Domain Changes dialog box, under Computer name, type VPN1. 4. In the Computer Name/Domain Changes dialog box, under Member of, choose Domain, and then under Domain, type contoso.com. 5. Click More. Under Primary DNS suffix of this computer, type contoso.com, and then click OK twice. 6. When prompted for a user name and password, type User1 and a password for the user account that you added to the Domain Admins group, and then click Submit. 7. When you see a dialog box that welcomes you to the Contoso.com domain, click OK. 8. When you see a dialog box that prompts you to restart the computer, click OK. 9. On the System Properties dialog box, click Close. 10. When you see a dialog box that prompts you to restart the computer, click Restart Now. 11. After the computer has been restarted, click Switch User, then click Other User and log on to the CONTOSO domain with the User1 account you created.

User Account Control

When configuring the Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2 operating systems, you are required to click Continue in the User Account Control (UAC) dialog box for some tasks. Several of the configuration tasks to follow require UAC approval. When prompted, always click Continue to authorize these changes. Alternatively, see the Appendix of this guide for instructions about how to set UAC behavior of the elevation prompt for administrators.

Install the Routing and Remote Access server role

16

To install the Routing and Remote Access server role 1. Click Close in the Initial Configuration Tasks window, and then use Server Manager, which is automatically displayed, to perform this procedure. 2. Under Roles Summary, click Add Roles, and then click Next. 3. Select the Network Policy and Access Services check box, and then click Next twice. 4. Select the Remote Access Service check box, click Next, and then click Install. 5. Verify the installation was successful, and then click Close. 6. Close Server Manager.

Configure Routing and Remote Access

Routing and Remote Access provides VPN service to VPN clients connected to the Internet subnet. VPN1 must be configured as a VPN server and as a RADIUS client to NPS1. To configure Routing and Remote Access as a VPN server 1. Click Start, click Run, type rrasmgmt.msc, and then press ENTER. 2. In the Routing and Remote Access console, right-click VPN1, and then click Configure and Enable Routing and Remote Access. This starts the Routing and Remote Access Server Setup Wizard. 3. Click Next, select Remote access (dial-up or VPN), and then click Next. See the following example.

17

4. Select the VPN check box, and then click Next. 5. Click the network interface with an IP address of 131.107.0.1. Clear the check box next to Enable security on the selected interface by setting up static packet filters, and then click Next. This ensures that CLIENT1 will be able to ping VPN1 when attached to the Internet subnet without having to configure additional packet filters for ICMP traffic. See the following example.

18

6. On the IP Address Assignment page, select From a specified range of addresses, and then click Next. 7. On the Address Range Assignment page, click New. Type 192.168.0.100 next to Start IP address and 192.168.0.110 next to End IP address, and then click OK. Verify that 11 IP addresses were assigned for remote clients, and then click Next. See the following example.

19

8. On the Managing Multiple Remote Access Servers page, select Yes, set up this server to work with a RADIUS server, and then click Next. 9. On the RADIUS Server Selection page, type 192.168.0.2 next to Primary RADIUS server, and type secret next to Shared secret. See the following example.

20

10. Click Next, and then click Finish. 11. In the Routing and Remote Access notification box that appears, click OK and then wait for Routing and Remote Access to start.

Configure authentication methods on VPN1

To configure authentication methods on VPN1 1. In the Routing and Remote Access console, right-click VPN1, and then click Properties. 2. Click the Security tab. Click Authentication Methods and verify that Extensible authentication protocol (EAP) and Microsoft encrypted authentication version 2 (MS-CHAP v2) are selected. 3. Click EAP Methods, and verify that Protected EAP (PEAP) is one of the installed EAP methods.

Allow ping on VPN1

Ping will be used to verify connectivity of CLIENT1 to VPN1 on the Internet segment. To enable VPN1 to respond to ping, ICMPv4 must be allowed through Windows Firewall on VPN1.
21

To allow ping on VPN1 1. Click Start, click Run, type wf.msc, and then press ENTER. 2. In the Windows Firewall with Advanced Security console tree, right-click Inbound Rules, and then click New Rule. 3. Select Custom, and then click Next. 4. Select All programs, and then click Next. 5. Next to Protocol type, select ICMPv4, and then click Customize. 6. Select Specific ICMP types, select the Echo Request check box, click OK, and then click Next. 7. Click Next to accept the default scope. 8. In the Action window, verify that Allow the connection is selected, and then click Next. 9. Click Next to accept the default profile. 10. In the Name window, under Name, type ICMPv4 echo request, and then click Finish.

Configure NPS1
For the test lab, NPS1 will be running Windows Server 2008 or Windows Server 2008 R2, and will host the NPS service, which provides RADIUS authentication, authorization, and accounting for VPN1. NPS1 configuration consists of the following steps: Install the operating system. Configure TCP/IP. Join the computer to the domain. Install the NPS server role. Install the Group Policy Management feature. Configure NAP client settings in Group Policy. Obtain a computer certificate. Configure NPS as a NAP health policy server. Allow ping on NPS1.

Install Windows Server 2008 or Windows Server 2008 R2

To install Windows Server 2008 or Windows Server 2008 R2 1. Start your computer using the Windows Server 2008 or Windows Server 2008 R2 product CD. 2. When prompted for the installation type, choose Custom.
22

3. Follow the instructions that appear on your screen to finish the installation.

Configure TCP/IP properties on NPS1

To configure TCP/IP properties on NPS1 1. Click Server Manager. 2. Under Server Summary, click View Network Connections. 3. In the Network Connections window, right-click Local Area Connection, and then click Properties. 4. In the Local Area Connection Properties dialog box, clear the Internet Protocol Version 6 (TCP/IPv6) check box. This step will reduce the complexity of the lab, particularly for those who are not familiar with IPv6. 5. In the Local Area Connection Properties dialog box, click Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 6. Select Use the following IP address. In IP address, type 192.168.0.2. In Subnet mask, type 255.255.255.0. 7. Select Use the following DNS server addresses. In Preferred DNS server, type 192.168.0.1. 8. Click OK, and then click Close to close the Local Area Connection Properties dialog box. 9. Close the Network Connections window. 10. Do not close Server Manager. It will be used in the next procedure. 11. Next, check network communication between NPS1 and DC1 by running the ping command from NPS1. 12. Click Start, click Run, in Open, type cmd, and then press ENTER. 13. In the command window, type ping DC1. 14. Verify that the response reads Reply from 192.168.0.1." 15. Close the command window.

Join NPS1 to the Contoso.com domain

To join NPS1 to the Contoso.com domain 1. In Server Manager, under Server Summary, click Change System Properties. 2. In the System Properties dialog box, on the Computer Name tab, click Change. 3. In the Computer Name/Domain Changes dialog box, under Computer name, type NPS1. 4. In the Computer Name/Domain Changes dialog box, under Member of, choose Domain, and then under Domain, type contoso.com.
23

5. Click More. Under Primary DNS suffix of this computer, type contoso.com, and then click OK twice. 6. When prompted for a user name and password, type User1 and the password for the user account that you added to the Domain Admins group, and then click OK. 7. When you see a dialog box that welcomes you to the Contoso.com domain, click OK. 8. When you are prompted to restart the computer, click OK. 9. On the System Properties dialog box, click Close. 10. When you are prompted to restart the computer, click Restart Now. 11. After the computer has been restarted, click Switch User, then click Other User and log on to the CONTOSO domain with the User1 account you created.

Install the NPS server role

To install the NPS server role 1. Click Close in the Initial Configuration Tasks window, and then use Server Manager, which is automatically displayed, to perform this procedure. 2. In Server Manager, under Roles Summary, click Add Roles, and then click Next. 3. Select the Network Policy and Access Services check box, and then click Next twice. 4. Select the Network Policy Server check box, click Next, and then click Install. 5. Verify the installation was successful, and then click Close. 6. Leave Server Manager open for the following procedure.

Install the Group Policy Management feature

Group Policy will be used to configure NAP client settings in the test lab. To access these settings, the Group Policy Management feature must be installed on a computer running Windows Server 2008. To install the Group Policy Management feature 1. In Server Manager, under Features Summary, click Add Features. 2. Select the Group Policy Management check box, click Next, and then click Install. 3. Verify the installation was successful, and then click Close to close the Add Features Wizard dialog box. 4. Close Server Manager.

24

Configure NAP client settings in Group Policy

The following NAP client settings will be configured in a new Group Policy object (GPO) using the Group Policy Management feature on NPS1: NAP enforcement clients NAP Agent service Security Center user interface

After these settings are configured in the GPO, security filters will be added to enforce the settings on computers you specify. The following section describes these steps in detail. To configure NAP client settings in Group Policy 1. On NPS1, click Start, click Run, type gpme.msc, and then press ENTER. 2. In the Browse for a Group Policy Object dialog box, next to Contoso.com, click the icon to create a new GPO, type NAP client settings for the name of the new GPO, and then click OK. 3. The Group Policy Management Editor window will open. Navigate to Computer Configuration/Policies/Windows Settings/Security Settings/System Services. 4. In the details pane, double-click Network Access Protection Agent. 5. In the Network Access Protection Agent Properties dialog box, select the Define this policy setting check box, choose Automatic, and then click OK. 6. In the console tree, open Network Access Protection\NAP Client Configuration\Enforcement Clients. 7. Do one of the following: a. If you are running Windows Vista on your CLIENT1 computer, in the details pane, right-click Remote Access Quarantine Enforcement Client, and then click Enable. b. If you are running Windows 7 on your CLIENT1 computer, in the details pane, right-click EAP Quarantine Enforcement Client, and then click Enable. 8. In the console tree, right-click NAP Client Configuration, and then click Apply. Note If you are running Windows Server 2008 R2, you can skip this step. 9. In the console tree, navigate to Computer Configuration\Policies\Administrative Templates\Windows Components\Security Center. 10. In the details pane, double-click Turn on Security Center (Domain PCs only), choose Enabled, and then click OK. 11. Close the Group Policy Management Editor window. 12. If you are prompted to apply settings, click Yes.

25

Configure security filters for the NAP client settings GPO

Next, configure security filters for the NAP client settings GPO. This prevents NAP client settings from being applied to server computers in the domain. To configure security filters for the NAP client settings GPO 1. On NPS1, click Start, click Run, type gpmc.msc, and press ENTER. 2. In the Group Policy Management Console (GPMC) tree, navigate to Forest: Contoso.com\Domains\Contoso.com\Group Policy Objects\NAP client settings. 3. In the details pane, under Security Filtering, click Authenticated Users, and then click Remove. 4. When you are prompted to confirm the removal of delegation privilege, click OK. 5. In the details pane, under Security Filtering, click Add. 6. In the Select User, Computer, or Group dialog box, under Enter the object name to select (examples), type NAP client computers, and then click OK. 7. Close the GPMC. Note CLIENT1 will be added to the NAP client computers security group after it is joined to the domain.

Obtain a computer certificate on NPS1

To provide server-side PEAP authentication, the server running NPS uses a computer certificate stored in its local computer certificate store. Certificate Manager will be used to obtain a computer certificate from the certification authority service on DC1. To obtain a computer certificate on NPS1 1. Click Start, click Run, type mmc, and then press ENTER. 2. On the File menu, click Add/Remove Snap-in. 3. In the Add or Remove Snap-ins dialog box, click Certificates, click Add, select Computer account, click Next, and then click Finish. 4. Click OK to close the Add or Remove Snap-ins dialog box. 5. In the console tree, double-click Certificates, right-click Personal, point to All Tasks, and then click Request New Certificate. 6. The Certificate Enrollment dialog box opens. Click Next. 7. Select the Computer check box, and then click Enroll, as shown in the following example. Note If you are running Windows Server 2008 R2, in the Certificate Enrollment dialog box, click Next. On the Select Certificate Enrollment Policy page,
26

select Active Directory Enrollment Policy, click Next, select Computer, and then click Enroll.

8. Verify the status of certificate installation is Succeeded, and then click Finish. 9. Close the Console1 window. 10. Click No when prompted to save console settings.

Configure NPS as a NAP health policy server

To serve as a NAP health policy server, NPS1 must validate the system health of clients against the configured network health requirements. For this test lab, configuration of NPS as a NAP health policy server is performed using the NAP configuration wizard. The NAP wizard helps you configure each NAP component to work with the NAP enforcement method you choose. These components are displayed in the NPS console tree, and include: System Health Validators. System health validators (SHVs) define configuration requirements for computers that attempt to connect to your network. For the test lab, WSHV will be configured to require that Windows Firewall is enabled, and that an antivirus application is installed. Health Policies. Health policies define which SHVs are evaluated, and how they are used in the validation of the configuration of computers that attempt to connect to your network. Based on the results of SHV checks, health policies classify client health status. The

27

two health policies in this test lab correspond to a compliant health state and a noncompliant health state. Network Policies. Network policies use conditions, settings, and constraints to determine who can connect to the network. There must be a network policy that will be applied to computers that are compliant with the health requirements, and a network policy that will be applied to computers that are noncompliant. For this test lab, compliant client computers will be allowed unrestricted network access. Clients determined to be noncompliant with health requirements will have their access restricted through the use of IP packet filters. Noncompliant clients will also be optionally updated to a compliant state and subsequently granted unrestricted network access. Connection Request Policies. Connection request policies are conditions and settings that validate requests for network access and govern where this validation is performed. In this test lab, a connection request policy is used that requires the client computer to perform protected EAP (PEAP) authentication before being granted access to the network. RADIUS Clients and Servers. RADIUS clients are network access servers. If you specify a RADIUS client, then a corresponding RADIUS server entry is required on the RADIUS client device. In this test lab, the VPN server is configured as a RADIUS client on NPS. You must also configure the VPN server to recognize NPS as a RADIUS server. Remediation Server Groups. Remediation server groups allow you to specify servers that are made available to noncompliant NAP clients so that they can remediate their health state and become compliant with health requirements. For this lab, you will configure a single remediation server so that noncompliant clients have access to domain services.

Configure NAP with a wizard

The NAP configuration wizard helps you to set up NPS as a NAP health policy server. The wizard provides commonly used settings for each NAP enforcement method, and automatically creates customized NAP policies for use with your network design. You can access the NAP configuration wizard from the NPS console. To configure NPS using the NAP wizard 1. Click Start, click Run, type nps.msc, and then press ENTER. 2. In the Network Policy Server console tree, click NPS (Local). 3. In the details pane, under Standard Configuration, click Configure NAP. The NAP configuration wizard will start. See the following example.

28

4. On the Select Network Connection Method for Use with NAP page, under Network connection method, select Virtual Private Network (VPN), and then click Next. 5. On the Specify NAP Enforcement Servers Running VPN Server page, under RADIUS clients, click Add. 6. In the New RADIUS Client dialog box, under Friendly name, type NAP VPN Server. Under Address (IP or DNS), type 192.168.0.3. 7. Under Shared secret, type secret. 8. Under Confirm shared secret, type secret, click OK, and then click Next. 9. On the Configure User Groups and Machine Groups page, click Next. You do not need to configure groups for this test lab. 10. On the Configure an Authentication Method page, confirm that a computer
29

certificate obtained in the previous procedure is displayed under NPS Server Certificate, and that Secure Password (PEAP-MSCHAP-v2) is selected under EAP types. Click Next. 11. On the Specify a NAP Remediation Server Group and URL page, click New Group. Important Noncompliant clients are automatically granted access to servers that you add to a remediation server group, provided this group is enabled in the network policy for noncompliant computers. You can also use IP Filters on the Settings tab of a network policy to grant or deny access to source and destination networks, using protocols you specify. At least one IP filter or remediation server group is required to enable restricted access for noncompliant computers. 12. In the New Remediation Server Group dialog box, under Group Name, type Domain Services, and then click Add. 13. In the Add New Server dialog box, under Friendly name, type DC1. 14. Under IP address or DNS name, type 192.168.0.1, and then click OK twice. 15. Under Remediation Server Group, verify that the newly created remediation server group is selected, and then click Next. 16. On the Define NAP Health Policy page, verify that Windows Security Health Validator and Enable auto-remediation of client computers check boxes are selected, and then click Next. 17. On the Completing NAP Enforcement Policy and RADIUS Client Configuration page, click Finish. 18. Leave the NPS console open for the following procedure.

Configure system health validators

System health validators (SHVs) define configuration requirements for computers that attempt to connect to your network. For the test lab, WSHV will be configured to require only that Windows Firewall is enabled. Use one of the following procedures depending on whether you are running Windows Server 2008 or Windows Server 2008 R2. To configure system health validators in Windows Server 2008 1. In the Network Policy Server console tree, open Network Access Protection, and then click System Health Validators. 2. In the details pane, under Name, double-click Windows Security Health Validator. 3. In the Windows Security Health Validator Properties dialog box, click Configure. 4. Clear all check boxes except A firewall is enabled for all network connections. See the following example.
30

5. Click OK to close the Windows Security Health Validator dialog box, and then click OK to close the Windows Security Health Validator Properties dialog box. 6. Leave the Network Policy Server console open for the following procedure. To configure system health validators in Windows Server 2008 R2 1. In the Network Policy Server console tree, open Network Access Protection/System Health Validators/Windows Security Health Validator/Settings. 2. In the details pane, under Name, double-click Default Configuration. 3. In the Windows Security Health Validator dialog box, in the left pane, select Windows 7/Windows Vista, and then under Choose policy settings for Windows Security Health Validator, clear all the check boxes except for A firewall is enabled for all network connections. 4. Click OK to close the Windows Security Health Validator dialog box, and then close the Network Policy Server console.

Configure VPN1 as a NAP-capable RADIUS client

Because VPN1 is a NAP enforcement server running Windows Server 2008 or Windows Server 2008 R2, it must be marked as a NAP-capable RADIUS client.

31

To configure VPN1 as a NAP-capable RADIUS client 1. In the NPS console tree, under RADIUS Clients and Servers, click RADIUS Clients. 2. In the details pane, double-click NAP VPN Server, and then do one of the following: If you are running Windows Server 2008, on the Settings tab, select the RADIUS client is NAP-capable check box. If you are running Windows Server 2008 R2, on the Advanced tab, select the RADIUS client is NAP-capable check box. See the following example for Windows Server 2008.

32

3. Click OK. 4. Close the Network Policy Server console.

Allow ping on NPS1

Ping will be used to verify connectivity of CLIENT1 to NPS1 on the Internet segment. To enable NPS1 to respond to ping, ICMPv4 must be allowed through Windows Firewall on NPS1. To allow ping on NPS1 1. Click Start, click Run, type wf.msc, and then press ENTER. 2. In the Windows Firewall with Advanced Security console tree, right-click Inbound Rules, and then click New Rule. 3. Select Custom, and then click Next. 4. Select All programs, and then click Next. 5. Next to Protocol type, select ICMPv4, and then click Customize. 6. Select Specific ICMP types, select the Echo Request check box, click OK, and then click Next. 7. Click Next to accept the default scope. 8. In the Action window, verify that Allow the connection is selected, and then click Next. 9. Click Next to accept the default profile. 10. In the Name window, under Name, type ICMPv4 echo request, and then click Finish.

Configure CLIENT1
CLIENT1 is a computer running Windows Vista or Windows 7 that you will use to demonstrate how NAP can be used with VPN to help protect a network from noncompliant client computers. CLIENT1 must be configured as a domain member while connected to the intranet network segment, and then configured as a VPN client while connected to the Internet segment. CLIENT1 configuration is performed in the following steps: Install the operating system. Configure TCP/IP for the intranet and Internet network segments. Enable Run on the Start menu and verify network connectivity. Join CLIENT1 to the Contoso.com domain. Add CLIENT1 to the NAP client computers security group and restart the computer. Verify Group Policy settings. Configure CLIENT1 for the Internet network segment and verify network connectivity. Configure and test a VPN connection.
33

The following sections explain these steps in detail.

Install Windows Vista or Windows 7 on CLIENT1

First, install the operating system on CLIENT1. To install the operating system on CLIENT1 1. Start your computer by using the product discs for Windows Vista or Windows 7. 2. When prompted for the installation type, choose Custom Installation. 3. When prompted for a computer name, type CLIENT1. 4. Follow the instructions that appear on your screen to finish the installation.

Configure TCP/IP for the intranet network segment

CLIENT1 must first be connected to the intranet network segment so that it can be joined to the Contoso.com domain. If CLIENT1 is connected to hub2, disconnect it and connect it temporarily to hub1. To configure TCP/IP for CLIENT1 on the intranet network segment 1. Click Start, and then click Run, and then type ncpa.cpl. Note You must enable the Run command to complete this step. For more information about how to enable the Run command, see To Enable Run on the Start menu procedure later in this document. 2. In the Network Connections window, right-click Local Area Connection, and then click Properties. 3. In the Local Area Connection Properties dialog box, clear the Internet Protocol Version 6 (TCP/IPv6) check box. This will reduce the complexity of the lab, particularly for those who are not familiar with IPv6. 4. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 5. Click Use the following IP address. Next to IP address, type 192.168.0.4. Next to Subnet mask, type 255.255.255.0. 6. Click Use the following DNS server addresses. Next to Preferred DNS server, type 192.168.0.1. 7. Click OK, and then click Close to close the Local Area Connection Properties dialog box. 8. Close the Network Connections window.

34

Enable Run on the Start menu

The run command is useful for several procedures in the test lab. To make it readily available, we will enable Run on the Start menu. To enable Run on the Start menu 1. Right-click Start, and then click Properties. 2. In the Taskbar and Start Menu Properties window, select Start menu, and then click Customize. 3. In the Customize Start Menu window, select the Run command check box, and then click OK twice.

Verify network connectivity for CLIENT1

Run the ping command from CLIENT1 to confirm network communication between CLIENT1 and DC1. To use the ping command to check network connectivity 1. Click Start, click Run, type cmd, and then press ENTER. 2. In the command window, type ping DC1. 3. Verify that the response reads Reply from 192.168.0.1." 4. Close the command window.

Join CLIENT1 to the Contoso.com domain

To join CLIENT1 to the Contoso.com domain 1. Click Start, right-click Computer, and then click Properties. 2. Under Computer name, domain, and workgroup settings, click Change settings. 3. In the System Properties dialog box, click Change. 4. In the Computer Name/Domain Changes dialog box, select Domain, and then type contoso.com. 5. Click More, and in Primary DNS suffix of this computer, type contoso.com. 6. Click OK twice. 7. When prompted for a user name and password, type the user name and password for the User1 account, and then click OK. 8. When you see a dialog box that welcomes you to the Contoso.com domain, click OK. 9. When you see a dialog box that prompts you to restart the computer, click OK. 10. In the System Properties dialog box, click Close. 11. In the dialog box that prompts you to restart the computer, click Restart Later.
35

Note Before you restart the computer, you must add it to the NAP client computers security group so that CLIENT1 will receive NAP client settings from Group Policy.

Add CLIENT1 to the NAP client computers security group

After joining the domain, CLIENT1 must be added to the NAP client computers security group so that it can receive NAP client settings. To add CLIENT1 to the NAP client computers security group 1. On DC1, click Start, point to Administrative Tools, and then click Active Directory Users and Computers. 2. In the console tree, click Contoso.com. 3. In the details pane, double-click NAP client computers. 4. In the NAP client computers Properties dialog box, click the Members tab, and then click Add. 5. In the Select Users, Contacts, Computers, or Groups dialog box, click Object Types, select the Computers check box, and then click OK. 6. Under Enter the object names to select (examples), type CLIENT1, and then click OK. 7. Verify that CLIENT1 is displayed below Members, and then click OK. 8. Close the Active Directory Users and Computers console. 9. Restart CLIENT1. 10. After CLIENT1 has been restarted, click Switch User, then click Other User and log on to the CONTOSO domain with the User1 account you created.

Verify Group Policy settings

After it has been restarted, CLIENT1 will receive Group Policy settings to enable the NAP Agent service and remote access enforcement client. The command line will be used to verify these settings. To verify Group Policy settings on CLIENT1 1. On CLIENT1, click Start, click Run, type cmd, and then press ENTER. 2. In the command window, type netsh nap client show grouppolicy, and then press ENTER. 3. In the command output, under Enforcement clients, verify the following: a. If you are running Windows Vista on your CLIENT1 computer, verify that the Admin status of the Remote Access Quarantine Enforcement Client is Enabled. b. If you are running Windows 7 on your CLIENT1 computer, verify that the Admin
36

status of the EAP Quarantine Enforcement Client is Enabled. 4. In the command window, type netsh nap client show state, and then press ENTER. 5. In the command output, under Enforcement client state, verify the following: a. If you are running Windows Vista on your CLIENT1 computer, verify that the Initialized status of the Remote Access Quarantine Enforcement Client is Yes. b. If you are running Windows 7 on your CLIENT1 computer, verify that the Initialized status of the EAP Quarantine Enforcement Client is Yes. 6. Close the command window.

Configure CLIENT1 for the Internet network segment

To simulate a VPN client connecting from the Internet, CLIENT1 must be disconnected from the intranet network segment (hub1), and then connected to the Internet network segment (hub2). CLIENT1 will be configured as a VPN client while connected to the Internet segment. CLIENT1 configuration for the intranet network segment is performed in the following steps: Configure TCP/IP and verify network connectivity. Configure and test a VPN connection.

The following sections explain these steps in detail.

Configure TCP/IP on CLIENT1

Before you perform this procedure, disconnect CLIENT1 from the intranet network segment and connect it to the Internet network segment. To configure TCP/IP for CLIENT1 on the Internet network segment 1. Click Start, right-click Network, and then click Properties. 2. Click Manage network connections. 3. Right-click Local Area Connection, and then click Properties. 4. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties. 5. Click Use the following IP address. Next to IP address, type 131.107.0.2. Next to Subnet mask, type 255.255.255.0. 6. Next to Preferred DNS server, remove 192.168.0.1. 7. Click OK, and then click Close to close the Local Area Connection Properties dialog box. 8. Close the Network Connections window.

Verify network connectivity for CLIENT1

Run the ping command from CLIENT1 to confirm network communication between CLIENT1 and VPN1 is working on the Internet network segment.

37

To use the ping command to check network connectivity 1. Click Start, click All Programs, click Accessories, and then click Run. 2. Type cmd, and then press ENTER. 3. In the command window, type ping 131.107.0.1. 4. Verify that the response reads Reply from 131.107.0.1." 5. Close the command window.

Configure and test a VPN connection

CLIENT1 must be configured with a VPN connection to VPN1 to access the intranet subnet.

Configure a VPN connection

To configure a VPN connection on CLIENT1 1. Click Start, right-click Network, and then click Properties. 2. Click Set up a connection or network. 3. On the Choose a connection option page, click Connect to a workplace, and then click Next. 4. On the How do you want to connect page, click Use my Internet connection (VPN). 5. Click I'll set up an Internet connection later. 6. On the Type the Internet address to connect to page, next to Internet address, type 131.107.0.1. Next to Destination name, type Contoso. Select the Allow other people to use this connection check box, and then click Next. 7. On the Type your user name and password page, type user1 next to User name, and type the password for the user1 account next to Password. Select the Remember this password check box, type CONTOSO next to Domain (optional), and then click Create. 8. On The connection is ready to use page, click Close. 9. In the Network and Sharing Center window, click Manage Network Connections. 10. Under Virtual Private Network, right-click Contoso, click Properties, and then click the Security tab. 11. Select Advanced (custom settings), and then click Settings. 12. Under Logon security, select Use Extensible Authentication Protocol (EAP), and then choose Protected EAP (PEAP) (encryption enabled). 13. Click Properties. 14. Select the Validate server certificate check box. Clear the Connect to these servers check box, and then select Secured Password (EAP-MSCHAP v2) under
38

Select Authentication Method. Clear the Enable Fast Reconnect check box, and then select the Enable Quarantine checks check box. See the following example.

15. Click OK three times to accept these settings.

Test the new VPN connection

To test the VPN connection on CLIENT1 1. In the Network Connections window, right-click the Contoso connection, and then click Connect. 2. In the Connect Contoso window, click Connect 3. Type the user1 account credentials next to User name, Password, and Logon
39

domain, select the Save this user name and password for future use check box, and then click OK. 4. You are presented with a Validate Server Certificate window the first time this VPN connection is used. Click View Server Certificate, and verify Certificate Information shows that the certificate was issued to nps1.contoso.com by Root CA. Click OK to close the Certificate window, and then click OK again. 5. Wait for the VPN connection to be established. Because CLIENT1 is compliant, it should have unlimited access to the intranet subnet. 6. Click Start, click Run, type cmd, and then press ENTER. 7. In the command window, type ping 192.168.0.1. 8. Verify that the response reads Reply from 192.168.0.1." 9. In the command window, type ping 192.168.0.2. 10. Verify that the response reads Reply from 192.168.0.2." 11. In the command window, type ping 192.168.0.3. 12. Verify that the response reads Reply from 192.168.0.3." 13. Close the command window. 14. In the Network Connections window, right-click the Contoso connection, and then click Disconnect. 15. Leave the Network Connections window open for the procedures to follow.

Verifying NAP functionality

The following procedures are used to verify that the NAP infrastructure is functioning correctly: Verification of NAP auto-remediation. CLIENT1 is automatically remediated when Windows Firewall is turned off, causing Windows Firewall to be turned back on. Verification of NAP policy enforcement. NAP policy is revised to be more restrictive, causing CLIENT1 to be noncompliant with policy and unable to remediate itself. When CLIENT1 is in a noncompliant state, its network access will be restricted.

Verification of NAP auto-remediation

The Noncompliant-Restricted network policy specifies that noncompliant computers should be remediated automatically. The following procedure will verify that CLIENT1 is remediated automatically when Windows Firewall is disabled. To verify that CLIENT1 is remediated automatically when Windows Firewall is turned off 1. On CLIENT1, click Start, and then click Control Panel. 2. Click Security, and under Windows Firewall, click Turn Windows Firewall on or off. 3. In the Windows Firewall Settings dialog box, click Off (not recommended), and
40

then click OK. 4. In the Network Connections window that was left open from the previous procedure, right-click Contoso, and then click Connect. 5. Click Connect, and then click OK. 6. Wait for the VPN connection to be established. 7. You might see a message in the notification area that indicates the computer does not meet health requirements. This message is displayed because Windows Firewall has been turned off. Click this message for more detailed information about the health status of CLIENT1. See the following example.

8. The NAP client will automatically turn Windows Firewall on to become compliant with network health requirements. The following message will appear in the notification area: This computer meets the requirements of this network. See the following example.

41

9. In the Manage Network Connections window, right-click the Contoso connection, and then click Disconnect. 10. Leave the Network Connections window open for the following procedures.

Verification of NAP policy enforcement

To verify that network restriction of noncompliant client computers is being enforced, you will configure NPS1 so that antivirus software is a requirement for system health. Because no antivirus program is installed on CLIENT1 and the NAP client components cannot remediate its health, CLIENT1 will be noncompliant.

Configure WSHV to require an antivirus application

To configure the WSHV to require antivirus software 1. On NPS1, click Start, click Run, type nps.msc, and then press ENTER. 2. In the Network Policy Server console tree, open NPS (Local), then Network Access
42

Protection, and then click System Health Validators. 3. Double-click Windows Security Health Validator, and then click Configure. 4. In the Windows Security Health Validator dialog box, under Virus Protection, select the check box next to An antivirus application is on. 5. Click OK, and then click OK again to close the Windows Security Health Validator Properties window.

Connect to VPN1 from CLIENT1

CLIENT1 will validate its system health when it connects to VPN1. Because an antivirus program is not installed, and the health requirement for an antivirus program cannot be remediated automatically, CLIENT1 will remain in a noncompliant state and will be placed on the restricted network. To verify that CLIENT1 is placed on the restricted network 1. On CLIENT1, in the Network Connections window, right-click Contoso, and then click Connect. 2. Click Connect, and then click OK. 3. Wait for the VPN connection to be made. You might see a message in the notification area that indicates the computer does not meet health requirements. This message is displayed because antivirus software has not been installed. 4. Click Start, click All Programs, click Accessories, and then click Command Prompt. 5. In the command window, type ping 192.168.0.1. 6. Verify that the response reads Reply from 192.168.0.1." CLIENT1 is able to ping this IP address because IP filters were applied in network policy to ensure that traffic from noncompliant clients can reach DC1. 7. In the command window, type ping 192.168.0.2. 8. Verify that there is no response from 192.168.0.2. CLIENT1 is unable to ping this IP address because its access has been restricted and no IP filters have been applied to allow noncompliant NAP client access to the intranet interface on VPN1. 9. In the command window, type ping 192.168.0.3. 10. Verify that there is no response from 192.168.0.3. CLIENT1 is unable to ping this IP address because its access has been restricted and no IP filters have been applied to allow noncompliant NAP client access to NPS1. 11. You can click the NAP icon in the notification area to see more information about the client health state. You can also check the NAP state of the computer by using a NAP client Netsh command. To use a Netsh command to show the NAP client's health state, type netsh nap client show state in the command window, and press ENTER. 12. Scroll the command window to display the Client state section. In the Client state
43

section, the Restriction state will be displayed as Restricted. 13. In the command output, under System health agent (SHA) state, verify next to Remediation results that Windows did not detect an antivirus program that is compatible with Windows Security Center is displayed. 14. Close the command window. 15. In the Network Connections window, right-click Contoso, and then click Disconnect. 16. Leave the Network Connections window open for the following procedure.

Remove the antivirus health requirement so that CLIENT1 can become compliant
To configure NAP policies on NPS1 to allow CLIENT1 to become compliant 1. Open the NPS management console on NPS1. 2. Open NPS (Local), then Network Access Protection, and then click System Health Validators. 3. Double-click Windows Security Health Validator, and then click Configure. 4. In the Windows Security Health Validator dialog box, under Virus Protection, clear the check box next to An antivirus application is on. 5. Click OK, and then click OK again to close the Windows Security Health Validator Properties window. 6. On CLIENT1, in the Network Connections window, right-click Contoso, and then click Connect. 7. Click Connect, and then click OK. 8. Wait for the VPN connection to be made. You should see a message in the notification area that indicates that the computer is compliant with health requirements. 9. Verify that CLIENT1 is compliant by using the command window to ping 192.168.0.2. 10. Verify that the response reads "Reply from 192.168.0.2." 11. Verify that CLIENT1 is compliant by using the command window to ping 192.168.0.3. 12. Verify that the response reads "Reply from 192.168.0.3."

See Also
http://go.microsoft.com/fwlink/?LinkId=56443

44

Appendix
This appendix will help you with troubleshooting techniques and the setting of optional features in Windows Server 2008 or Windows Server 2008 R2 and Windows Vista or Windows 7.

Set UAC behavior of the elevation prompt for administrators

By default, User Account Control (UAC) is enabled in Windows Server 2008 or Windows Server 2008 R2 and Windows Vista or Windows 7.This service will prompt for permission to continue during several of the configuration tasks described in this guide. In all cases, you can click Continue in the UAC dialog box to grant this permission, or you can use the following procedure to change the UAC behavior of the elevation prompt for administrators. To set UAC behavior of the elevation prompt for administrators 1. Click Start, point to All Programs, click Accessories, and then click Run. 2. Type secpol.msc, and press ENTER. 3. In the User Account Control dialog box, click Continue. 4. In the left pane, double-click Local Policies, and then click Security Options. 5. In the right pane, double-click User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode. 6. From the drop-down list box, choose Elevate without prompting, and then click OK. 7. Close the Local Security Policy window.

Review NAP client events

Reviewing information contained in NAP client events can assist you with troubleshooting. It can also help you to understand NAP client functionality. To review NAP client events in Event Viewer 1. Click Start, point to All Programs, click Accessories, and then click Run. 2. Type eventvwr.msc, and press ENTER. 3. In the left tree, navigate to Event Viewer(Local)\Applications and Services Logs\Microsoft\Windows\Network Access Protection\Operational. 4. Click an event in the middle pane. 5. By default, the General tab is displayed. Click the Details tab to view additional information. 6. You can also right-click an event and then click Event Properties to open a new window for reviewing events.
45

Review NAP server events

Reviewing information contained in Windows System events on your NAP servers can assist you with troubleshooting. It can also help you to understand NAP server functionality. To review NAP server events in Event Viewer 1. Click Start and then click Run. 2. Type eventvwr.msc, and press ENTER. 3. In the left tree, navigate to Event Viewer(Local)\Custom Views\Server Roles\Network Policy and Access Services. 4. Click an event in the middle pane. 5. By default, the General tab is displayed. Click the Details tab to view additional information. 6. You can also right-click an event and then click Event Properties to open a new window for reviewing events.

46