Posted By: Jeff Alexander | Aug 20th @ 12:01 AM

One of the most important features of Windows Server 2008 is Network Access Protection.  In it’s simplest terms NAP is a platform Windows Server 2008 and Windows Vista for implementing client health requirements on your network. We all know that clients become unhealthy for many reasons.  NAP enforces client health requirements that you defines to make sure that your PC’s in your environment stay healthy. I’ve done presentations and demo’s on this many times so I thought it was about time to to turn the demo’s I’ve done into a screencast.  So I needed to break this down into 2 parts.  In part 1 of this screencast I’m going to to take you through some of the things you need to do to configure NAP for 802.1x authentication; including the switch confirguration; domain setup and NAP setup in Windows Server 2008. 

In part 2 I’ll show you NAP in action and what it looks like from the client perspective plus some of the events that occur at the server end and on the client.

Jeff Alexander

Rating:
1
0
The video is so blurry at full screen it is unwatchable for me.
selecting the WMV (High) option from downloads is a much more watchable full screen experience.
Agree. That is night and day different.

I already putted the NAP with 802.1x enforcement in production both in wired and wireless networks (really it works great for the wireless ....).  I was waiting till final released for 2008, some efforts I managed to configure with both 3 Com and Cisco switches. Really it gives a good presentation for situation of the domain join computers (not to mention security and dynamic switching).

Now I’m having some conflict issues with the GPOs for the wireless networks for domain joined computers but I think I will fix it...

 

Too much to say for the NAP solution..... a good testimonial for Microsoft for our campus.... Really good job

shkumbini