<?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>Remotely connecting to a Hyper-V virtual machine with networking disabled</title><link>http://blogs.msdn.com/granth/archive/2008/11/10/remotely-connecting-to-a-hyper-v-virtual-machine-with-networking-disabled.aspx</link><description>In a previous blog post, I explained the steps to convert the VS2010 CTP VPC from Virtual PC to Hyper-V . When using virtual machines, sometimes you don’t want them to be connected to any network. This is especially true with the Team Foundation Server</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Remotely connecting to a Hyper-V virtual machine with networking disabled</title><link>http://blogs.msdn.com/granth/archive/2008/11/10/remotely-connecting-to-a-hyper-v-virtual-machine-with-networking-disabled.aspx#9141940</link><pubDate>Tue, 25 Nov 2008 17:06:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9141940</guid><dc:creator>wma</dc:creator><description>&lt;p&gt;The only thing I would add is that the user experience is better with Remote Desktop vs. VMConnect. &amp;nbsp;An internal network connection would at least allow you to use RDP.&lt;/p&gt;
&lt;p&gt;My 2 cents.&lt;/p&gt;
</description></item></channel></rss>