<?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>Unified Communications licensing made easy</title><link>http://blogs.technet.com/ewan/archive/2007/12/14/unified-communications-licensing-made-easy.aspx</link><description>Well, hopefully. I get asked a lot about what licenses customer need when they want to deploy Exchange &amp;amp; Office Communications Server, in order to keep themselves legal &amp;amp; compliant. It's sometimes a bit confusing that there are several versions</description><dc:language>en-GB</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>CAL Suites..</title><link>http://blogs.technet.com/ewan/archive/2007/12/14/unified-communications-licensing-made-easy.aspx#2660110</link><pubDate>Wed, 19 Dec 2007 16:16:54 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2660110</guid><dc:creator>Dougs Blog &gt;&gt; Exchange Server in the field</dc:creator><description>&lt;p&gt;Just found a nice blog by Ewan Dalton on the subject of licensing, specifically concerning Unified Comms;&lt;/p&gt;
</description></item></channel></rss>