<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Microsoftâ€™s Unified Communications â€œStrategyâ€</title>
	<atom:link href="http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/feed/" rel="self" type="application/rss+xml" />
	<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/</link>
	<description>A daily round table on the tech industry with experts and callers from all over the globe. Join us as we pick apart the news and get to the meat of what\'s happening out there.</description>
	<pubDate>Fri, 16 May 2008 02:57:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: CisteraNucleusBlog</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-22079</link>
		<dc:creator>CisteraNucleusBlog</dc:creator>
		<pubDate>Fri, 30 Jun 2006 20:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-22079</guid>
		<description>&lt;strong&gt;More Microsoft Strategy for Unified Communications...&lt;/strong&gt;

Unlike Alex Saunders I am not prepared to go this far. As I have stated previously there is more to building a PBX than meets the eye, and it is something that Cisco has been working on since 1998......</description>
		<content:encoded><![CDATA[<p><strong>More Microsoft Strategy for Unified Communications&#8230;</strong></p>
<p>Unlike Alex Saunders I am not prepared to go this far. As I have stated previously there is more to building a PBX than meets the eye, and it is something that Cisco has been working on since 1998&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: -- Alec Saunders .LOG</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21986</link>
		<dc:creator>-- Alec Saunders .LOG</dc:creator>
		<pubDate>Fri, 30 Jun 2006 11:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21986</guid>
		<description>[...] It&#8217;s hard to disagree, and that&#8217;s the reason I called the announcement a damp squib. It&#8217;s the intersection of the fundamentals of presence and business processes that will provide the value that customers are looking for.Â  That intersection will happen in three phases: [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] It&#8217;s hard to disagree, and that&#8217;s the reason I called the announcement a damp squib. It&#8217;s the intersection of the fundamentals of presence and business processes that will provide the value that customers are looking for.Â  That intersection will happen in three phases: [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mail from Microsoftâ€™s Kyle Marsh -- Alec Saunders .LOG</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21917</link>
		<dc:creator>Mail from Microsoftâ€™s Kyle Marsh -- Alec Saunders .LOG</dc:creator>
		<pubDate>Fri, 30 Jun 2006 02:32:10 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21917</guid>
		<description>[...] A couple of days after I wrote Microsoftâ€™s Unified Communications â€œStrategyâ€, I got a nice note from Kyle Marsh, unified communications evangelist. He gave some additional details about the products, as well as correcting a mistake I made. I understood that Exchange would be renamed Microsoft Communcations Server, which in fact is not the case. He also invited us to participate in a developer lab in Redmond at the end of the month. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] A couple of days after I wrote Microsoftâ€™s Unified Communications â€œStrategyâ€, I got a nice note from Kyle Marsh, unified communications evangelist. He gave some additional details about the products, as well as correcting a mistake I made. I understood that Exchange would be renamed Microsoft Communcations Server, which in fact is not the case. He also invited us to participate in a developer lab in Redmond at the end of the month. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21549</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Wed, 28 Jun 2006 15:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21549</guid>
		<description>IBM is doing it right:

http://smeit.com.sg/ShowPage.aspx?pagetype=2&#38;articleid=3865&#38;pubid=3&#38;tab=Home&#38;issueid=92</description>
		<content:encoded><![CDATA[<p>IBM is doing it right:</p>
<p><a href="http://smeit.com.sg/ShowPage.aspx?pagetype=2&amp;articleid=3865&amp;pubid=3&amp;tab=Home&amp;issueid=92" rel="nofollow">http://smeit.com.sg/ShowPage.aspx?pagetype=2&amp;articleid=3865&amp;pubid=3&amp;tab=Home&amp;issueid=92</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21364</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Tue, 27 Jun 2006 21:44:59 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21364</guid>
		<description>Microsoft is not renaming Exchange to Office Communications Server.  They will remain separate products.</description>
		<content:encoded><![CDATA[<p>Microsoft is not renaming Exchange to Office Communications Server.  They will remain separate products.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the rant trap &#187; Blog Archive &#187; Microsoft&#8217;s &#8220;Me Too&#8221; Attempt to Jump into VoIP</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21305</link>
		<dc:creator>the rant trap &#187; Blog Archive &#187; Microsoft&#8217;s &#8220;Me Too&#8221; Attempt to Jump into VoIP</dc:creator>
		<pubDate>Tue, 27 Jun 2006 15:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21305</guid>
		<description>[...] Alec Saunders is the CEO of Iotum&#8230;one of the coolest products for productivity ever made.Â  They build a &#8220;Relevance Engine&#8221; which promises to manage your phone calls in a way that allow you to recieve the calls you want to recieve when you want to recieve them.Â  Sort of like an electronic Executive Assistant.Â  I looked to him for commentary because part of the MS strategy aims at his product specifically.Â  By the way, I believe Alec is an ex MicroSoftie&#8230;someone correct me if I&#8217;m wrong on that.Â  His blog can be found here.Â  I would say his commentary is the best I&#8217;ve seen out of a group of good stuff. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Alec Saunders is the CEO of Iotum&#8230;one of the coolest products for productivity ever made.Â  They build a &#8220;Relevance Engine&#8221; which promises to manage your phone calls in a way that allow you to recieve the calls you want to recieve when you want to recieve them.Â  Sort of like an electronic Executive Assistant.Â  I looked to him for commentary because part of the MS strategy aims at his product specifically.Â  By the way, I believe Alec is an ex MicroSoftie&#8230;someone correct me if I&#8217;m wrong on that.Â  His blog can be found here.Â  I would say his commentary is the best I&#8217;ve seen out of a group of good stuff. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The PhoneBoy Blog</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21219</link>
		<dc:creator>The PhoneBoy Blog</dc:creator>
		<pubDate>Tue, 27 Jun 2006 06:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21219</guid>
		<description>&lt;strong&gt;Alec Sanders Responds to the Microsoft "Threat"...&lt;/strong&gt;

Now I will admit to not having read all the various information about Microsoft's entry into Unified Communications, though I did hear about it on today's KenRadio episode. Alec Saunders, the CEO......</description>
		<content:encoded><![CDATA[<p><strong>Alec Sanders Responds to the Microsoft &#8220;Threat&#8221;&#8230;</strong></p>
<p>Now I will admit to not having read all the various information about Microsoft&#8217;s entry into Unified Communications, though I did hear about it on today&#8217;s KenRadio episode. Alec Saunders, the CEO&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://saunderslog.com/2006/06/26/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21169</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 27 Jun 2006 01:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/1969/12/31/microsoft%e2%80%99s-unified-communications-%e2%80%9cstrategy%e2%80%9d/#comment-21169</guid>
		<description>Microsoft's entry into this market is not a wise move at all, Exchange is a moneymaker for them plain and simple - if it ain't broke..., forcing any type of telephony solution on Data VAR's who have pre-existing relationships with PBX manufacturer's is a big mistake, the right strategy is to complement the existing sales channel, which so many Microsoft/PBX partners have done very well for a long time now.

Adding Fax/Voice/IM resources to Exchange has been so glaringly absent for so long, it will take M$ the full ten years to catch up to the partner market, and then only to realize they are not equipped to play in that world.

Maybe they should buy Nortel?  :)</description>
		<content:encoded><![CDATA[<p>Microsoft&#8217;s entry into this market is not a wise move at all, Exchange is a moneymaker for them plain and simple - if it ain&#8217;t broke&#8230;, forcing any type of telephony solution on Data VAR&#8217;s who have pre-existing relationships with PBX manufacturer&#8217;s is a big mistake, the right strategy is to complement the existing sales channel, which so many Microsoft/PBX partners have done very well for a long time now.</p>
<p>Adding Fax/Voice/IM resources to Exchange has been so glaringly absent for so long, it will take M$ the full ten years to catch up to the partner market, and then only to realize they are not equipped to play in that world.</p>
<p>Maybe they should buy Nortel?  :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
