<?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>The business case for Exchange 2007</title><link>http://blogs.technet.com/ewan/archive/2007/06/29/the-business-case-for-exchange-2007.aspx</link><description>(this is a follow on to the previous post on measuring business impact , and are my own thoughts on the case for moving to Exchange 2007) There are plenty of resources already published which talk about the top reasons to deploy, upgrade or migrate to</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>The business case for Exchange 2007 - part II</title><link>http://blogs.technet.com/ewan/archive/2007/06/29/the-business-case-for-exchange-2007.aspx#1588120</link><pubDate>Mon, 23 Jul 2007 18:40:10 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1588120</guid><dc:creator>The Electric Wand</dc:creator><description>&lt;p&gt;(This is a follow on to the previous post on measuring business impact , and the first post on the business&lt;/p&gt;
</description></item><item><title>Exchange 2010 beta &amp; high availability strategies</title><link>http://blogs.technet.com/ewan/archive/2007/06/29/the-business-case-for-exchange-2007.aspx#3226670</link><pubDate>Wed, 15 Apr 2009 13:43:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3226670</guid><dc:creator>The Electric Wand</dc:creator><description>&lt;p&gt;Exchange 2010 beta released - significant changes to architecture of clustering and high availability make provisioning highly available servers simpler and less expensive.&lt;/p&gt;
</description></item></channel></rss>