network access protectionextreme, Joey, neil, AdamBombhttp://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/Edge/images/feedimage.pnghttp://edge.technet.com/Tags/Network+Access+Protection/network access protectionhttp://edge.technet.com/Tags/Network+Access+Protection/en-usSun, 31 Aug 2008 11:03:20 GMTSun, 31 Aug 2008 11:03:20 GMTEvNet (EvNet, Version=1.0.3186.2534, Culture=neutral, PublicKeyToken=null)<img src="http://edge.technet.com/Link/e97080ed-7d8d-4135-843e-2a99b7473267/" border="0" />Hello again,<br /> <br /> In my previous post on Network Access Protection I showed you how to configure the server and get the switch going for 802.1x authentication.  In this Screencast I'm going to look at what happens at the client end so you can see how to configure a Windows Vista client and then look at some of the events that get logged when a client moves in and out of health.<br /> <br /> Enjoy!<img src="http://edge.technet.com/1623/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" />http://edge.technet.com/Media/Screencast-Network-Access-Protection-Part-2/Hello again, In my previous post on Network Access Protection I showed you how to configure the server and get the switch going for 802.1x authentication.  In this Screencast I'm going to look at what happens at the client end so you can see how to configure a Windows Vista client and then look at some of the events that get logged when a client moves in and out of health. Enjoy!http://edge.technet.com/Media/Screencast-Network-Access-Protection-Part-2/Mon, 01 Sep 2008 01:20:00 GMThttp://edge.technet.com/Media/Screencast-Network-Access-Protection-Part-2/10538http://edge.technet.com/1623/WebViewBug.aspx?EVT=0Hello again, In my previous post on Network Access Protection I showed you how to configure the server and get the switch going for 802.1x authentication.  In this Screencast I'm going to look at what happens at the client end so you can see how to configure a Windows Vista client and then look at&#8230;jeffadudejeffadude1http://edge.technet.com/Media/Screencast-Network-Access-Protection-Part-2/RSS/http://edge.technet.com/1623/Trackback.aspxNetwork Access ProtectionSecurityWindows Server 2008<img src="http://mschnlnine.vo.llnwd.net/d1/edge/5/5/5/1/napjeffa1_small_edge.jpg" border="0" /><p>One of the most important features of <a href="http://www.microsoft.com/windowsserver2008/en/us/default.aspx">Windows Server 2008</a> is <a href="http://www.microsoft.com/windowsserver2008/en/us/nap-product-home.aspx">Network Access Protection</a>.  In it’s simplest terms NAP<a href="http://edge.technet.comfile:///C:/Users/jeffa/AppData/Local/Temp/WindowsLiveWriter1286139640/supfiles5CB700/Windows%20Server%202008%20logo%20v[9].png></a> 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.  </p> <p>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.<br /> <br /> Jeff Alexander</p><img src="http://edge.technet.com/1555/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" />http://edge.technet.com/Media/Screencast-Network-Access-Protection-with-8021x-Part-1/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 Alexanderhttp://edge.technet.com/Media/Screencast-Network-Access-Protection-with-8021x-Part-1/Wed, 20 Aug 2008 07:01:00 GMThttp://mschnlnine.vo.llnwd.net/d1/edge/5/5/5/1/napjeffa1_edge.mp48882http://edge.technet.com/1555/WebViewBug.aspx?EVT=0One 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…jeffadudejeffadude4http://edge.technet.com/Media/Screencast-Network-Access-Protection-with-8021x-Part-1/RSS/http://edge.technet.com/1555/Trackback.aspxClient HealthNAPNetwork Access ProtectionSecurityWindows Server 2008<img src="http://edge.technet.com/Link/858734ec-11a0-43e7-b065-e44408f4f8ab/" border="0" />In this screencast Corey Hynes walks us through Network Access Protection, but unlike normal demos we take a look from the client side.  Get a look at what actually occurs on a client machine as it goes in and out of compliance on a Windows Server 2008 network protected by Network Access Protection.<img src="http://edge.technet.com/841/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" />http://edge.technet.com/Media/Network-Access-Protection-Client-Side-Screencast/In this screencast Corey Hynes walks us through Network Access Protection, but unlike normal demos we take a look from the client side.  Get a look at what actually occurs on a client machine as it goes in and out of compliance on a Windows Server 2008 network protected by Network Access Protection.http://edge.technet.com/Media/Network-Access-Protection-Client-Side-Screencast/Fri, 18 Apr 2008 06:59:00 GMThttp://edge.technet.com/Media/Network-Access-Protection-Client-Side-Screencast/6803http://edge.technet.com/841/WebViewBug.aspx?EVT=0In this screencast Corey Hynes walks us through Network Access Protection, but unlike normal demos we take a look from the client side.JoeyJoey0http://edge.technet.com/Media/Network-Access-Protection-Client-Side-Screencast/RSS/http://edge.technet.com/841/Trackback.aspxNAPNetwork Access ProtectionWindows Server 2008<img src="http://mschnlnine.vo.llnwd.net/d1/edge/1/6/4/napmsit_small_edge.jpg" border="0" />After months of cajoling, I 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 the web. Here you go Jeff. Persistance pays off.<br />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?"<br />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.<br />(this video was originally posted to Channel9 back before Edge existed, but since it's really IT content, not dev, I wanted to put it up over where it belongs)<img src="http://edge.technet.com/461/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" />http://edge.technet.com/Media/Network-Access-Protection-with-Microsofts-IT/After months of cajoling, I 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 the web. 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.(this video was originally posted to Channel9 back before Edge existed, but since it's really IT content, not dev, I wanted to put it up over where it belongs)http://edge.technet.com/Media/Network-Access-Protection-with-Microsofts-IT/Tue, 15 Jan 2008 03:27:00 GMThttp://edge.technet.com/Media/Network-Access-Protection-with-Microsofts-IT/4895http://edge.technet.com/461/WebViewBug.aspx?EVT=0After months of cajoling, I 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 the web. Here you go Jeff. Persistance pays off.AdamBombAdamBomb2http://edge.technet.com/Media/Network-Access-Protection-with-Microsofts-IT/RSS/http://edge.technet.com/461/Trackback.aspxNAPNetwork Access ProtectionSecurityWindows ServerWindows Server 2008