<?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: Troubleshooting CRM 3.0 Outlook Client Synchronization Issues</title>
	<atom:link href="http://blogs.infinite-x.net/2006/11/21/troubleshooting-crm-30-outlook-client-synchronization-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.infinite-x.net/2006/11/21/troubleshooting-crm-30-outlook-client-synchronization-issues/</link>
	<description>Knowledge found and lost while working with Microsoft CRM</description>
	<pubDate>Wed, 19 Nov 2008 16:14:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: mitch</title>
		<link>http://blogs.infinite-x.net/2006/11/21/troubleshooting-crm-30-outlook-client-synchronization-issues/#comment-500</link>
		<dc:creator>mitch</dc:creator>
		<pubDate>Fri, 04 May 2007 16:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.infinite-x.net/2006/11/21/troubleshooting-crm-30-outlook-client-synchronization-issues/#comment-500</guid>
		<description>Richard,

It turns out that there is actually some information stored within the CRM database itself which is only updated by the outlook client itself. Changing the registry key doesn't actually produce the same result.

There is also no information or practices which will allow us to change this database information either.

Mitch</description>
		<content:encoded><![CDATA[<p>Richard,</p>
<p>It turns out that there is actually some information stored within the CRM database itself which is only updated by the outlook client itself. Changing the registry key doesn&#039;t actually produce the same result.</p>
<p>There is also no information or practices which will allow us to change this database information either.</p>
<p>Mitch</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: richardb</title>
		<link>http://blogs.infinite-x.net/2006/11/21/troubleshooting-crm-30-outlook-client-synchronization-issues/#comment-499</link>
		<dc:creator>richardb</dc:creator>
		<pubDate>Fri, 04 May 2007 15:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.infinite-x.net/2006/11/21/troubleshooting-crm-30-outlook-client-synchronization-issues/#comment-499</guid>
		<description>Mitch,
These are the keys we need.
We want to change the sync settings for all users BEFORE they launch Outlook.
Here's our problem: The 3 sync keys: SyncCalItem, SyncContact and SyncTask don't seem to 'take' when done via the registry.(we want to set those 3 keys to 0 before they start Outlook)
However, we are able to modify the RunOutlookSyncOnStartup key and it does take right away.
We did notice that the key type for RunOutlookSyncOnStartup is different than the other 3.
Those keys are set properly when done via Outlook client.
Any idea why this happens?
Thanks for your help,
Richard</description>
		<content:encoded><![CDATA[<p>Mitch,<br />
These are the keys we need.<br />
We want to change the sync settings for all users BEFORE they launch Outlook.<br />
Here&#039;s our problem: The 3 sync keys: SyncCalItem, SyncContact and SyncTask don&#039;t seem to &#039;take&#039; when done via the registry.(we want to set those 3 keys to 0 before they start Outlook)<br />
However, we are able to modify the RunOutlookSyncOnStartup key and it does take right away.<br />
We did notice that the key type for RunOutlookSyncOnStartup is different than the other 3.<br />
Those keys are set properly when done via Outlook client.<br />
Any idea why this happens?<br />
Thanks for your help,<br />
Richard</p>
]]></content:encoded>
	</item>
</channel>
</rss>
