Skip to main content

Q: In Network Access Protection, what happens if a compliant computer falls out of compliance while accessing data?

I had a lot of trouble finding a definitive answer to this one at Microsoft. Please take these comments of my interpretation of what happens from the following blog knowing that you may want to test this with your applications prior to deployment.

http://blogs.technet.com/nap/archive/2008/09/05/what-is-the-nap-client-doing.aspx

If you client falls out of compliancy in an NAP environment while you have open data from a network share, the result will be like if the server went down. Let’s say you open a Word document and are happily typing along. You client goes out of compliance and loses its connection to the network. Since the data is already loaded in Word, the user should be able to continue typing. If they try to save it, Word will not be able to access the location. They will have to save the changes locally until the client is back within compliance.

Comments

Popular posts from this blog

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...