<?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>Updating a web site to apply a security patch with the help of Hyper-V</title><link>http://blogs.msdn.com/tom/archive/2008/09/11/updating-a-web-site-to-apply-a-security-patch-with-the-help-of-hyper-v.aspx</link><description>With the release of the latest security updates, it made me think about how painful it is to have to reboot a server because of applying a security update.&amp;#160; You have to balance the need to stay secure, with keeping your server up and running.&amp;#160;</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>A Best Practice approach to updating Hyper-V environments</title><link>http://blogs.msdn.com/tom/archive/2008/09/11/updating-a-web-site-to-apply-a-security-patch-with-the-help-of-hyper-v.aspx#9153230</link><pubDate>Fri, 28 Nov 2008 23:33:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9153230</guid><dc:creator>The things that are better left unspoken</dc:creator><description>&lt;p&gt;Updating environments with Hyper-V can be more of a challenge compared to updating an environment that&lt;/p&gt;
</description></item></channel></rss>