Office Communicator 2007 R2 - April 2009 hotfix rollup - v3.5.6907.9

Issues fixed:

Communicator 2007 R2 update for Microsoft Online Services

You experience one-way audio when LG-Nortel IP8540 or Polycom CX700 phones are used in an Audio Video call on Windows XP

Error events occur when you disconnect a computer that is running Communicator 2007 R2 from the network: "Event ID: 3" or "Event ID: 7"

Initial changes for the integration of Office Communicator 2007 R2 and the next version of Office after the Office 2007 release

Communicator 2007 R2 stores the Actual Remote Number (The number that is dialed) for outgoing calls to a remote party

You cannot see features in Office 14 builds if you are running Communicator 2007 R2 RTM or earlier versions

The font in the Conversation window is very small when you run Office Communicator 2007 R2 on a Windows Vista-based computer that has high DPI (120 DPI) with Internet Explorer 8 installed

You cannot click the password field and enter a password when you sign in to Office Communicator 2007 R2

Office Communicator 2007 R2 update to support Polycom roundtable devices

In Office Communicator 2007 R2, User A gets a failure-to-deliver message after sending an IM to User B even though User B receives the message.

You can read more about the issues fixed in this release here.

Download the Office Communicator 2007 R2 client update here.

The update changes the build number from v3.5.6907.0 to v3.5.6907.9, which can be tracked inside the OCS 2007 R2 administration panel, under 'Database'.

Now for the $1000 question: How the heck do I install this update onto my OCS server so that my clients will automagically download the update when they connect in the next time? I cannot find how to configure the Office Communicator 2007 R2 Automatic Client Update functionality anywhere on the Internet or in the official documentation. I admit, I've only searched for about a half hour, but it is extremely frustrating. I already have updating the Phone Editions working 100%.

Update: Thanks to this blog post and a few e-mails later - I have a solution to the $1000 question here.