Le Cloud de Christophe BOUCETTA

Voici le blog sur les communications unifiées et la collaboration Microsoft par un MVP nominé depuis 11 ans

Voici un excellent article sur les problèmes de localisation avec OCS 2007 R2 :

For all of you European OCS 2007 R2 users, there’s a small “hidden feature” in the release of the OCS 2007 R2 Edge server.

During our migrations from OCS 2007 R1 to the all new R2 RTM release, we noticed some strange A/V Edge Authentication server errors. Users would see a “limited calling” error in Communicator, the Mediation server would complain there was no valid A/V Authentication service, and the front-end A/V Validation would simply fail without any helpful notification. After some in-house troubleshooting, it was time to call in the troops. Together with Microsoft, we validated the Edge configuration, did some tracing, and couldn’t find anything wrong with the edge server. One of the problems that kept coming up was a vague “Version Mismatch” error in the snooper logs. One of our troops at Microsoft took a closer look and noted that the edge server was complaining about a version 2,0 instead of a 2.0. Yes, you read that correctly, a comma instead of a period. We never thought of the fact that we installed the servers with Dutch localization, and apparently, Microsoft didn’t either.

One of the main differences when using a European localization, is the change in number notation. Where the US locale uses a notation like $ 1,000,000.00 , us Europeans will use € 1.000.000,00 . This caused the Edge server to be unable to recognize any version numbers coming in. This bug has been reported to Microsoft, and is in the process of being fixed.

In the meantime, you can work around this issue in the following manner;

    * On the Edge server, add the Edge Service account to local administrators and logoff.
    * Logon using the Edge Service account
    * Go to control panel, Regional and Language options.
    * Change the format to English (US).
    * Remove the Service Account from the local administrators and reboot.

You can verify this workaround by rerunning the validation wizard on your front-end. It will show the A/V authentication service pass with flying colors!

Facebook Like