MVP Lee Desmond posted a great post about the November updates for Office Communications Server 2007 R2. Check it out here: http://www.leedesmond.com/weblog/?p=607
Check out the latest Nov 2009 updates released for the different Office Communications Server 2007 R2 server roles as described in KB968802. This applies to both the Standard and Enterprise Editions.
A very important and welcome addition to assist the patch management process is the “Cumulative Server Update Installer” (ServerUpdateInstaller.exe) delivered as part of this release. Instead of having to determine and manually applying the relevant patches to the various R2 server roles, this tool relieves the administrator from those tedious chores by applying all updates for the appropriate server role in just one click. You can also use this tool on the command line with the switches /silent, /forcereboot and /extractall.
If not already present, you shoud also apply the update* for the Office Communications Server 2007 R2 Back-end Database (KB969834).
Download for the updates (.msp), executable (.exe) and installer (.msi) can be obtained here.
Here is a good guide on how to install the updates: http://blogs.technet.com/ucspotting/archive/2009/11/26/3296447.aspx
When using Microsoft Office Communicator 2007 R2, double-clicking a Contact fails to launch a new conversation window. However, you are still able to right-click a Contact, and start an IM session by selecting “Send an Instant Message.”
Cause: When double-clicking a Contact, OC 2007 R2 uses XML to initialize a new conversation window, and we’re finding several customers who have incompatible and/or legacy builds of MSXML.DLL that are encountering these failures.
Resolution: To resolve this issue, please install XML Version 6.0 and XML Version 3.0 SP7.
Thanks to Scott Oseychik for posting the solution here: http://blogs.msdn.com/scottos/archive/2009/09/25/communicator-2007-r2-fails-to-open-new-window-when-double-clicking-a-contact.aspx
If you have users with computers that are not joined to the same domain that their OCS account is homed to, the users always have to type the password when logging on using Communicator. This is the default setting in Communicator. There is a registry setting for enabling the “remember password” checkbox in the Communicator sign in dialog. I have tested it with non domain joined computers and it works like a charm. Here’s what you do
- Open Registry editor
- Locate the following key
- If the key is not there
- Create the Communicator folder
- Create the key as DWORD and give it the name SavePassword
- Set SavePassword=1.
- This enables a checkbox to save password in MOC login dialogue.
- After the password is entered it is saved into the registry
- This registry key store in hashed value. Changing the hash requires re-entering the password.
Original article found over at OCSpedia.com http://www.ocspedia.com/FE/How_to_Save_Password_MOC.htm