Last updated: April 11, 2006
Welcome to the
© 2006 Microsoft Corporation. All rights reserved.
This document contains important information you should know before you deploy and use Communicator Mobile.
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: If you do not remove all copies of Communicator Mobile from your device and desktop computer before you install a new version, unexpected behavior can result during installation or when you later try to remove Communicator Mobile. When you install a new copy of Communicator Mobile without removing previous versions, you will see multiple Communicator Mobile Today or Home screen add-ins, as well as multiple entries for Communicator Mobile in the Programs folder of your mobile device.
Resolution: Remove all previous
installations of Communicator Mobile before installing a new version or
reinstalling an existing copy. See the
Issue: On a smartphone that is running the Windows Mobile 2003 SE software, you cannot remove Communicator Mobile when the Communicator Mobile Home screen add-in program is running.
Resolution: Modify the device’s Home screen layout setting so that the Communicator Mobile Home screen add-in program is no longer displayed on the Home screen. Restart the device, and then remove Communicator Mobile.
Issue: When you use Microsoft ActiveSync technology to install Communicator Mobile on a Pocket PC that is running Windows Mobile 2003 SE, you choose to install Communicator Mobile on a storage card, but it is installed on the device instead.
Resolution: Communicator
Issue: When you use ActiveSync to remove Communicator Mobile, you click Remove to remove the program from the device and the installer file from your desktop computer. However, the Communicator Mobile installer file is not removed from your desktop computer.
Workaround: After you use
ActiveSync to remove Communicator Mobile from the device, remove the installer
file from your desktop computer by using Add or Remove Programs in the
Control Panel. See the
Issue: If the connection type on the mobile device changes while you are using Communicator Mobile—for example, you move from GPRS to Wi-Fi, or you cradle and uncradle the device—Communicator Mobile signs out automatically before attempting to sign in again by using the new connection type. You are disconnected from any conversations in which you are currently a participant.
Resolution: Avoid changing
connection types during a conversation. If you do change connection types
during a conversation and are signed out, Communicator Mobile automatically
saves the history of each conversation as a draft in the Drafts folder of your
device’s
Issue: On devices that are running Windows Mobile 2003 SE, Communicator Mobile does not sign in automatically when you connect to the network by using ActiveSync.
Workaround: None. If you have configured Communicator Mobile to sign in automatically, the program will automatically retry sign-in after a few minutes.
Issue: When you use a Communicator Mobile contact card to call a contact’s phone number, the GPRS data connection is disconnected, thereby causing Communicator Mobile to sign out.
Workaround: None at this time. Windows
Issue: When you lose the network connection for any reason, current conversations are ended without warning and without the option to save.
Workaround: None. If, however, you do lose the network connection during a conversation, Communicator Mobile automatically saves the history of each conversation as a draft in your device’s Outlook Drafts folder.
Issue: When you try to log in to Communicator Mobile, the message Unable to connect to network appears, even though you are connected to the network over Microsoft ActiveSync technology or Wi-Fi.
Resolution: Verify that you have
correctly configured a proxy server for your mobile device. For information about configuring
a proxy server for your mobile device, see “Troubleshooting” in the
Issue: When you try to log in to Communicator Mobile, the message Wrong Server Name appears, even though you are using the correct server name, user name, and password.
Resolution: Verify that you have an
active, available data connection (ActiveSync, GPRS, 1xRTT, or Wi-Fi), and then
try again.
Issue: When you enable Flight mode on your mobile device while you are signed in to Communicator Mobile, Flight mode is disabled after approximately thirty seconds.
Resolution: Enable Flight mode once more. The second time, the issue does not recur.
Issue: You have a large number of contacts, and one of the following occurs:
· The Contacts list does not display presence for some or all of them.
·
Communicator
·
Communicator
Resolution: Your device may be
low on memory. Communicator
Communicator
Issue: When you use Office Communicator 2005 on your desktop to set the permission type of All Other Contacts to Block, the presence status of the contacts that are affected does not change to Blocked in the Communicator Mobile Contacts list. Instead, each contact’s actual presence status, as set by each contact, is displayed.
Workaround: Configure Block or Allow permissions for individual contacts.
Issue: Call forwarding settings in Communicator Mobile and Office Communicator are always the same. For example, if both programs show that call forwarding is enabled, and you then disable call forwarding on Communicator Mobile, call forwarding is also disabled on Office Communicator.
Resolution: This behavior is by design. Call forwarding settings affect all Communicator programs that you use. When you change your call forwarding settings using one program, confirm that you have the intended effect with both programs.
Issue: When you use the Communicator Mobile Home screen add-in program to open Communicator Mobile, or if you use the Home screen add-in program immediately after ending a call, the program is unresponsive.
Resolution: After the call has ended, wait for several minutes before using the Home screen add-in to open Communicator Mobile. Or use the Back button on the smartphone to open Communicator Mobile instead of using the Home screen add-in program.
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.
© 2006 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Windows Mobile, Windows NT, Windows Server, Windows
Vista,, Active Directory,
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.