Comments on: Forcing Address Book Updates in Communicator 2007 R2

By: Nolan

Nolan — Mon, 03 May 2010 23:14:43 +0000

HKEY_CURRENT_USERSoftwareWow6432Node does not exist on Server 2003 x64 it only exists on Windows 7 and server 2008

By: eshudnow

eshudnow — Fri, 02 Apr 2010 13:15:15 +0000

Yes, you need to create the key. It does not exist by default.

By: Mark Denny

Mark Denny — Tue, 30 Mar 2010 21:27:35 +0000

What is the "Communicator" Key does not exist? I run Win7 32 bit and cannot find the key, should i create the key?

By: Elan Shudnow

Elan Shudnow — Thu, 18 Feb 2010 23:03:22 +0000

Thanks for the heads up. I've used the registry keys though as they are and seemed to work fine. Out of curiosity, what OS are you using?

By: Ed Swindelles

Ed Swindelles — Wed, 17 Feb 2010 13:49:24 +0000

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).

By: Jan Fredborg

Jan Fredborg — Sun, 07 Feb 2010 10:06:27 +0000

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.

By: Elan Shudnow

Elan Shudnow — Thu, 04 Feb 2010 18:42:49 +0000

JaBier,

That error can be caused by several things. Make sure that Communicator is patched with the latest MSP. Make sure Outlook is patched. Make sure Windows is patched. Make sure the Front End certificate is attached to the Default Website in IIS on your Front End Server (Web Components Server which would be the Front End on an OCS 2007 R2 Consolidated Server). You also want to make sure that the Internal Web Farm FQDN is set correctly (Standard Front End and the Internal Web Farm FQDN would be the FQDN of your server and Enterprise Front End the Internal Web Farm FQDN would be the Pool FQDN).

Hope that helps.

By: JaBier

JaBier — Thu, 28 Jan 2010 18:53:21 +0000

Thanks, but I have a problem with this question.
My issue is my systems says ALWAYS "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."
I've search this question in forums, msoft and others, but I have still the issue.
Can you help me? any idea ?
Thanks

By: Jayden

Jayden — Wed, 27 Jan 2010 05:01:03 +0000

Hi Mr. Elan, this is Jayden from Temasek Polytechnic, Singapore.
We are now doing our finaly year project and it is something like your OCS.
Would it be possible to have youe contact as we have so much to ask you.
:)
We have like 3 computers, and one dual-boot for Vista and Windows Server 2008, one XP install MOC and one windows server 2003 with Exchange Server 07.

Now having problem installing OCS on Windows server 2008 :(

And we want to ask your permission that can we follow something like your setup of OCS 07 R2? But maybe not so complex haha..

Hope to hear from you soon.

PS. Would be my honor to have you in my msn. jaydenshih@hotmail.com. :)

By: Tweets that mention Forcing Address Book Updates in Communicator 2007 R2 | Elan Shudnow's Blog -- Topsy.com

Thu, 21 Jan 2010 17:28:29 +0000

[...] This post was mentioned on Twitter by Services Ready, Bruno Stöckli. Bruno Stöckli said: Forcing Address Book Updates in Communicator 2007 R2 http://bit.ly/6R9YXh [...]