Wednesday, May 20, 2009

Communicator 2007 R2 hotfix rollup package: May 2009 kb971083

get it here
Issue that this update package fixes
This cumulative update fixes the following issue:
  • 971078 (http://support.microsoft.com/kb/971078/ ) An Automatic Update download is not initiated on a computer that is running Office Communicator 2007 R2 build 3.5.6907.9

This cumulative update also includes the following previously released updates:
  • 968504 (http://support.microsoft.com/kb/968504/ ) Description of the Communicator 2007 R2 update for Microsoft Online Services

  • 968623 (http://support.microsoft.com/kb/968623/ ) You experience one-way audio when LG-Nortel IP8540 or Polycom CX700 phones are used in an Audio Video call on Windows XP

  • 968624 (http://support.microsoft.com/kb/968624/ ) Error events occur when you disconnect a computer that is running Communicator 2007 R2 from the network: "Event ID: 3" or "Event ID: 7"

  • 968625 (http://support.microsoft.com/kb/968625/ ) Description of a hotfix that applies the initial changes for the integration of Office Communicator 2007 R2 and the next version of Office after the Office 2007 release

  • 968628 (http://support.microsoft.com/kb/968628/ ) Communicator 2007 R2 stores the Actual Remote Number (The number that is dialed) for outgoing calls to a remote party

  • 968631 (http://support.microsoft.com/kb/968631/ ) 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

  • 968632 (http://support.microsoft.com/kb/968632/ ) You cannot click the password field and enter a password when you sign in to Office Communicator 2007 R2

  • 968634 (http://support.microsoft.com/kb/968634/ ) Description of Office Communicator 2007 R2 update to support Polycom roundtable devices

  • 968690 (http://support.microsoft.com/kb/968690/ ) 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

It solved also Exchange 2010 integration problems get more info here