<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Forcing Address Book Updates in Communicator 2007 R2</title>
	<atom:link href="http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/</link>
	<description>Just another IT guy!</description>
	<lastBuildDate>Thu, 09 Feb 2012 12:04:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Victor</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-11851</link>
		<dc:creator>Victor</dc:creator>
		<pubDate>Thu, 24 Feb 2011 14:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-11851</guid>
		<description>There is something still no right in to all this. If I apply the registry key hack then the Address Book is downloaded by the OC Clients but if I don&#039;t apply it, the Address Book is not downloaded (I have waited 24 hours). The OC client doesn&#039;t report any error such as:  &quot;Cannot syncronize with the corporate address book. This may be cause the proxy server setting in your web browser does not allow access to the addres book.&quot; 
 
So my question is, the OC clients should be updating on their own. The reg hack is a hack and not a solution to this problem. What am I missing here?  </description>
		<content:encoded><![CDATA[<p>There is something still no right in to all this. If I apply the registry key hack then the Address Book is downloaded by the OC Clients but if I don&#039;t apply it, the Address Book is not downloaded (I have waited 24 hours). The OC client doesn&#039;t report any error such as:  &quot;Cannot syncronize with the corporate address book. This may be cause the proxy server setting in your web browser does not allow access to the addres book.&quot; </p>
<p>So my question is, the OC clients should be updating on their own. The reg hack is a hack and not a solution to this problem. What am I missing here?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: koszyk.org &#187; Blog Archive &#187; Office communicator 2007 r2 i książka adresowa</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-11294</link>
		<dc:creator>koszyk.org &#187; Blog Archive &#187; Office communicator 2007 r2 i książka adresowa</dc:creator>
		<pubDate>Mon, 27 Dec 2010 00:19:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-11294</guid>
		<description>[...] I link do autora: http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/ [...]</description>
		<content:encoded><![CDATA[<p>[...] I link do autora: <a href="http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/" rel="nofollow">http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Updating the Lync 2010 Address Book &#124; Volta82&#039;s Blog</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-10670</link>
		<dc:creator>Updating the Lync 2010 Address Book &#124; Volta82&#039;s Blog</dc:creator>
		<pubDate>Thu, 18 Nov 2010 19:02:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-10670</guid>
		<description>[...] systems running the 32-bit only OC 2007 R2 client had to have the setting created under the Wow6432Node policies [...]</description>
		<content:encoded><![CDATA[<p>[...] systems running the 32-bit only OC 2007 R2 client had to have the setting created under the Wow6432Node policies [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Updating the Lync 2010 Address Book : Jeff Schertz&#039;s Blog</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-10491</link>
		<dc:creator>Updating the Lync 2010 Address Book : Jeff Schertz&#039;s Blog</dc:creator>
		<pubDate>Tue, 28 Sep 2010 22:05:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-10491</guid>
		<description>[...] systems running the 32-bit only OC 2007 R2 client had to have the setting created under the Wow6432Node policies [...]</description>
		<content:encoded><![CDATA[<p>[...] systems running the 32-bit only OC 2007 R2 client had to have the setting created under the Wow6432Node policies [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nolan</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-10078</link>
		<dc:creator>Nolan</dc:creator>
		<pubDate>Mon, 03 May 2010 23:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-10078</guid>
		<description>HKEY_CURRENT_USERSoftwareWow6432Node does not exist on Server 2003 x64 it only exists on Windows 7 and server 2008 </description>
		<content:encoded><![CDATA[<p>HKEY_CURRENT_USERSoftwareWow6432Node does not exist on Server 2003 x64 it only exists on Windows 7 and server 2008</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eshudnow</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-9865</link>
		<dc:creator>eshudnow</dc:creator>
		<pubDate>Fri, 02 Apr 2010 13:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-9865</guid>
		<description>Yes, you need to create the key.  It does not exist by default.  </description>
		<content:encoded><![CDATA[<p>Yes, you need to create the key.  It does not exist by default.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Denny</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-9853</link>
		<dc:creator>Mark Denny</dc:creator>
		<pubDate>Tue, 30 Mar 2010 21:27:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-9853</guid>
		<description>What is the &quot;Communicator&quot; Key does not exist? I run Win7 32 bit and cannot find the key, should i create the key? </description>
		<content:encoded><![CDATA[<p>What is the &quot;Communicator&quot; Key does not exist? I run Win7 32 bit and cannot find the key, should i create the key?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elan Shudnow</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-9675</link>
		<dc:creator>Elan Shudnow</dc:creator>
		<pubDate>Thu, 18 Feb 2010 23:03:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-9675</guid>
		<description>Thanks for the heads up.  I&#039;ve used the registry keys though as they are and seemed to work fine.  Out of curiosity, what OS are you using? </description>
		<content:encoded><![CDATA[<p>Thanks for the heads up.  I&#039;ve used the registry keys though as they are and seemed to work fine.  Out of curiosity, what OS are you using?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Swindelles</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-9671</link>
		<dc:creator>Ed Swindelles</dc:creator>
		<pubDate>Wed, 17 Feb 2010 13:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-9671</guid>
		<description>FYI - The quotation marks in your registry entries need to be changed to regular quotations before you can import them using a .reg file (for me, anyway). </description>
		<content:encoded><![CDATA[<p>FYI &#8211; The quotation marks in your registry entries need to be changed to regular quotations before you can import them using a .reg file (for me, anyway).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Fredborg</title>
		<link>http://www.shudnow.net/2010/01/20/forcing-address-book-updates-in-communicator-2007-r2/comment-page-1/#comment-9635</link>
		<dc:creator>Jan Fredborg</dc:creator>
		<pubDate>Sun, 07 Feb 2010 10:06:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.shudnow.net/?p=1616#comment-9635</guid>
		<description>JaBier, 
 
It might also have to do with the CRL not being available to the client - check that the CRL location in the certificate is available to the client, if not (and you are using your own internal CA) you can change / add CRL paths in the CA Authority utility before re-issuing new certs. </description>
		<content:encoded><![CDATA[<p>JaBier, </p>
<p>It might also have to do with the CRL not being available to the client &#8211; check that the CRL location in the certificate is available to the client, if not (and you are using your own internal CA) you can change / add CRL paths in the CA Authority utility before re-issuing new certs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

