Use Group Policy to configure clients for Network Access Protection

Network Access Protection is another tool in your arsenal to protect your networks. With it, you have the ability to make sure your defenses are on, stay on, and are up to date. NAP also provides you the tools to help make remediation of any problems automatic.

Your clients needs to have several configuration changes made to the in order to respond to NAP. They are:

- Security Center must be turned on.

- The NAP Service must be running.

- The proper NAP Enforcement Client must be enabled.

You can achieve this using group policy. Just make sure this GPO is applied to all your clients.

Security Center: Computer Configuration \ Policies \ Administrative Templates \ Windows Components \ Security Center \ Turn on Security Center (Domain PCs Only). Set this object to Enabled.

NAP Service: Computer Configuration \ Policies \ Windows Settings \ System Services \ Network Access Protection Agent. Check Define the Policy and then select Automatic.

NAP Enforcement Client: Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Network Access Protection \ NAP Configuration \ Enforcement Clients. Double Client the Enforcement Client you will be setting up and Enable it.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog