Windows Server 2012 R2 and Windows Server 2016 include features to help protect your network from malicious activity and data loss. Windows Server 2012 R2 and Windows Server 2016 include a Network Access Protection (NAP) feature that helps protect your network by verifying the identity of clients and authorizing access to resources.
To configure NAP on a Windows Server 2012 R2 or Windows Server 2016 server:
1. Open Server Manager.
2. In the left navigation pane, click Network and Sharing Center.
3. In the Network and Sharing Center window, under Manage Services, click NAP.
4. In the NAP window, under Configure NAP, click Enable NAP.
5. In the NAP window, under Configure NAP, under Settings, click Add Client.
6. In the Add Client window, under Select Client Type, select Windows 10, 8.
1, or 8.
7. In the Add Client window, under Select Client Location, select the location where the client computer is located.
8. In the Add Client window, under Select Client Security Level, select the level of security that the client computer must meet.
9. In the Add Client window, under Select Client Certificate, select the certificate that the client computer must have.
10. In the Add Client window, under Select Client Session, select the session that the client computer must have.
11. In the Add Client window, under Configure required settings, click Configure.
12. In the Configure required settings window, under Authentication Methods, select Windows 10, 8.
13. Under Authorization Methods, select Windows 10, 8.
14. Under Authorization Rules, under Require User To Enter A Password, select the check box.
15. Under Authorization Rules, under Require User To Log On With A User Name And Password, select the check box.
16. Under Authorization Rules, under Require User To Log On Using A Certificate, select the check box.
17. Under Authorization Rules, under Require User To Log On Using A Kerberos Ticket, select the check box.
18. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Session Host, select the check box.
19. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Client, select the check box.
20. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Web Access Session, select the check box.
21. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Web Access Client, select the check box.
22. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Web Access Application, select the check box.
23. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Web Access Session Host, select the check box.
24. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Web Access Client Host, select the check box.
25. Under Authorization Rules, under Require User To Use A Specific Remote Desktop Web Access Application Host, select the check box.
26.
27.
28.
29.
30.
31.
32.
33.
34. Under Authorization Rules, under Require User To Sign In Using A Microsoft Account, select the check box.
35. Under Authorization Rules, under Require User To Sign In Using A Local Account, select the check box.
36. Under Authorization Rules, under Require User To Use A Specific User Principal Name, select the check box.
37. Under Authorization Rules, under Require User To Use A Specific User Domain, select the check box.
