<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Hyper-V VLANs part II</title><link>http://blogs.msdn.com/adamfazio/archive/2009/06/23/hyper-v-vlans-part-ii.aspx</link><description>In my first post on Hyper-V VLANs, I talked about the most common scenario for VLANs with Hyper-V, which is using VLAD IDs on the Virtual Machines or the Hyper-V Virtual Switch. Now that I’ve been around the block a few times working with enterprise customers</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Hyper-V VLANs part II</title><link>http://blogs.msdn.com/adamfazio/archive/2009/06/23/hyper-v-vlans-part-ii.aspx#9801815</link><pubDate>Wed, 24 Jun 2009 20:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9801815</guid><dc:creator>BP Sullivan</dc:creator><description>&lt;p&gt;Awesome article. Being that I have an IQ of 26, it's quite hard to believe that I can type, let alone read. Keep up the great work.&lt;/p&gt;</description></item></channel></rss>