Checklist: Implementing a Standalone Server Isolation Policy Design

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 contains procedures for creating a server isolation policy design that is not part of an isolated domain. For the steps required to create an isolated server zone within an isolated domain, see Checklist: Configuring Rules for an Isolated Server Zone.

This parent checklist includes cross-reference links to important concepts about the domain isolation policy design. It also contains links to subordinate checklists that will help you complete the tasks that are required to implement this design.

Note

Complete the tasks in this checklist in order. When a reference link takes you to a procedure, return to this topic after you complete the steps in that procedure so that you can proceed with the remaining tasks in this checklist.
The procedures in this section use the Group Policy MMC snap-in interfaces to configure the GPOs, but you can also use the Netsh command-line tool. For more information, see Use Netsh to Configure GPOs.

Checklist: Implementing a standalone server isolation policy design

	Task	Reference
	Review important concepts and examples for the server isolation policy design to determine if this design meets your deployment goals and the needs of your organization.	Identifying Your Windows Firewall with Advanced Security Deployment Goals Server Isolation Policy Design Server Isolation Policy Design Example Planning Server Isolation Zones
	Create the GPOs and connection security rules for isolated servers.	Checklist: Configuring Rules for Servers in a Standalone Isolated Server Zone
	Create the GPOs and connection security rules for the client computers that must connect to the isolated servers.	Checklist: Creating Rules for Clients of a Standalone Isolated Server Zone
	Verify that the connection security rules are protecting network traffic on your test computers.	Verify That Network Traffic Is Authenticated
	After you confirm that network traffic is authenticated by IPsec as expected, you can change authentication rules for the isolated server zone to require authentication instead of requesting it.	Change Rules from Request to Require Mode
	According to the testing and roll-out schedule in your design plan, add computer accounts for the client computers to the membership group so that you can deploy the settings.	Add Production Computers to the Membership Group for a Zone