Network Access Protection - Windows Server 2008

I am looking to better understand at what stage the NAP client initializes during the windows OS startup process.  At some point during the winlogon initialization, the NAP client reports system status to the NAP enforcement server. If the NAP client logging in meets the
NPS requirements, it will be allowed to log into the network.  Does this occur prior to establishing a secure channel to the domain controller? Since NAP is a window service, I would imagine that the service control manager starts prior to the NAP client.  Any insight you could provide would be much appreciated.
novanationAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Sushil SonawaneConnect With a Mentor Commented:
0
 
NisheshPrasadConnect With a Mentor Commented:
Hi

We know that NAP is enforced against certain services that the Domain Provides. For example - DHCP or Wireless.

Lets take DHCP as an example.

If NAP is enforced on a DHCP Scope, what it essentially implies is that before your clients can get an IP Address from the Windows DHCP Server, the DHCP Server would point your clients to the NAP Enforcement Server to "pass or meet" the NAP Policies.

Now - how do you "Enforce" the Clients to go through a NAP Server. In other words - how do you ensure that the NAP Agent will do what it is supposed to do and when it is supposed to do it ? You configure Group Policies to enable the NAP Agent on each client and ALSO you configure the "type" of NAP Enforcement you want to put in place - in this case DHCP Quarantine Enforcement.

To achieve the above scenario - your clients "WILL" have to connect to a Domain Controller and Process its GPOs first - and to do this there "WILL" be a secured a channel created first between the client and the domain controller BEFORE the client even reaches a NAP Server for Policy Enforcements.

Hope this helps.
0
All Courses

From novice to tech pro — start learning today.