<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Operating System Deployment in an 802.1x Environment</title><link>http://blogs.technet.com/b/wincat/archive/2010/03/24/operating-system-deployment-in-an-802-1x-environment.aspx</link><description>For those that have investigated, or deployed 802.1x port authentication on either a wireless or a wired network understand the benefits and additional security that such a solution offers. The ability to stop traffic at layer 2, at the port is a powerful</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Operating System Deployment in an 802.1x Environment</title><link>http://blogs.technet.com/b/wincat/archive/2010/03/24/operating-system-deployment-in-an-802-1x-environment.aspx#3382044</link><pubDate>Mon, 24 Jan 2011 10:50:10 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3382044</guid><dc:creator>Herbert</dc:creator><description>&lt;p&gt;Tough situation, only PXE is embraced by all and further developments made to remove the chicken and egg scenario, then it becomes a silverbullet. We are stuck too with failing to IP address because we cannot be authenticated.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3382044" width="1" height="1"&gt;</description></item></channel></rss>