windows-itpro-docs/windows/keep-secure/change-rules-from-request-to-require-mode.md
2016-07-20 13:40:45 -07:00

2.3 KiB

title, description, ms.assetid, ms.prod, ms.mktglfcycl, ms.sitesec, ms.pagetype, author
title description ms.assetid ms.prod ms.mktglfcycl ms.sitesec ms.pagetype author
Change Rules from Request to Require Mode (Windows 10) Change Rules from Request to Require Mode ad969eda-c681-48cb-a2c4-0b6cae5f4cff w10 deploy library security brianlic-msft

Change Rules from Request to Require Mode

Applies to

  • Windows 10
  • Windows Server 2016

After you confirm that network traffic is being correctly protected by using IPsec, you can change the rules for the domain isolation and encryption zones to require, instead of request, authentication. Do not change the rules for the boundary zone; they must stay in request mode so that devices in the boundary zone can continue to accept connections from devices that are not part of the isolated domain.

Administrative credentials

To complete these procedures, you must be a member of the Domain Administrators group, or otherwise be delegated permissions to modify the GPOs.

In this topic:

To convert a rule from request to require mode

  1. Open the Group Policy Management Console to Windows Firewall with Advanced Security.

  2. In the navigation pane, click Connection Security Rules.

  3. In the details pane, double-click the connection security rule that you want to modify.

  4. Click the Authentication tab.

  5. In the Requirements section, change Authenticated mode to Require inbound and request outbound, and then click OK.

To apply the modified GPOs to the client devices

  1. The next time each device refreshes its Group Policy, it will receive the updated GPO and apply the modified rule. To force an immediate refresh, run the following command from an elevated command prompt:

    gpupdate /force
    
  2. To verify that the modified GPO is correctly applied to the client devices, you can run the following command:

    gpresult /r /scope computer
    
  3. Examine the command output for the list of GPOs that are applied to the device, and make sure that the list contains the GPOs you expect to see on that device.