<?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>Hyper-V and Windows 2008 on my laptop - how to deal with wireless networking</title><link>http://blogs.technet.com/gbordier/archive/2008/03/26/hyper-v-and-windows-2008-on-my-laptop-how-to-deal-with-networking.aspx</link><description>I received a few weeks ago my latest Microsoft laptop and as usual came the question of which OS to install it with. This time my focus was : go 64 bits and use our latest Windows Server OS, Windows Server 2008 which remarkably was getting out of the</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Hyper-V and Windows 2008 on my laptop - how to deal with wireless networking</title><link>http://blogs.technet.com/gbordier/archive/2008/03/26/hyper-v-and-windows-2008-on-my-laptop-how-to-deal-with-networking.aspx#3182815</link><pubDate>Thu, 15 Jan 2009 16:54:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3182815</guid><dc:creator>Graham</dc:creator><description>&lt;p&gt;This worked perfectly for me. &amp;nbsp;I have a laptop with windows server 2008 as a workstation with Hyper V installed. &amp;nbsp;I created the internal network and then bridged them and now my VM's can access the internet ok.&lt;/p&gt;
</description></item></channel></rss>