Posted By: adambomb | Oct 10th, 2007 @ 2:35 PM | 19,235 Views | 16 Comments
After months of cajoling, Adam was finally able to convince Jeff Sigman from the NAP team and Brent Atkison from MSIT to sit still for 30 minutes to talk about why we created NAP, and how we went about deploying it worldwide at Microsoft.  Ah, who am I kidding.  Jeff's been asking me for months to put his blue anime hair up on Channel9.  Here you go Jeff.  Persistance pays off.
Network Access Protection is a new feature in Windows Server 2008 that allows you to enforce computer health requirements before allowing machines to communicate on the network.  It's the answer to the question "do I trust that this machine is patched and won't infect other machines on my network?"
These guys have done some pretty impressive stuff.  The NAP team worked with a list of partners as long as your arm to make sure NAP will play nicely with whatever switch hardware you've invested in.  Brent shares some impressive sizing guidelines for implementing NAP:  Microsoft turned reporting and deferred enforcement on 120,000 machines worldwide, using a very small number of servers.  Very small.  Less than 3.  Total help desk calls as a result?  Also a very small number.  Oh, and he did that deployment using beta builds of Longhorn Server 2008.
Media Downloads:
Rating:
0
0
If NAP prevents a non-healthy computer from acquiring an ip address i.e. lacking Windows patches or an antivirus, then how is it able to acquire them conveniently?

Or is it connected to another server exclusively dedicated to this function?
It does not prevent you from acquiring an IP address - it provides an IP with a set of settings that prevents you from communicating with any machines on the network other than those specified via the access policy.  These are termed as 'fixup servers'.

Please see documents/whitepapers/other info at http://www.microsoft.com/nap for more information.

-Chris
NAPDude
NAPDude
NAP'ing the World
No comment (oh wait) on Adam's hair (or lack thereof), since he had to mention mine!


Jeff Sigman


PS - Thanks to Adam for making this video happen! Let us know if you like it and we can continue a series all about NAP. Make sure to check out the NAP blog.
Any key differences between this and any standard NAC appliance?
Enterprise CA required or Standalone okay to test?
NAPDude
NAPDude
NAP'ing the World

Hey Matt, good question.

1.) Integrated client available in XP SP3 and Vista.
2.) Able to enforce NAP orthogonally to the logged-on user (since it is an NT service).
3.) 3rd parties can build on top of client and server and extend the scope of what "health" means.
4.) The TCG adopted our Statement of Health (SoH) protocol as a standard - anyone can read the standard and interoperate.
5.) Check out this demo video I made to get a better idea of the experience.

I hope you try it out for yourself!


Jeff Sigman
Senior Program Manager - NAP

ZippyV
ZippyV
Fired Up
So, a networking guy hit by blaster because he didn't have his firewall on. Hmmm, fake story!
NAPDude wrote:


Hey Matt, good question.

1.) Integrated client available in XP SP3 and Vista.
2.) Able to enforce NAP orthogonally to the logged-on user (since it is an NT service).
3.) 3rd parties can build on top of client and server and extend the scope of what "health" means.
4.) The TCG adopted our Statement of Health (SoH) protocol as a standard - anyone can read the standard and interoperate.
5.) Check out this demo video I made to get a better idea of the experience.

I hope you try it out for yourself!


Jeff Sigman
Senior Program Manager - NAP



The live meeting site says that the webcast has expired.
Microsoft Communities