Description of the update package for Office Communications Server 2007 R2: June, 2009

This article describes the issues that are fixed in the update package for Microsoft Office Communications Server 2007 R2 that is dated June 2009.

• The issues that the update package fixes.
• The prerequisites for installing the update package.
• Whether you must restart the computer after you install the update package.
• Whether the update package is replaced by any other update package.
• Whether you must make any registry changes.
• The files that the update package contains.

Issues that this update package fixes

This update package fixes the following issues:

• The license expiration date for Office Communications Server (OCS) 2007 R2 Evaluation Edition was calculated incorrectly. This causes OCS 2007 R2 Evaluation Edition to expire on June 13, 2009. This update fixes the license expiration date calculation for the OCS 2007 R2 Evaluation Edition. By downloading this update, the expiration date will be based correctly on the installation date of the server.
• Earlier updates of OCS 2007 R2 required Microsoft Message Queuing (also known as MSMQ) to be installed on OCS 2007 R2 Enterprise Edition Distributed – Front End or the OCS 2007 R2 Standard Edition. This update removes that requirement.
• The RTC Media Relay driver in OCS Edge Server has also been updated this update.

This cumulative update also includes the following previously released updates:

• 968879  (http://support.microsoft.com/kb/968879/ ) You cannot forward a call between federated users in Communications Server 2007 R2
• 968938  (http://support.microsoft.com/kb/968938/ ) The Communications Server 2007 R2 - A/V Edge Authentication Server does not recognize a token request if the locale for RTCProxyService is not en-US/409
• 969010  (http://support.microsoft.com/kb/969010/ ) Communications Server 2007 R2 performance counters are missing in Performance Monitor
• 968910  (http://support.microsoft.com/kb/968910/ ) Communications Server 2007 does not detect the changes when Unified Messaging dial plans or UM servers are added

Update package information

Download Center

The following file is available for download from the Microsoft Download Center:
Download the Server.msp package now. (http://go.microsoft.com/fwlink/?LinkId=154247)
Release Date: June 2009

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Microsoft Update

To obtain this update, visit the following Microsoft Web site: The update appears in Optional Updates under Microsoft Office Communications Server 2007 R2. For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

If you are an administrator, you may want to download this update and then distribute it to clients. To download the update to a folder of your choice, visit the following Microsoft Web site: When you search for Communications Server 2007 R2, all the updates that are available for Communications Server 2007 R2 are shown.

By Contacting Microsoft Support

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this update package.

Restart requirement

You will be prompted to restart your computer after you install this update package.

Note You do not have restart after you uninstall the update package.

Hotfix replacement information

This hotfix package replaces hotfix package 967831.

Registry information

To use the updates in this package, you do not have to make any changes to the registry.

Update package installation information

To install this update package, install the OCS2007-KB972041-amd64-Server.msp package on the following computers:

• Office Communications Server 2007 R2– Standard Edition Server
• Office Communications Server 2007 R2– Enterprise Edition Consolidated
• Office Communications Server 2007 R2 – Enterprise Edition Distributed – Front End
• Office Communications Server 2007 R2 – Edge Server
  
  Note Because this update package updates the RTC Media Relay driver, you may have to intervene in the installation of this update on OCS 2007 R2 – Edge Server. If you install this update to by using Microsoft Update on a computer that is running Windows Server 2008 or if you manually install this update on other Windows operating systems, you will receive the following prompt:

  Windows Security
  
  Would you like to install this device software?
  Always trust software from "Microsoft Corporation".  
  [Install] [Don't Install]
  You should only install driver software from publishers you trust.  How can I decide which device software is safe to install?

  You should choose Install. Additionally, if you check Always trust content from Microsoft Corporation, you will not receive this prompt again.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issue that listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Removal information

To remove this update package, use the Add or Remove Programs item in Control Panel.

Note When you uninstall this update, Office Communications Server Monitoring Agent (RTCQmsAgent) is stopped. However, you must manually restart RTCQmsAgent after you uninstall this update.

Note You cannot uninstall the RTC Media Relay driver. All other binaries that are installed by the update, will be rolled back to the previous version when you uninstall this update. However, the RTC Media Relay driver (RTCMRDRV.sys) in %windir%\system32\drivers is not rolled back.

Additionally, when you try to uninstall the update package, you may be prompted for the source CD. If you are prompted for the source CD, insert the source CD, or provide the path of the location of the source files.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: