Last updated March 20, 2007
Welcome to the Microsoft® Office Communicator 2007 (Public Beta) Release Notes. Refer to this file for information regarding known issues about the Office Communicator 2007 (Public Beta) release.
© 2007 Microsoft Corporation. All rights reserved.
This document contains important information that you should know before you deploy and use the Public Beta version of the Office Communicator 2007 client.
ISSUE: If a user has both internal and external SIP servers configured and signs in to Office Communicator from home without using a virtual private network (VPN), and then connects through a VPN, Office Communicator automatically signs out and signs back in. In this state, user cannot make VoIP calls because Media Relay fully qualified domain name (FQDN) cannot be resolved.
RESOLUTION: The only known workaround is to sign out manually and sign back in re-entering the credentials.
ISSUE: If a user changes the system default device using the Control Panel in Microsoft® Windows, the Office Communicator default speaker and microphone may not update. For example, assume a user with high-fidelity speakers and low-bandwidth speakers makes a call with Office Communicator and realizes that the low-bandwidth speakers are being used as the default. If the user hangs up and changes the default system speakers using the Sounds and Audio Devices Properties in the Control Panel, the user will discover that Office Communicator continues to use the low-bandwidth speakers to play all alert sounds.
RESOLUTION: The user can run the Set Up Audio and Video wizard and manually select the high-fidelity speakers, or the user can exit Communicator and re-start it.
Audio or Video device detection fails on Windows Vista if the user plugs in the device into a different USB port
ISSUE: If a user has selected a device as the preferred audio or video device for conversations using Communicator, and then detaches the device and plugs it into a different USB port, Communicator may not recognize it because Windows gives it a different name. This issue is limited to Windows Vista™.
RESOLUTION: The user can re-attach the device to the port that it was originally attached to.
ISSUE: Emoticons used in an instant messaging session do not appear in an archived message of the conversation history in the Outlook Conversation History folder.
RESOLUTION: There are no workarounds at this time.
ISSUE: When joining a conference scheduled from Outlook, participant names are not saved when the conversation is ended and saved in Outlook.
RESOLUTION: There are no workarounds at this time.
Users upgrading from Office Communicator Beta 3 to Public Beta, who have not moved Public Internet Connectivity ACE from the Blocked Container, should remove the Public Internet Connectivity ACE
ISSUE: Users upgrading from Office Communicator (Beta 3) who have not moved their PIC ACE (AOL® software, Yahoo® Messenger, MSN® network of Internet services or Windows Live™ Messenger services) from the Blocked Access Level to another Access Level must either delete the Public Internet Connectivity Access Control Entry (ACE) from the Blocked Access Level or move it to any other level. If the Public Internet Connectivity ACE is not deleted or moved, users will not receive a notification when a Public Internet Connectivity user tries to add them as a contact. Also, when users try to add a new Public Internet Connectivity contact, and don’t select a non-blocked container for the contact, they will not be able to know if the contact accepted their request. In addition, no IM will be received from already added contacts.
RESOLUTION: Delete the Public Internet Connectivity ACE from the Blocked container or move it to any other container.
ISSUE: The Message Waiting indicator in the Office Communicator window fails to update in some cases when a user running Outlook 2007 in cached mode receives a new Voice Mail or Missed Call item. Also, when users are running Outlook 2007 in cached mode, there have been instances where Voice Mail and Missed Conversations items have failed to appear in the Outlook Voice Mail or Missed Conversations folders.
RESOLUTION: If there is an item in Office Outlook 2007 Voice Mail or Missed Conversations folder, you can enable the Message Waiting Indicator functionality by expanding the Search Folder node in Outlook 2007, clicking on the corresponding Search folder, either Missed Conversations or Voice mail, then selecting an item inside one of the folders and marking it read or unread. If there are no items in the Voice Mail or Missed Conversations folders, there is no workaround at this time. The Office Communicator team is working with the Office Outlook team on a fix.
ISSUE: After installing the Live Meeting console, the Additional Actions entry points do not appear in the Office Communicator user interface, so users cannot start a Live Meeting session from Communicator.
RESOLUTION: The Live Meeting Service needs to be configured using the Live Meeting console or the Conferencing Add-In for Microsoft Office Outlook. To configure Live Meeting from the console, start Live Meeting, click the Down arrow in the Live Meeting Title bar, click Open User Accounts, and then under Service, specify the required information, and then click Test Connection. Before Live Meeting entry points appear in the Office Communicator user interface, the user must exit Communicator and then restart it. To do this, the user can right-click the Communicator icon in the system tray and then click Exit, restart Communicator, and then sign back in to Communicator.
ISSUE: Office Communicator cannot open a note created with Microsoft® Office OneNote™ if a graphic has been added to the note.
RESOLUTION: Do not add graphic images to OneNote files that are linked to Office Communicator conversations.
ISSUE: Office Communicator presence is not displayed in Office Outlook or Office SharePoint.
RESOLUTION: Set the following registry keys to make Communicator the default application for Presence within Office applications.
REG_DWORD HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\PersonaMenu\RTCApplication=3
REG_DWORD HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\PersonaMenu\RTCApplication=3
ISSUE: When a user signs out of Office Communicator, contacts in the Communicator Contact List could show presence information that is out-of-date.
RESOLUTION: Restart Office Communicator or restart Office Outlook.
ISSUE: If a user shuts down Office Communicator and navigates between e-mails within Outlook while Communicator is shutting down, Outlook may disconnect from Communicator and show no presence, even if Communicator is restarted
RESOLUTION: Restart Office Outlook.
ISSUE: If a user’s e-mail address, as entered into an Outlook e-mail, cannot be resolved to a SIP address in the Outlook Address Book or through Office Communicator, then presence cannot be retrieved for that user.
RESOLUTION: Set the SetOnlineStatusLevel registry key to allow Outlook to make a call to Microsoft Exchange to help resolve the SIP address for users. Setting this key can help particularly when the user’s Exchange address (x400/X500) is in the e-mail.
HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\IM] "SetOnlineStatusLevel"=dword:00000003
ISSUES: In Office Communicator 2007 (Public Beta), Public Internet Connectivity users are automatically assigned to the Blocked Access Level to avoid spam. As a result, users who add Public Internet Connectivity contacts to their Contact List do not receive alerts from these contacts.
RESOLUTION: If users want to receive notifications from Public Internet Connectivity users in their Contact List, they must define a domain Access Control Entry (ACE) level that enables them to receive notifications.
ISSUES: In order to integrate applications under the Action menu in the Office Communicator window or the Conversation window, registry keys must be created under hklm\software\microsoft\communicator\session manager\apps\<GUID>. During the uninstall of Office Communicator, the Communicator hive is removed. Therefore, if you uninstall and reinstall Office Communicator, you no longer see entry points under the Action menu to invoke the plugged-in applications.
RESOLUTION: Export the session\manager\apps hive into a .reg file before uninstalling Office Communicator. After reinstalling Office Communicator, import values from the .reg file to Office Communicator.
ISSUES: Interoperability issues exist between the Office Communicator 2005 client and Office Communicator 2007 client.
Application-sharing with NetMeeting is no longer available with Office Communicator 2007.
Support for plugging in custom applications has changed between Office Communicator 2005 and Office Communicator 2007. See the Application Integration section for more information.
Passing contacts in a tabbed page using HTTP GET/POST is no longer supported. With Office Communicator 2007 (Public Beta), developers can pass contextual information to a tabbed page by invoking a script in the tab page. For more information about custom tabs, see the Microsoft Office Communicator 2007 (Public Beta) Deployment Guide.
Enhanced Presence states in Microsoft Office Communicator 2007 are not visible to Office Communicator 2005 clients.
Location-based forwarding is no longer available in Office Communicator 2007.
The video stream freezes intermittently during audio/video calls between Office 2005 and Office Communicator 2007.
When an Office Communicator 2005 user calls an Office Communicator 2007 enterprise-voice enabled number, the Office Communicator 2007 user cannot add video to the call.
Adding or removing audio/video modes is not supported in a call from a Communicator 2007 client to a Communicator 2005 client if the Communicator 2005 client encryption level is set to “required” or “reject” by domain policy.
When a Communicator 2007 user has an IM conversation with a Communicator 2005 user, the 2007 client adds that user to the Recent Contacts list. As a result, the 2005 client user sees an alert indicating they have been added to the Contact List of the Communicator 2007 client. In reality, the user is only added to the Recent Contacts list, not the Contact List. Currently there is no way for a Communicator 2005 client user to distinguish between alerts being generated by being added to a Recent Contacts list and alerts generated by being added to a Contact List.
RESOLUTION: None.
Enhanced Presence states in Office Communicator 2007 are not supported in Windows Messenger 5.1
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Windows Media, Active Directory, DirectX, Internet Explorer, OneNote, Outlook, PowerPoint, and RoundTable are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.