Microsoft Office Communicator 2005

[shamodeyu]

from betamail:

We are happy to announce the release of "Istanbul Beta 2 (build 422)" and to

reveal its new name - Microsoft Office Communicator 2005. On the heels of this

morning's launch of Communicator by Bill Gates and alumni of the hit TV show

"The Apprentice," we are excited to offer our Beta customers first access to

Communicator via the "Downloads" section of Beta Place. Also available on Beta

Place is the Live Communications Server 2005 Address Book Service, the Microsoft

Office Communicator Documentation, and Release Notes. Please read the Release

Notes and Documentation carefully so that you may fully understand the

requirements and have a successful lab deployment of "Communicator".

Communicator has advanced dramatically since the Beta 1 release. Now that Beta

2 has arrived, we hope you will join with us to deploy it and begin your

testing. We will be offering some great incentives and contests in the very near

future, so stay tuned for more information.

Microsoft? Office Communicator 2005 Beta 2 Release Notes

Welcome to the Beta 2 release of Office Microsoft? Office Communicator 2005. Refer to this file to obtain known issues about Microsoft Office Communicator 2005 for this Beta release.

Released: March, 2005

Copyright

? 2005 Microsoft Corporation. All rights reserved.

About This Document

This document contains important information you should know prior to deploying and using Microsoft Office Communicator 2005.

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.

Back to Top

Known Issues

PSTN Conferencing is not supported in Communicator 2005 Beta 2

Issue: PSTN Conferencing not supported in Communicator 2005 Beta 2.

Resolution: None.

Installing Communicator 2005 when Microsoft Office applications and Windows Messenger 5.1 are running

Issue: If you have Microsoft Outlook? 2003 or any other Microsoft Office application and Microsoft Windows? Messenger 5.1 running when you install Communicator 2005, the presence integration in Communicator 2005 may be disabled until your restart the Office applications.

Resolution: Restart all Microsoft Office Applications and Windows Messenger. Additionally, if you are running a Microsoft Internet Explorer session to a Microsoft SharePoint Server portal then you must close and restart Internet Explorer.

Installing Microsoft Office Communicator on removable media is not supported.

Issue: If you attempt to install Microsoft Office Communicator on removable media the installation procedure will complete and Microsoft Office Communicator will function up until the external media is removed.

Resolution: Uninstall Microsoft Office Communicator from the removable media. Note: the process of uninstalling is possible regardless of whether the media is attached or removed.

Uninstalling Microsoft Office Communicator 2005 Beta 2 requires manually setting the SIP configuration service account for Windows Messenger 5.1 clients

Issue: Users who have uninstalled Microsoft Office Communicator Beta 2 from computers running Microsoft Office Outlook 2003, Windows Messenger 5.1, on Windows XP SP2 computers will need to reset their Messenger 5.1 SIP configuration service account information re-enable presence.

Resolution: To re-enable presence for Windows Messenger 5.1 you must do the following:

1. From the Windows Messenger window Click Tools, then click Options.

2. Click Accounts.

3. Under SIP Communications Service Account, click the My contacts include users of a SIP Communications Service.

4. Enter the account information in the Sign-on name box.

5. Click Ok.

Application Sharing and whiteboard not supported between computers running Windows 2000 SP4 using Windows Messenger 5.1 and computers running Windows XP SP2 using Communicator 2005

Issue: Computers running Windows XP SP2 using Communicator 2005 support T120 level security by default. Windows 2000 SP4 using Windows Messenger 5.1 does not support T120 security by default.

Resolution: Set the following registration key:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Conferencing\CallSecurity = 2.

When sharing applications from a computer using multiple monitors the application being shared must be displayed on the primary monitor

Issue: When using multiple monitors, one monitor serves as the primary display. Applications will open on the primary monitor or not, depending on the monitor they were they were displayed the last time they were closed. If you are using Communicator 2005 on a computer sharing multiple monitors, the shared application must be displayed on the primary display. If the application is not displayed on the primary monitor?displayed on any secondary monitor?then the user attempting to view the shared application will view the application sharing window, but not the application being shared.

Resolution: Move the application being shared to the primary monitor.

Communicator 2005 must be manually started after initial installation to open automatically during subsequent logon instances

Issue: Communicator 2005 is installed by the administrator for another user(s) and then logs off the computer without starting Communicator. When the user logs onto the computer, Communicator 2005 does not automatically launch. The user must do a one-time manual opening of Communicator 2005 for subsequent logon instances to occur automatically.

Resolution: Manually start Communicator 2005. Subsequent logon instances will launch Communicator 2005 automatically

Setting monitor to high contrast mode requires Communicator 2005 to be restarted

Issue: Users with computers running Communicator 2005 where the video resolution mode is subsequently reset to high contrast mode will not be able to view the Communicator main window.

Resolution: Close and re-open Communicator.

To view the phone number for a personal contact in Communicator 2005 Beta 2 the phone information must be added to Outlook personal contacts prior to the contact being created in Communicator 2005

Issue: When you enter a new personal contact (not in the GAL) in Communicator 2005 you cannot enter or view phone information. Personal contacts that already exist as contacts in Outlook (and are stored in the GAL) or in the Windows Address Book (WAB) display phone information. To add and/or view phone information not stored in the GAL (for example AOL or Hotmail contacts) you must create the contact in Outlook. After the personal contact has been created in Outlook the contact can be found in Communicator 2005 contact search and phone information can be displayed and dialed.

Resolution: To enter and view the phone number for a personal contact in Communicator 2005 you must first enter the personal contact information in Outlook. For existing contacts in Communicator 2005 that are not personal contacts in Outlook, you must delete the contact from Communicator 2005, create the personal contact in Outlook, and search for the contact in Communicator 2005.

Presence status for a requested new contact may appear as ?offline? until after the contact has accepted the request

Issue: A new contact found in Search may display presence as ?online.? When you add the contact to your list, the contact presence may change to ?offline.? The presence status for the new contact will not appear as ?offline? until after the new contact has accepted the request to be added as a new contact.

Note: the ACL for the new contact in this case is set to ?notify? and thus will remain ?offline? until the request to be added is accepted or rejected.

Resolution: Continue using Search to view the contacts presence information until the new contact either accepts or rejects the request. If the user accepts, the presence information will be up to date in the contact list.

Cannot start application sharing when separate application is using local port 1503

Issue: Communicator 2005 uses local port 1503 for establishing data collaboration requests and listening for incoming requests for application sharing. If another application on your computer is using port 1503 then your invite for sharing will fail. Likewise, if your computer has an application using port 1503 and a participant attempts to share an application the port will be blocked.

The following error result:

Invite error: You have sent an invite for a data collaboration session. Communicator 2005 cannot establish this connection because another application is using resource (Port 1503). You must close the session using port 1503 to open a data collaboration invite.

Receive error: You have received an invite for a data collaboration session. Communicator 2005 cannot establish this connection because another application is using resource (Port 1503). You must close the session using port 1503 to open a data collaboration invite.

Resolution: You must close the session using port 1503 to open a data collaboration invite.

Security policy for Communicator 2005 application sharing must be set using the NetMeeting policy settings for encrypting shared applications

Issue: Policy setting SetSecurityOptions (REG_DWORD) specifies whether encryption is disabled, required, or optional when Communicator 2005 sends and receives data using its collaboration features: whiteboard and application sharing. This setting is disabled for Communicator 2005.

Resolution: Security policy for Communicator 2005 application sharing must be set using the NetMeeting policy settings for encrypting shared applications.

Set the Conferencing registry key:

1. Using regedt32.exe, navigate to: HKEY_CURRENT_USER\Software\Policies\Microsoft\Conferencing

2. Create the DWORD CallSecurity

3. Set one of the following:

1 - required

2 ? rejected

Non-normalized phone numbers in AD will not appear in Communicator 2005 personal options

Issue: Office Communicator 2005 requires all phone numbers to be in standardized TEL URI format for reverse number lookup functionality and for dialing. Office Communicator 2005 uses Active Directory and Outlook (if present) as phone number sources. The following is an example of TEL URI format:

tel:+14255551212;ad-rdn=telephoneNumber;displayName=(425)555-1212

Phone numbers stored in Active Directory and Outlook in the TEL URI format, are published by the Address Book Serice to the Office Communicator 2005. Any numbers not in the correct format must be converted to the correct format: normalized. Normalization must be performed prior to deploying telephony if you have existing numbers in Active Directory and Outlook. If the phone numbers are not normalized correctly then they will not appear in Communicator

Resolution: Any numbers not in the correct format must be converted to the correct format.

Communicator 2005 will block potentially threatening files during File Transfer.

Issue: Communicator 2005 will block potentially threatening files during File Transfer. These files may or may not be a threat to you organization but have been blocked for Security.

Resolution: For files that you want to allow you can configure group policy to accept select file extensions (policy IAttachmentExecute).

To manually load LCClient.adm in Group Policy Object Editor

1. Open the Group Policy Object Editor using the MMC (snap-in the GPO if you have not already done so).

2. Click User Configuration and click Administrative Templates.

3. Click Windows Components and click Attachment Manager.

This policy setting allows you to configure the list of high risk file types. If the file attachment is listed as a high risk file type part of the restricted zone, Windows blocks the user from accessing the file. If the file is from the Internet zone, Windows prompts the user before accessing the file. This inclusion list takes precedence over the Medium and Low risk inclusion lists (where an extension is listed in more than one inclusion list.

Data Collaboration invites greater than 11 participants appear inoperable but do not fail

Issue: A user invites 11 or more participants to a data collaboration session (for example, sharing an application). Communicator 2005 may appear to not function slowly update presence and the roster. However, the application sharing session can still be done.

Resolution: If you intend on inviting 11 or more participants to an application sharing session, then begin by inviting 4 or 5 participants and continue to invite as many participants as you would like up to 20 participants.

Copyright

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. 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.

? 2005 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, Outlook, Windows, Windows NT, and Windows Server 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.

news source

[at0mican]

Can Office Communicator connect with other MSN Messenger users?

[CoLdFuSi0n]

this is old news