<?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>Find out how Microsoft deployed Windows Server 2008 (BETA 3) to run Microsoft.com</title><link>http://blogs.msdn.com/publicsector/archive/2007/06/28/find-out-how-microsoft-deployed-windows-server-2008-beta-3-to-run-microsoft-com.aspx</link><description>If you or your company is thinking about what Windows Server 2008 (code name: Longhorn) in your environment, but are not quite sure what to expect from a scalability and availability perspective. Well, check out how the Microsoft.com team is putting their</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>www.microsoft.com Now Running on Server 2008 Beta 3</title><link>http://blogs.msdn.com/publicsector/archive/2007/06/28/find-out-how-microsoft-deployed-windows-server-2008-beta-3-to-run-microsoft-com.aspx#3720805</link><pubDate>Fri, 06 Jul 2007 07:59:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3720805</guid><dc:creator>Realtime Community | Windows Server</dc:creator><description>&lt;p&gt;Microsoft has always followed the &amp;quot;dog food&amp;quot; policy, forcing their updates down their own throats before ever releasing them onto the unwashed masses. That gives them street cred for putting up with their own pre-release software before we have to, and&lt;/p&gt;
</description></item></channel></rss>