This article describes the Microsoft Office Communications Server 2007 R2 issues that are fixed in the cumulative update for Microsoft Office Communications Server 2007 R2 that is dated January 2010.
This article describes the following items about the update package:
- 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:
978363
(http://support.microsoft.com/kb/978363/
)
You experience performance issues in Office Communications Server 2007 R2 during NTLM authentication
978364
(http://support.microsoft.com/kb/978364/
)
You experience performance issues in Office Communications Server 2007 R2 when you move many users between pools at the same time
978366
(http://support.microsoft.com/kb/978366/
)
Instant messages are blocked in Office Communications Server 2007 R2 if a third-party application uses the "otherIpPhone" attribute
978367
(http://support.microsoft.com/kb/978367/
)
You cannot start the Office Communications Server 2007 R2 Front-End service if the connection to the root domain controller is lost
978369
(http://support.microsoft.com/kb/978369/
)
Instant messaging fails when the Office Communications Server 2007 R2 front-end server that you connect to changes
This cumulative update also includes the following previously released updates:
975892
(http://support.microsoft.com/kb/975892/
)
Error message when you send a meeting request for a conference call that is hosted in Office Communications Server 2007 R2, Enterprise Edition
975894
(http://support.microsoft.com/kb/975894/
)
Event ID 44031 for trusted domains is logged frequently in Office Communications Server 2007 R2
968955
(http://support.microsoft.com/kb/968955/
)
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
972714
(http://support.microsoft.com/kb/972714/
)
No calling party name appears in Communicator 2007 R2 when a Private Branch Exchange telephone user calls a Communications Server 2007 R2 user
972709
(http://support.microsoft.com/kb/972709/
)
Error message when a SIP message request is sent from a federated partner in Communications Server 2007 R2: "500: Server Internal Error"
972700
(http://support.microsoft.com/kb/972700/
)
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
972403
(http://support.microsoft.com/kb/972403/
)
Network performance issues that are caused by Global address list (GAL) file downloads or by GAL delta file downloads in Office Communicator 2007 R2
971844
(http://support.microsoft.com/kb/971844/
)
No calling party name appears in Communicator 2007 R2 when a Private Branch Exchange telephone user calls a Communications Server 2007 R2 user
971845
(http://support.microsoft.com/kb/971845/
)
You cannot use a set of features in Office Communicator 2007 R2 that integrate secure delegation for the local Outlook 2007 calendar
975892
(http://support.microsoft.com/kb/975892/
)
Error message when you send a meeting request for a conference call that is hosted in Office Communications Server 2007 R2, Enterprise Edition
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
- The license expiration date for Office Communications Server (OCS) 2007 R2 Evaluation Edition was calculated incorrectly. This miscalculation causes OCS 2007 R2 Evaluation Edition to expire on July 13, 2009. This update fixes the calculation of the license expiration date for OCS 2007 R2 Evaluation Edition. By downloading this update, the expiration date is based 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.
Update package information
Microsoft Download Center
The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
(http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4)
Release Date: January 2010
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591
(http://support.microsoft.com/kb/119591/
)
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 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
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 are 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 975611.
975611
(http://support.microsoft.com/kb/975611/
)
Description of cumulative update for Office Communications Server 2007 R2: October 2009
Registry information
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-KB977345-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 during the installation of the update on OCS 2007 R2 – Edge Server. If you install this update 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:
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?
Removal information
To remove this update package, use the
Add or Remove
Programs feature 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.
Sometimes, when you try
to uninstall the update package, you are prompted for the source CD. If you are prompted for the source CD, insert it, or provide the path where the source
files can be found.
File information
This update may not contain all the files that you must have to fully update a product to the latest build. This update 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:
Collapse this tableExpand this table
| File name | File version | File size | Date | Time | Platform |
|---|
| Abserver.exe | 3.5.6907.83 | 329,560 | 11-Dec-2009 | 21:30 | x86 |
| Abserver.exe.config | Not Applicable | 1,541 | 11-Dec-2009 | 21:30 | Not Applicable |
| Exumrouting.exe | 3.5.6907.56 | 358,224 | 11-Dec-2009 | 21:30 | x86 |
| Microsoft.rtc.server.mcuinfrastructure.dll | 3.5.6907.37 | 1,644,424 | 11-Dec-2009 | 21:30 | x86 |
| Inboundrouting.exe | 3.5.6907.56 | 362,328 | 11-Dec-2009 | 21:30 | x86 |
| Lcmanagedtaskhandler.dll | 3.5.6907.41 | 1,062,752 | 11-Dec-2009 | 21:30 | x86 |
| Mediarelaysvc.exe | 3.5.6907.37 | 231,248 | 11-Dec-2009 | 21:30 | x86 |
| Microsoft.rtc.mras.dll | 3.5.6907.37 | 284,512 | 11-Dec-2009 | 21:30 | x86 |
| Microsoft.rtc.server.mcuinfrastructure.dll | 3.5.6907.37 | 1,644,424 | 11-Dec-2009 | 21:30 | x86 |
| Rtcarcha.dll | 3.5.6907.37 | 1,664,328 | 11-Dec-2009 | 21:30 | x64 |
| Rtcmrdrv64.sys | 3.5.6907.37 | 160,584 | 11-Dec-2009 | 21:30 | x64 |
| Rtcsrv.exe | 3.5.6907.34 | 1,026,888 | 11-Dec-2009 | 21:30 | x64 |
| Sipstack.dll | 3.5.6907.83 | 2,898,264 | 11-Dec-2009 | 21:30 | x64 |
| Translationservice.exe | 3.5.6907.37 | 362,336 | 11-Dec-2009 | 21:30 | x86 |
| Userpinservice.exe | 3.5.6907.83 | 624,480 | 11-Dec-2009 | 21:30 | x86 |
| Wrtces.dll | 3.5.6907.83 | 4,861,776 | 11-Dec-2009 | 21:30 | x64 |
For more information about
software update terminology, click the following article number to view the
article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 977345 - Last Review: January 7, 2010 - Revision: 1.0
APPLIES TO
- Microsoft Office Communications Server 2007 R2 Standard Edition
- Microsoft Office Communications Server 2007 R2 Enterprise Edition
| kbsurveynew kbexpertiseinter kbqfe kbhotfixrollup kbautohotfix kbhotfixserver KB977345 |
Back to the top
