To go along with the Office Communicator 2007 R2 April update mentioned
here, we have a server side update that brings the build to
v3.5.6907.9.
Most of them seem to involve certificates, Response Group, and the Conferencing Attendant related. The Conferencing Attendant issue listed below has been particularly annoying for some users, so I'm glad to see it listed.
KB 967832 - Application Host
When you configure the Communications Server 2007 SIP Proxy to listen on a port other than the default SIP TLS port, SIP connections cannot be initiated by Response Group Server or by Conference Auto Attendant
KB 967833 - Application Sharing Server
When you try to import configuration settings into Communications Server 2007 R2, the Application Sharing multipoint control unit does not register the new media relay for the pool
KB 968280 - Administration Tools
Response Group Service cannot start if you assign a certificate that has a wildcard in the Subject Name to Office Communications Server 2007 R2
Response Group Service cannot start if you assign a certificate that contains a SAN list, and the last name on the list is not the pool FQDN to Office Communications Server 2007 R2
After you restart the Communications Server 2007 R2 Response Group Service, the service does not send calls to agents
The Communications Server 2007 R2 Response Group Service does not update its list of trusted hosts at run time
KB 967827 - Core Components
Error message when you open an audit log file for Office Communications Server 2007 R2: "The process cannot access the log file because is being used any another process"
KB 967836 - Communicator Web Access
The Office Communications Server 2007 R2 Dial-in Conferencing Settings page will not display the user's conference ID when the global meeting policy is set to disallow anonymous users
When a Communications Server (OCS) 2007 user clicks an OCS 2007 R2 audio conference join link, the user receives an incorrect error message
A Communicator Web Access user who joins a conference as a federated user cannot share the computer desktop in Office Communications Server 2007 R2
When a user uses Office Communicator (OC) or Communicator Web Access (CWA) to send an IM message to a federated or Public IM Connectivity user, OC or CWA may give an incorrect notification of the IM delivery status
The selected language is not used when a user on a localized version of Communications Server 2007 R2 signs in to the dial-in conferencing page by using Integrated Windows Authentication and then selects a language from the drop-down list
The logo at the top of the Communications Server 2007 R2 Dial-in Conferencing Settings page is only in English, even after the Communicator Web Access language pack is installed
Users who have special characters in their names cannot sign in to the Office Communications Server 2007 R2 Dial-in Conferencing Settings page
KB 968913 - Conferencing Attendant
Enterprise users can have a conference call without the Presenter/Leader and without realizing that Public Switched Telephone Network (PSTN) users are on hold in Communications Server 2007 R2
KB 967837 - Monitoring Server
Communication Monitoring Server 2007 R2 cannot support more than 100 instances of Mediation Server or of A/V Conferencing Server
KB 967675 - Mediation Server
Fixes not listed yet on Microsoft's site.
KB 967835 - Outside Voice Control
The Outside Voice Control service rejects connections from a new server as non-trusted connections in a Communications Server 2007 R2 deployment
KB 967829 - Response Group Service
Response Group Service cannot start if you assign a certificate that has a wildcard in the Subject Name to Communications Server 2007 R2
Response Group Service cannot start if you assign a certificate that contains a subject alternate names (SAN) list, and the last name is not the pool FQDN to Office Communications Server 2007 R2
After you restart the Communications Server 2007 R2 Response Group Service, the service does not send calls to agents
The Communications Server 2007 R2 Response Group Service does not update its list of trusted hosts at run time
KB 967831 - Enterprise Edition Server
You cannot forward a call between federated users in Communications Server 2007 R2
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 does not detect the changes when Unified Messaging dial plans or UM servers are added
KB 967674 - Unified Communications Manager API 2.0 Core Redist 64-bit
Fixes not listed yet on Microsoft's site.
KB 967830 - Web Components Server
Error message when you open an audit log file for Communications Server 2007 R2: "The process cannot access the log file because is being used any another process"
Response Group Service cannot start if you assign a certificate that has a wildcard in the Subject Name to Communications Server 2007 R2
After you restart the Communications Server 2007 R2 Response Group Service, the service does not send calls to agents
The Communications Server 2007 R2 Response Group Service does not update its list of trusted hosts at run time
You can read about the complete list of fixes here.
The easiest way to get these updates on to your server(s) is to use Microsoft Update, and update all servers so that there is isn't a mix of v3.5.6907.0 servers and v3.5.6907.9 servers.
