2010-03-1
Office Communicator error – Cannot synchronize address book
So after doing some extensive Googling, I did some troubleshooting and found that the situtation was:
- There was no issue with the proxy server. I could manually enter the name of one of the address book files (eg https://ocs.domain.com/Abs/Ext/F-0918.lsabs) and download it manually through the browser.
- There is no GalContacts.db file in the ‘C:\Documents and Settings\%UserName%\Local Settings\Application Data\Microsoft\Communicator’ folder meaning that there was no locally cached copy of the address book.
- In the registry under ‘HKCU\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\INTERNET SETTINGS’ if I set the CertificateRevocation DWORD and to 0, I can successfully sign in and retrieve the address book (below)
- Registry setting
This pointed to an issue with the certificate we were using and specifically the Certificate Revocation List (CRL). From here we need to check the certificate we were using for OCS, look at the details tab and check the CRL Distribution Point (shown below)
- Check Certificate
I then checked this distribution point (a HTTP location in our case) and found out that it was invalid. Right, so next it was off to reconfigure our internal Certificate Authority server with the correct CRL locations.
On the Certificate Authority, we open up the MMC snap-in, right click the server name and select properties. On the extension tab, select ‘CRL Distibution Point’. You then want to configure some valid location underneath here and tick the box to ensure these are being included in the issued certificates. For example in my case, I ensured that there were 3 additional entries (not including the C:\Windows one):
1 2 3 4 5 6 | LDAP:///CN=<CATruncatedName><CRLNameSuffix>,CN=<ServerShortName>,CN=CDP,CN=Public Key Services,CN=Services,<ConfigurationContainer><CDPObjectClass> [TICK] Publish CRLs to this location [UNTICK] Include in all CRLs…….Active Directory….. [UNTICK] Include in CRLs….Delta CRL Locations….. [TICK] Include in the CDP extension of issued certificates [TICK] Publish Delta CRLs to this location |
1 2 3 4 5 6 | file://\\<ServerDNSName>/CertEnroll/<CaName><CRLNameSuffix><DeltaCRLAllowed>.crl [TICK] Publish CRLs to this location [GREYED OUT] Include in all CRLs…….Active Directory….. [UNTICK] Include in CRLs….Delta CRL Locations….. [TICK] Include in the CDP extension of issued certificates [UNTICK] Publish Delta CRLs to this location |
1 2 3 4 5 6 | http://<ServerDNSName>/CertEnroll/<CAName><CRLNameSuffix><DeltaCRLAllowed>.crl [GREYED OUT] Publish CRLs to this location [GREYED OUT] Include in all CRLs…….Active Directory….. [UNTICK] Include in CRLs….Delta CRL Locations….. [TICK] Include in the CDP extension of issued certificates [GREYED OUT] Publish Delta CRLs to this location |
Selecting OK will then restart the Certificate Services service. Then you need to recreate your OCS certificates via the OCS MMC certificate wizard. Once these have been applied to the OCS server (OCS services do NOT need to be restarted), you clients just need to sign out and back in and all of your address book issues are fixed!
If you look at your new certificate, the newly added CRL Distribution Points should be listed. You can also use the ‘Certutil.exe –v –verify –urlfetch c:\exported_certificate.cer’ with above certificate and check that CRL locations can be reached successfully. The ‘pkiview.msc’ tools from the Windows 2003 Resource Kit was also very useful in checking that the CRL locations could be reached.