Checklist: Creating Rules for Clients of a Standalone Isolated Server Zone

Applies To: Windows 7, Windows Essential Business Server, Windows SBS 2003, Windows SBS 2008, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Vista

This checklist includes tasks for configuring connection security rules and IPsec settings in the GPOs for client computers that must connect to servers in an isolated server zone. The way in which these rules and settings are configured depends on whether the computers to which the GPO applies are running Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2 or an earlier version of the Windows operating system.

In this topic:

  • Checklist for Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2

  • Checklist for Windows XP, Windows Server 2003, and Windows 2000

Checklist: Configuring isolated server zone client rules for computers running Windows 7, Windows Vista, Windows Server 2008, or Windows Server 2008 R2

Note

The GPOs for computers running Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2 are usually similar. If this is true for your design, create one GPO, configure it by using the tasks in this checklist, and then create a copy of the GPO. For example, create and configure the GPO for Windows 7, create a copy of it for Windows Server 2008 R2, and then follow the steps in this checklist to make the required changes (if any) to the copy.

Task Reference

Create a GPO for the client computers that must connect to servers in the isolated server zone, and that are running one of the versions of Windows. After you have finished the tasks in this checklist, you can make a copy of it.

Checklist: Creating Group Policy Objects

Copy a GPO to Create a New GPO

To determine which computers receive the GPO, assign the NAG for the isolated servers to the security group filter for the GPO. Make sure that each GPO has the WMI filter for the correct version of Windows.

Modify GPO Filters to Apply to a Different Zone or Version of Windows

Configure IPsec to exempt all ICMP network traffic from IPsec protection.

Exempt ICMP from Authentication on Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2

Create a rule that exempts all network traffic to and from computers on the exemption list from IPsec.

Create an Authentication Exemption List Rule on Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2

Configure the key exchange (main mode) security methods and algorithms to be used.

Configure Key Exchange (Main Mode) Settings on Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2

Configure the data protection (quick mode) algorithm combinations to be used.

Configure Data Protection (Quick Mode) Settings on Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2

Configure the authentication methods to be used.

Configure Authentication Methods on Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2

Create a rule that requests authentication for network traffic. Because fallback-to-clear behavior in Windows Vista and Windows Server 2008 has no delay when communicating with computers that cannot use IPsec, you can use the same any-to-any rule used in an isolated domain.

Create an Authentication Request Rule on Windows 7, Windows Vista, Windows Server 2008, and Windows Server 2008 R2

Link the GPO to the domain level of the Active Directory organizational unit hierarchy.

Link the GPO to the Domain

Add your test computers to the NAG for the isolated server zone. Be sure to add at least one for each operating system supported by a different GPO in the group.

Add Test Computers to the Membership Group for a Zone

Checklist: Configuring isolated server zone client rules for computers running Windows XP, Windows Server 2003, or Windows 2000

Note

The GPOs for computers that run Windows Server 2003, Windows XP, and Windows 2000 are usually similar. If this is true for your design, create one GPO, configure it by using the tasks in this checklist, and then make a copy of the GPO to capture all of the settings. For example, create and configure the GPO for Windows XP, create a copy of it for Windows Server 2003, and then follow the steps in this checklist to make the few required changes to the copy.

Task Reference

Create a GPO for the client computers that must connect to servers in the isolated server zone, and that are running one of the versions of Windows. After you have finished the tasks in this checklist and configured the GPO for one version of Windows, you can create a copy of it. To determine which computers receive the GPO, assign the NAG for the isolated servers to the security group filter for the GPO.

Create a Group Policy Object

Copy a GPO to Create a New GPO

To determine which computers receive the GPO, assign the NAG for the isolated servers to the security group filter for the GPO. Make sure that each GPO has the WMI filter for the correct version of Windows.

Modify GPO Filters to Apply to a Different Zone or Version of Windows

Add registry settings that optimize IPsec behavior to the GPO.

Configure Settings to Optimize IPsec Behavior on Earlier Versions of Windows

Create a new IP Security policy in the GPO.

Create a New IP Security Policy in a GPO for Earlier Versions of Windows

Configure the key exchange (main mode) security methods and algorithms to be used.

Configure Key Exchange (Main Mode) Settings on Earlier Versions of Windows

Create IP filter lists for ICMP traffic, the exemption list, and all other IP traffic. This filter list is potentially different from the filter list for an isolated domain.

Create Filter Lists for Clients of Isolated Server Running Earlier Versions of Windows

Create filter actions to allow traffic and request authentication. If the isolated servers require encryption, make sure that you include the appropriate encryption algorithms in the data protection (quick mode) settings of the request filter action.

Create Filter Actions on Earlier Versions of Windows

Combine the filter lists and filter actions into the required IPsec rules.

Create IPsec Rules for an Isolated Domain on Earlier Versions of Windows

Assign the IPsec policy for the isolated domain to your GPO.

Assign an IPsec Policy to a GPO for Earlier Versions of Windows

Link the GPO to the domain level of the Active Directory organizational unit hierarchy.

Link the GPO to the Domain

Add your test computers to the membership group for the isolated domain. Be sure to add at least one for each operating system supported by a different GPO in the group.

Add Test Computers to the Membership Group for a Zone

Verify that the connection security rules are protecting your network traffic.

Verify That Network Traffic Is Authenticated

Do not change the rules for any of your zones to require authentication until all of the zones have been set up and thoroughly tested.