<?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: Meeting Request</title><link>http://blogs.technet.com/b/meamcs/archive/2012/10/10/challenges-of-migration-from-groupwise-to-exchange-2010-meeting-request.aspx</link><description>The previous article explained the first challenge which is co-existence: Challenges of Migration from GroupWise to Exchange 2010: Co-Existence In this article I will talk about one of the most annoying problems that may affect the migration which is</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: Meeting Request</title><link>http://blogs.technet.com/b/meamcs/archive/2012/10/10/challenges-of-migration-from-groupwise-to-exchange-2010-meeting-request.aspx#3525202</link><pubDate>Wed, 10 Oct 2012 14:56:39 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3525202</guid><dc:creator>Chad Lindley, Senior Product Manager, Quest Software - now part of Dell</dc:creator><description>&lt;p&gt;Thanks Mohamed. This is an important step to ensure seamless coexistence. When 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;) to synchronize directories, this property is automatically set to ensure GroupWise users receive proper invitations. &lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3525202" width="1" height="1"&gt;</description></item></channel></rss>