Suggestion interessante dans le cas ou Communicator affiche le message : Cannot Synchronize Address Book

• use the “Automatically detect settings” instead of specifying settings for a proxy server in IE
• for IE7 under Advanced / Security, uncheck the option “Check for server certificate revocation” and restart the browser (manually or via Group Policy)
• ascertain that the URL listed on the certificate points to the Certificate Revocation List (CRL) Distribution Point that is reachable on the inside and/or outside network
• if OCS is deployed with digital certificates issued from an internal CA, add the .crl URL to the Trusted sites or Local Intranet zone on the Security tab in IE then exit and restart MOC e.g. http://*.swissitpro.ch. This enables the intranet URL for Address Book (AB) download to be recognized as safe and valid.
• deploy certificates from trusted public Certificate Authority (CA) permits both domain and guest (non-domain) accounts to connect to internal OCS pools

Nouveau problème soulevé par un de nos clients aujourdhui suite a un changement de certificats :

Communicator affiche en haut à droite le message suivant “Cannot synchronize with the corporate address book because the file could not be found. Please contact your system administrator with this information.”.

Le certificat sur le site web par défaut de IIS ayant aussi était changé, on a résolu le pb en regénérant le carnet d'adresses :

- commande : abserver -regenUR

- commande : abserver -syncnow

puis supprimer le fichier galcontacts.gb situé dans Documents and Settings\<user>\Local Settings\Application Data\Microsoft\Communicator

Fermer Communicator puis relancé le.

Un bug dans dans la version d'evaluation de communicator 2007 R2 a provoqué une expiration prématuré (180 jours d'evalution) des client. Panique, mais voila la solution et la cause :

This update package fixes the following issues:

The license expiration date for Office Communicator (OC) 2007 R2 Evaluation Edition was calculated incorrectly. This causes OC 2007 R2 Evaluation Edition to expire on June 13, 2009. This update fixes the license expiration date calculation for the OC 2007 R2 Evaluation Edition. By downloading this update, the expiration date will be based correctly on the installation date of the OC 2007 R2.

Read more here:
http://support.microsoft.com/?kbid=972042

Get it here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=515d6dba-4c6a-48bb-a06a-d99c5742676d

Je vais faire part d'un problème que je viens d'avoir suite a une mise a jour effectué sur mon front end OCS R2 qui empeche le service de demarré :

Source: OCS AppDomain Host Process, ID: 50007

An unhandled exception was encountered.

Exception Details. System.NullReferenceException: Object reference not set to an instance of an object.
2 Microsoft.Rtc.Server.McuFactory.McuFactoryHost.Main(String[] args)
2 Microsoft.Rtc.Server.McuFactory.ExecutableEntryPoint.Main(String[] args)
2 System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
2 System.AppDomain.ExecuteAssemblyByName(String assemblyName, Evidence assemblySecurity, String[] args)
2 Microsoft.Rtc.AppDomainHost.Launcher.AppDomainLauncher.RunThread()
2 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
2 System.Threading.ThreadHelper.ThreadStart()
Cause: One of the applications identified in the eventlog description failed.

Resolution:

Restart the server. If the problem persists contact product support.

Pour résoudre ce problème :

1. Uninstall all Frameworks on server.
2. Download and install a last version of Framework (3.5 SP1) from Microsoft site.
3. Download and install NDP20SP2-KB958481-x64.exe, NDP30SP2-KB958483-x64.exe, NDP35SP1-KB958484-x64.exe updates.
4. After that Windows update installs to updates to Communication Server (April and some for Monitoring Server, before that it don't want to install April updates).
5. Reboot server, services started.