Checklist: Creating Rules for Clients of a Standalone Isolated Server Zone
Applies To: Windows Server 2012
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.
Checklist: Configuring isolated server zone client rules for computers running Windows 8, Windows 7, Windows Vista, Windows Server 2012, Windows Server 2008, or Windows Server 2008 R2
Note
The GPOs for computers running Windows 8, Windows 7, Windows Vista, Windows Server 2012, 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 8, create a copy of it for Windows Server 2012, 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. |
||
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. |
||
Create a rule that exempts all network traffic to and from computers on the exemption list from IPsec. |
||
Configure the key exchange (main mode) security methods and algorithms to be used. |
||
Configure the data protection (quick mode) algorithm combinations to be used. |
||
Configure the authentication methods to be used. |
||
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. |
||
Link the GPO to the domain level of the Active Directory organizational unit hierarchy. |
||
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. |