<?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>Challenges of Migration from GroupWise to Exchange 2010: Co-Existence</title><link>http://blogs.technet.com/b/meamcs/archive/2012/10/08/challenges-of-migration-from-groupwise-to-exchange-2010-co-existence.aspx</link><description>This article will discuss a high level overview about the migration from GroupWise to Exchange 2010. &amp;#160; The following steps summarize the migration process from GroupWise to Exchange 2010: 1. Design Exchange 2010. 2. Implement and configure Exchange</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Challenges of Migration from GroupWise to Exchange 2010: Co-Existence</title><link>http://blogs.technet.com/b/meamcs/archive/2012/10/08/challenges-of-migration-from-groupwise-to-exchange-2010-co-existence.aspx#3547523</link><pubDate>Tue, 22 Jan 2013 16:32:59 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3547523</guid><dc:creator>AmirDC</dc:creator><description>&lt;p&gt;Based on my conversation with Dell, to use Quest Coexistence Manager, one has to engage Dell/Quest Services ($), or an authorized partner ($).&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3547523" width="1" height="1"&gt;</description></item><item><title>re: Challenges of Migration from GroupWise to Exchange 2010: Co-Existence</title><link>http://blogs.technet.com/b/meamcs/archive/2012/10/08/challenges-of-migration-from-groupwise-to-exchange-2010-co-existence.aspx#3543724</link><pubDate>Wed, 02 Jan 2013 22:30:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3543724</guid><dc:creator>Konrad Sagała</dc:creator><description>&lt;p&gt;Very useful article, much better than CMG user guide.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3543724" width="1" height="1"&gt;</description></item><item><title>re: Challenges of Migration from GroupWise to Exchange 2010: Co-Existence</title><link>http://blogs.technet.com/b/meamcs/archive/2012/10/08/challenges-of-migration-from-groupwise-to-exchange-2010-co-existence.aspx#3525266</link><pubDate>Wed, 10 Oct 2012 18:52:52 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3525266</guid><dc:creator>Chad Lindley, Senior Product Manager, Quest Software - now part of Dell</dc:creator><description>&lt;p&gt;Great outline of the routing configuration between GroupWise and Exchange.&lt;/p&gt;
&lt;p&gt;It may also be helpful to note that a more robust experience is possible using Coexistence Manager for GroupWise (&lt;a rel="nofollow" target="_new" href="http://www.quest.com/coexistence-manager-for-groupwise/"&gt;www.quest.com/coexistence-manager-for-groupwise&lt;/a&gt;) including dirsync, bi-directional free/busy queries, and enhance calendar interoperability including custom recurring meetings and meeting reschedules.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3525266" width="1" height="1"&gt;</description></item></channel></rss>