Friday, December 11, 2009

Update Rollup 1 for Exchange Server 2010 (KB976573)

get it here

Issues that the update rollup fixes.

Update Rollup 1 for Exchange Server 2010 fixes the issues that are described in the following Microsoft Knowledge Base articles:

977439 (http://support.microsoft.com/kb/977439/ ) Exchange Server 2010 users cannot open certain attachments when they access their mailboxes by using Outlook Web App

977551 (http://support.microsoft.com/kb/977551/ ) Meeting requests that are sent to a room mailbox are not processed in Exchange Server 2010

977552 (http://support.microsoft.com/kb/977552/ ) Exchange RPC Client Access service crashes in the Handler.dll that is located on an Exchange 2010 Client Access service server

977553 (http://support.microsoft.com/kb/977553/ ) Exchange RPC Client Access service crashes in Parser.dll on the Exchange Server 2010 CAS server

977554 (http://support.microsoft.com/kb/977554/ ) The subject or body of a message that is hosted in an Exchange Server 2010 mailbox is not set as expected

977555 (http://support.microsoft.com/kb/977555/ ) The message body is inaccessible when the property conversion from PR_BODY_HTML to PR_BODY fails

977556 (http://support.microsoft.com/kb/977556/ ) The body text of an e-mail message is invisible after you create exceptions for a recurring appointment or for a recurring meeting by using a CDO application together with Exchange Server 2010

977557 (http://support.microsoft.com/kb/977557/ ) An E_FAIL error occurs when you create an exception to a meeting request by using a CDO application for a Microsoft Exchange Server 2010 mailbox

977558 (http://support.microsoft.com/kb/977558/ ) A folder name is not changed when you try to move and then rename the folder in an Exchange Server 2010 mailbox by using the CopyFolder method of the IMAPIFolder interface

977559 (http://support.microsoft.com/kb/977559/ ) The location of a meeting or an appointment is not updated on an Exchange Server 2010 mailbox

977560 (http://support.microsoft.com/kb/977560/ ) Update fails when you use a CDO application to update a recurrence task on Exchange Server 2010

977561 (http://support.microsoft.com/kb/977561/ ) VSS backup process stops responding when you try to perform a Volume Shadow Copy Service (VSS) backup for Exchange Server 2010 databases

Monday, December 7, 2009

Microsoft and Cisco: Joint Interoperability Support Statement

Get it here

Communications server team’s Blog on the subject

Very good blog here on “Make sure you know what you’re buying.”

Cut and paste from this document*************************

Cisco UC IntegrationÔ for Microsoft Office Communicator

Microsoft provides support for its published APIs[1] for Microsoft Office Communications Server and Microsoft Office Communicator to all its ISV partners.  Cisco, a Microsoft Gold Certified Partner, uses these published APIs to develop the Cisco UC IntegrationÔ for Microsoft Office Communicator product.  Microsoft is pleased that Cisco has chosen to leverage Microsoft API’s to provide functionality for our mutual customers as an ISV. 

Cisco, as the developer of the Cisco UC IntegrationÔ for Microsoft Office Communicator, provides support for this product.  Microsoft will provide ongoing support for the published APIs for Microsoft Office Communications Server and Microsoft Office Communicator to our ISV’s, including Cisco.   Microsoft does not provide direct support for the Cisco UC IntegrationÔ for Microsoft Office Communicator.  The Microsoft UC platform will continue to evolve as the industry evolves and customer requirements change, and as with our broader ISV community, Microsoft is fully committed to working with Cisco so they can provide quality support for our mutual customers with future versions of Microsoft Office Communications Server and Office Communicator.

Remote Call Control is supported by Microsoft in Office Communications Server 2007 and Office Communications Server 2007 R2 and will continue to be supported for customers upgrading their Remote Call Control deployments to the next release of Office Communications Server. Microsoft has announced the deprecation of Remote Call Control in Office Communications Server. As a result, in the next release of Office Communications Server, new deployments of Remote Call Control will not be supported by Microsoft.

Direct SIP Interoperability

Microsoft has tested and supports Direct SIP interoperability between Cisco Unified Communications Manager versions 4.x and 5.x and Office Communications Server 2007 and Office Communications Server 2007 R2, as documented on the Microsoft Unified Communications Open Interoperability Program website. While Cisco offers and supports a SIP interface with Cisco Unified Communications Manager versions 4.x and 5.x, interoperability using this interface is only supported for systems that have been tested and documented on the Cisco Interoperability Portal. Cisco has not tested Direct SIP interoperability between Office Communications Server 2007 and Office Communications Server 2007 R2 and Cisco Unified Communications Manager versions 4.x and 5.x.

Cisco has tested and supports Direct SIP interoperability between Microsoft Office Communications Server 2007 and Cisco Unified Communications Manager versions 6.1 and 7.02. Microsoft has tested and supports Office Communications Server 2007 and Office Communications Server 2007 R2 with Cisco Unified Communications Manager version 6.11.

To facilitate interoperability support for our joint customers, both Cisco and Microsoft are members of TSANet, an independent third-party organization that helps coordinate multi-vendor support.