Issues that this update package fixes
This update package fixes the following issues:
Error message when you send a meeting request for a conference call that is hosted in Office Communications Server 2007 R2, Enterprise Edition
Event ID 44031 for trusted domains is logged frequently in Office Communications Server 2007 R2
This cumulative update also includes the following previously released updates:
A computer that is running Office Communications Server 2007 R2, Audio/Video Conferencing Edge Server crashes when it tries to process a Relay NAT message
Two users unexpectedly join the same conference when they try to join separate conferences in Office Communications Server 2007 R2
Error message when a SIP message request is sent from a federated partner in Communications Server 2007 R2: "500: Server Internal Error"
When Office Communications Server 2007 R2 routes a voice mail call to an Exchange Server 2007 Unified Messaging server, the corresponding invitation message does not indicate that the request originates from Office Communications Server
No calling party name appears in Communicator 2007 R2 when a Private Branch Exchange telephone user calls a Communications Server 2007 R2 user
The delegate permissions feature in Office Communicator 2007 R2 is unavailable to non-unified communications users
You cannot forward a call between federated users in Communications Server 2007 R2
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
Communications Server 2007 R2 performance counters are missing in Performance Monitor
Communications Server 2007 does not detect the changes when Unified Messaging dial plans or UM servers are added
This update package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
- 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 July 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 calculated correctly, based on the installation date of the server.
- Earlier updates of OCS 2007 R2 required Microsoft Message Queuing 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.
Microsoft Download Center
The following file is available for download from the Microsoft Download Center:Download the Server.msp package now.
Release Date: October 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:
How to obtain Microsoft support files from online services
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.
By contacting 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 that are 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.
The fixes in the update for Office Communications Server 2007 R2 take effect only if the following update for Office Communication Server 2007 R2 core components is also applied together with the update that is described in this article. Therefore, the fixes are split between two updates that include the following update:
Description of the Cumulative Update for Office Communications Server 2007 R2, Core Components: October 2009
You do not have to restart the computer after you apply this update package.
Hotfix replacement information
This update package replaces the following update package:
Description of the update package for Office Communications Server 2007 R2: July, 2009
To use one of the update packages 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-KB975611-amd64-Server.msp package on computers in your network that are running the following platforms:
- 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
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 receive the following prompt:
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?
When you receive this prompt, click Install
. Additionally, if you click to select Always trust content from Microsoft Corporation
, you will not receive this prompt again.
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 issues that are listed in this article.
After the update is installed, the global version of this update has the file attributes, or a later version of the file attributes, that are listed in the following table:
|File name||File version||File size||Date||Time||Platform|
|File_abserver.exe.config||Not Applicable||1,541||21-Oct-2009||18:24||Not Applicable|
To remove this update package, use the Add or Remove Programs
feature in Control Panel. Note
When you uninstall this update, the Office Communications Server Monitoring Agent (RTCQmsAgent) stops. 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 are rolled back to the earlier 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.