Published: December 2005
Welcome to Microsoft® Office Communicator Web Access Release Notes. Refer to this file for information on known issues about Communicator Web Access.
This document contains important information you should know prior to deploying and using Microsoft® Office Communicator Web Access.
These materials are provided "as-is," for informational purposes only.
Neither Microsoft nor its suppliers makes any warranty, express or implied, with respect to the content of these materials or the accuracy of any information contained herein, including, without limitation, the implied warranties of merchantability or fitness for a particular purpose. Because some states/jurisdictions do not allow exclusions of implied warranties, the above limitation may not apply to you.
Neither Microsoft nor its suppliers shall have any liability for any damages
whatsoever, including consequential incidental, direct, indirect, special, and
loss of profits. Because some states/jurisdictions do not allow exclusions of
implied warranties, the above limitation may not apply to you. In any event,
Microsoft's and its suppliers' entire liability in any manner arising out of
these materials, whether by tort, contract, or otherwise shall not exceed the
suggested retail price of these materials.
Issue: Setup may fail if the destination folder has
non-ASCII characters in the folder name.
Resolution: Use standard ASCII characters in the
destination folder name.
Issue: When a user enters his or her user name in Unicode characters and tries to log on using forms-based or integrated Microsoft Windows® operating system authentication, logon fails. The user sees the error message, "Cannot sign in. The password or sign-in name may be incorrect. Make sure that your sign-in name matches the user account and try again." Although Live Communications Server and Office Communicator support user names containing Unicode characters, IIS and browser limitations prevent their use in Communicator Web Access.
Resolution: Do not use Unicode characters in the user name or password.
Issue: Depending on the capacity of the user’s computer, during sign-in, a user who has a large number of contacts or a large number of ACEs in his or her permissions list may see a warning stating that a script on the page is causing the browser to run slowly. In this case, the sign-in process could use up to 100% of the CPU capacity.
Resolution: To allow the sign-in process to continue, choose the option that allows the script to continue running.
Issue: After Communicator Web Access is installed, it takes several minutes for Live Communications Server to update the trust list. During this time, users will be unable to sign in to Communicator Web Access.
Resolution: Wait for updates to complete (typically 15 minutes or more, depending on the Microsoft Active Directory® directory service replication configuration). Then attempt to sign in again.
Issue: Netscape Browser 8.0
users must configure the appropriate pop-up blocker and trust settings for
Communicator Web Access.
Resolution: Configure
Netscape 8.0 pop-up blockers and trust settings for the Communicator Web Access
site as follows:
1.
Display the
Communicator Web Access sign-in page.
2.
Right-click the
3.
Click the Advanced
tab. Under Web Features, deselect the Open requested pop-ups in new
tab checkbox. Select the Allow unrequested pop-up windows checkbox.
4.
Click Tools,
and then click Options. Click Tab Browsing. Under Tab Browsing,
deselect the Open a new tab instead of a new window checkbox. Deselect
the Open non-requested pop-ups in a new tab checkbox. Click OK.
Issue: Communicator Web Access users running Netscape Browser 8.0 on Windows
operating systems may experience dialog box sizing issues. Certain dialog boxes
may be rendered too small to display the text.
Resolution: In Netscape 8.0, change the rendering engine
for the Communicator Web Access site from Firefox to Internet Explorer. To do
this, right-click the Microsoft
Office Communicator Web Access tab,
and then click Show Site Controls. Under Rendering Engine, click Internet Explorer.
Issue: If KB832894 is not applied to computers running Internet Explorer 6, the Toast, Options, and ACL Web Page Dialog headings fail to display correctly. Without the patch, the headings displays as -- Web Page Dialog. With the patch applied, the headings correctly display as {Toast | Options | ACL} -- Web Page Dialog. If Windows XP SP2 or later is installed on the computer, this issue does not appear.
Resolution: Apply KB832894, available at http://support.microsoft.com/kb/832894.
Issue: For Internet Explorer running on the Windows 2000, Windows XP, or Microsoft Windows Server™ 2003 operating system, when a user who is actively using another program receives an incoming IM desktop alert ("toast") in Communicator Web Access, the focus switches from the program to the desktop alert. In Windows XP, this issue occurs in certain applications such as the main window of the Microsoft Office Outlook® messaging and collaboration client. In Windows 2000, Windows XP, and Windows Server 2003, this issue also occurs if the ForegroundLockTimeout registry key, which controls focus behavior, has been changed from its default setting of 30d40. If this setting has been changed to 0, the focus issue will occur.
Resolution: Set the ForegroundLockTimeout registry key to 30d40. You can modify this registry key by using the regedit command or by using the Microsoft PowerToy TweakUI.exe. The ForegroundLockTimeout registry key is usually located in the registry under HKEY_CURRENT_USER/Control Panel/Desktop. If the registry key does not exist in this location, conduct a search in the registry. Alternatively, you can run the TweakUI.exe tool and select the option "Prevent applications from stealing focus." The TweakUI.exe tool for Windows XP, for example, is available at http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx.
Note: In Windows XP, even if you change the ForegroundLockTimout setting, the problem will still occur with the main window of the Microsoft Office Outlook® messaging and collaboration client.
Issue: When a user logs on to both Windows Messenger 5.1 and Communicator Web Access either on the same computer or on separate computers, the user's status in Windows Messenger does not display correctly.
Resolution: None. Users can experience such inconsistencies while logged in to both Windows Messenger 5.1 and Communicator Web Access.
Issue: If the proper case is not used when entering the SIP URI, for example when adding a contact, presence information cannot be retrieved.
Resolution: Wherever a SIP URI is used, ensure that the case exactly matches the SIP URI specified in Active Directory. This requirement also applies to Communicator 2005 users who want to interoperate with Communicator Web Access users.
Issue: Windows Installer 3.0 or later is required for installation of Communicator Web Access Manager.
Resolution: Before installing Communicator Web Access Manager on a remote management computer, ensure that Windows Installer 3.0 or later is installed.
Issue: When managing a Communicator Web Access server remotely, if you are logged on to the local management computer with an account that does not have local administrator rights on the remote server, you will not be able to perform any management actions on the remote Communicator Web Access server that require access to the remote certificate store. This issue occurs even if, when connecting to the remote Communicator Web Access server, you use a different account that has local administrator rights on the remote server.
Resolution: First log on to the local management computer with an account that has local administrator rights on the remote server. Then connect to the remote Communicator Web Access server.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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.
© 2005 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Outlook, Windows, Windows NT, Windows Server,
and Windows Vista are either registered trademarks or trademarks of Microsoft
Corporation in the
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.