<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Emailmigrations.com &#187; Exchange 2007</title>
	<atom:link href="http://emailmigrations.com/category/exchange-2007/feed" rel="self" type="application/rss+xml" />
	<link>http://emailmigrations.com</link>
	<description>A real-world guide on how to achieve a successful email migration project</description>
	<lastBuildDate>Tue, 31 Jan 2012 21:10:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>GroupWise Migrations to Exchange 2010 vs Quest GroupWise Coexistence Manager &#8211; thoughts &#8230;</title>
		<link>http://emailmigrations.com/groupwise-migrations-to-exchange-2010-vs-quest-groupwise-coexistence-manager-thoughts?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=groupwise-migrations-to-exchange-2010-vs-quest-groupwise-coexistence-manager-thoughts</link>
		<comments>http://emailmigrations.com/groupwise-migrations-to-exchange-2010-vs-quest-groupwise-coexistence-manager-thoughts#comments</comments>
		<pubDate>Wed, 03 Aug 2011 01:51:34 +0000</pubDate>
		<dc:creator>webmaster</dc:creator>
				<category><![CDATA[Co-existence]]></category>
		<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[Exchange 2010]]></category>
		<category><![CDATA[GroupWise]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[Novell]]></category>
		<category><![CDATA[Quest]]></category>
		<category><![CDATA[coexistence]]></category>
		<category><![CDATA[directory synchronization]]></category>
		<category><![CDATA[exchange 2007]]></category>
		<category><![CDATA[free busy]]></category>
		<category><![CDATA[freebusy]]></category>
		<category><![CDATA[migration]]></category>

		<guid isPermaLink="false">http://emailmigrations.com/?p=954</guid>
		<description><![CDATA[Migrating off Novell GroupWise onto Microsoft Exchange 2010 has always presented a few challenges to overcome – especially if you are trying to produce a robust Migration Strategy on how to do it. Back in the days of Microsoft Exchange 2003 you could leverage the Microsoft GroupWise Connector to inter-connect the two systems, and this gave you the minimum two functions (in my opinion) required for a migration: Directory Synchronisation Mail Flow Plus, the luxury of an additional function – &#8230; <a class="more-link" href="http://emailmigrations.com/groupwise-migrations-to-exchange-2010-vs-quest-groupwise-coexistence-manager-thoughts">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://emailmigrations.com/groupwise-migrations-to-exchange-2010-vs-quest-groupwise-coexistence-manager-thoughts/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Domino Migration to Exchange &#8211; User Behaviour with Calendaring</title>
		<link>http://emailmigrations.com/domino-migration-to-exchange-user-behaviour-with-calendaring?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=domino-migration-to-exchange-user-behaviour-with-calendaring</link>
		<comments>http://emailmigrations.com/domino-migration-to-exchange-user-behaviour-with-calendaring#comments</comments>
		<pubDate>Fri, 28 Jan 2011 21:27:41 +0000</pubDate>
		<dc:creator>webmaster</dc:creator>
				<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[Exchange 2010]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[appointments]]></category>
		<category><![CDATA[Calendar]]></category>
		<category><![CDATA[domino]]></category>
		<category><![CDATA[email migration]]></category>
		<category><![CDATA[exchange 2007]]></category>
		<category><![CDATA[free busy]]></category>
		<category><![CDATA[lotus notes]]></category>
		<category><![CDATA[Outlook]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Rooms]]></category>

		<guid isPermaLink="false">http://emailmigrations.com/?p=747</guid>
		<description><![CDATA[On a recent email migration project from Domino r8 to Exchange 2007, I noted a pattern of behaviour amongst the user population with regard to support calls related to booking appointments in Outlook 2007. In Domino, when users made a calendar booking involving a Resource, they would use the Rooms&#38;Resource Domino Database to make the booking in the actual Resource calendar, and then all other attendees would be invited at this point also.   The person making the booking did not &#8230; <a class="more-link" href="http://emailmigrations.com/domino-migration-to-exchange-user-behaviour-with-calendaring">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://emailmigrations.com/domino-migration-to-exchange-user-behaviour-with-calendaring/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Domino Rooms &amp; Resources Migration to Exchange 2007/2010 using Quest &#8211; random thoughts</title>
		<link>http://emailmigrations.com/domino-exchange-room-and-resource-custom-address-book-view?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=domino-exchange-room-and-resource-custom-address-book-view</link>
		<comments>http://emailmigrations.com/domino-exchange-room-and-resource-custom-address-book-view#comments</comments>
		<pubDate>Mon, 20 Dec 2010 01:28:15 +0000</pubDate>
		<dc:creator>administrator</dc:creator>
				<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[Exchange 2010]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[appointments]]></category>
		<category><![CDATA[Calendar]]></category>
		<category><![CDATA[domino]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[Quest]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Rooms]]></category>
		<category><![CDATA[transporter]]></category>

		<guid isPermaLink="false">http://emailmigrations.com/?p=729</guid>
		<description><![CDATA[Within Domino, the Rooms and Resources Database provides a rich user experience when it comes to making Calendar bookings from the end-user perspective using the Lotus Notes client.   During a typical email migration from Domino to Exchange2007/2010 there is often negative feedback when people use Outlook Calendaring due to the slightly lesser &#8220;experience&#8221; offered within Exchange 2007/2010. The differences in Calendaring between the two email platforms is often under estimated, and Rooms &#38; Resources are usual migrated to Exchange &#8230; <a class="more-link" href="http://emailmigrations.com/domino-exchange-room-and-resource-custom-address-book-view">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://emailmigrations.com/domino-exchange-room-and-resource-custom-address-book-view/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Quest Notes Migrator to remove Domino Forwarder</title>
		<link>http://emailmigrations.com/using-quest-notes-migrator-to-remove-domino-forwarder?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=using-quest-notes-migrator-to-remove-domino-forwarder</link>
		<comments>http://emailmigrations.com/using-quest-notes-migrator-to-remove-domino-forwarder#comments</comments>
		<pubDate>Mon, 29 Nov 2010 07:25:08 +0000</pubDate>
		<dc:creator>administrator</dc:creator>
				<category><![CDATA[Co-existence]]></category>
		<category><![CDATA[Domino]]></category>
		<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[Quest]]></category>
		<category><![CDATA[Transporter]]></category>
		<category><![CDATA[coexistence]]></category>
		<category><![CDATA[domino]]></category>
		<category><![CDATA[email migration]]></category>
		<category><![CDATA[exchange 2007]]></category>
		<category><![CDATA[lotus notes migration]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[transporter]]></category>

		<guid isPermaLink="false">http://emailmigrations.com/?p=713</guid>
		<description><![CDATA[On a recent email migration project, from Domino r8 to Exchange 2007, there was a requirement to roll-back a group of migrated users to Domino.    We were using Quest Notes Migrator to Exchange (QNME) 4.3 for the migration so were able to create a collection containing the details of the users to be rolled back, and used the option to set mail delivery for these users to Domino which: Removed the Notes forwarder to Exchange Changed the Mail Type back &#8230; <a class="more-link" href="http://emailmigrations.com/using-quest-notes-migrator-to-remove-domino-forwarder">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://emailmigrations.com/using-quest-notes-migrator-to-remove-domino-forwarder/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Enable-ContinuousReplicationHostName &#8211; Exchange 2007</title>
		<link>http://emailmigrations.com/enable-continuousreplicationhostname-exchange-2007?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=enable-continuousreplicationhostname-exchange-2007</link>
		<comments>http://emailmigrations.com/enable-continuousreplicationhostname-exchange-2007#comments</comments>
		<pubDate>Thu, 14 Oct 2010 08:46:58 +0000</pubDate>
		<dc:creator>administrator</dc:creator>
				<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[CCR]]></category>
		<category><![CDATA[Cross over]]></category>
		<category><![CDATA[Enable-ContinuousReplicationHostName]]></category>
		<category><![CDATA[Log Ship]]></category>

		<guid isPermaLink="false">http://emailmigrations.com/?p=542</guid>
		<description><![CDATA[Getting Exchange 2007 CCR cluster nodes to use a private network for CCR log shipping &#8211; easy or hard ?  Bit of both really. This article is really a companion guide to the information already out there on this topic.  I got stuck implementing it, figured out why, and decided to share this with you. I have been working on a new Exchange 2007 CCR implementation where we decided to deploy a pair of cross-over cables between the two CCR &#8230; <a class="more-link" href="http://emailmigrations.com/enable-continuousreplicationhostname-exchange-2007">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://emailmigrations.com/enable-continuousreplicationhostname-exchange-2007/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exchange 2003 Restore After Exchange 2007</title>
		<link>http://emailmigrations.com/exchange-2003-restore-after-exchange-2007?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=exchange-2003-restore-after-exchange-2007</link>
		<comments>http://emailmigrations.com/exchange-2003-restore-after-exchange-2007#comments</comments>
		<pubDate>Thu, 19 Nov 2009 22:52:11 +0000</pubDate>
		<dc:creator>administrator</dc:creator>
				<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[exchange 2003]]></category>
		<category><![CDATA[exchange 2007]]></category>
		<category><![CDATA[legacy]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[restore]]></category>

		<guid isPermaLink="false">http://emailmigrations.com/?p=351</guid>
		<description><![CDATA[When migrating from Exchange 2003 to Exchange 2007, there is a high probability that you receive a request to restore a mailbox from before the migration. How do you do this ?   There are many ways you can retain some sort of Exchange 2003 infrastructure for restore purposes.   This could involve a lab setup, or leaving all your Exchange 2003 production mailbox servers in operation. The most efficient solution I have found involves a little know trick using ADSIEdit and &#8230; <a class="more-link" href="http://emailmigrations.com/exchange-2003-restore-after-exchange-2007">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://emailmigrations.com/exchange-2003-restore-after-exchange-2007/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Exchange 2003 to 2007 Migration</title>
		<link>http://emailmigrations.com/exchange-2003-to-2007-migration?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=exchange-2003-to-2007-migration</link>
		<comments>http://emailmigrations.com/exchange-2003-to-2007-migration#comments</comments>
		<pubDate>Mon, 12 Oct 2009 01:37:54 +0000</pubDate>
		<dc:creator>administrator</dc:creator>
				<category><![CDATA[Exchange 2007]]></category>
		<category><![CDATA[exchange 2003]]></category>
		<category><![CDATA[exchange 2007]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://emailmigrations.com/?p=294</guid>
		<description><![CDATA[I am just completing a major Exchange 2003 to Exchange 2007 migration.  All mailboxes and services have just completed migrating.  Exchange 2003 decom is now required &#8211; after remedial action is taken with Recipient Update Policies and Public Folders. Watch out for the move mailbox operation from Exchange 2003 to Exchange 2007 in the same Org.  The Recipient Update Policy is enforced as part of the move &#8211; Microsoft feature !!  This is not expected and can cause a lot &#8230; <a class="more-link" href="http://emailmigrations.com/exchange-2003-to-2007-migration">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
		<wfw:commentRss>http://emailmigrations.com/exchange-2003-to-2007-migration/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

