Sunday, January 10, 2010

Client Version Filtering on Windows x64

At my company we use Client Version Filtering to deploy the latest Communicator client updates. Here is how it is configured:

After installing the January updates for Office Communications Server 2007 R2 and publishing the new Communicator update to Client Version Filtering, I received an error that my client could not find the update.

I looked in the IIS logs and noticed that it was trying to pull the update for the x64 architecture.

2010-01-10 21:11:12 POST /AutoUpdate/Ext/Handler/OCUpgrade.aspx folder=OC&lang=1033&mode=non-ui&arch=x64&flavor=pm&build=fre 443 - Microsoft+Office+Communicator/3.0 401 2 5 596

Even though my Communicator client is x86, I am running Windows 7 x64.

I created a new folder for x64 in the AutoUpdate path as pictured below:

Subsequently, my client was able to download and install the new Communicator update.

2010-01-10 21:34:53 HEAD /AutoUpdate/Ext/Files/OC/x64/fre/1033/Communicator.msp - 443 - Microsoft+BITS/7.5 401 2 5 63

Although this is an acceptable workaround for now, my assumption is that this is actually a bug that will need to be addressed by Microsoft. Most likely this logic was put in place for a forthcoming x64 version of Communicator.


  1. Days ago, i saw a page here some free keys of windows and office related version: To share and hope can help you.

  2. Recommend you guys a good site to get cheap and genuine product keys for windows:, all versions of windows keys can be found there.