Last updated:
Welcome to the release notes for Microsoft® Office Communicator Mobile (2007 release). Refer to this document to review known issues and potential workarounds for the 2007 release of Communicator Mobile.
This document contains important information that you should know before you deploy and use Communicator Mobile (2007 release).
Issue: By default, when you install Communicator Mobile on a mobile device running Windows Mobile 6.0, the Communicator Mobile cabinet (.cab) file is not removed from the device after installation is complete.
Resolution: You can delete the Communicator Mobile cabinet file manually.
Issue: When you use Microsoft®
ActiveSync® technology (or Windows Mobile Device Center 6, if you are using
Windows Vista®) 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.
Resolution: After you use
ActiveSync (or Windows Mobile Device Center) to remove Communicator Mobile from
the device, remove the installer file from your desktop computer by using Add
or Remove Programs (or Programs and
Features, if you are using Windows Vista) in the Control Panel. See the
Issue: Sometimes, when you use Windows Mobile Device Center 6 to install Communicator Mobile, the installer runs successfully on the computer, but Communicator Mobile is not installed on the device.
Resolution: If you use a computer
running the Windows Vista operating system to install Communicator Mobile (2007
release), and you have User Account Authentication enabled, you must run the
Communicator Mobile installer as an Administrator in order to successfully
install Communicator Mobile on the device. See the
Issue: When you select the Run and sign in on start option in Communicator Mobile, you are signed in to the program automatically, but your device also brings the program into focus in the foreground.
Resolution: Currently, there is no resolution. A fix is planned for a future release.
Issue: In the current release, if you have 60 or more contacts in your Contact List, the Communicator Mobile sign-in process can take longer. In addition, having more than 60 contacts can cause the battery to drain very quickly. Having a large number of contacts in your Contact List can also cause Communicator Mobile to stop responding altogether.
Resolution: A fix may be available for a future release. In the current release, if Communicator Mobile has stopped responding, delete contacts by using Office Communicator 2007, and then restart your mobile device before you try to sign in again.
Issue: In the current release, when the device becomes active after an idle period and Communicator Mobile is brought to the foreground (for example, when you view the Contact List or a conversation), Communicator Mobile can seem unresponsive. This can happen if you selected the Disable presence updates when application is not used checkbox in Communicator Mobile Options in order to preserve battery life. If Communicator Mobile is configured to suspend presence updates during idle periods, Communicator Mobile can be unresponsive while it attempts to update presence status for all your contacts when you resume using the program.
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 Microsoft® Office
Outlook® messaging and collaboration client.
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.
Resolution: Currently, there is
no resolution. Windows
Issue: When you lose the network connection for any reason, current conversations are ended without warning and without the option to save.
Resolution: Currently there is no resolution. If, however, you 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: Communicator
Resolution: When Windows Mobile powered devices are low on program memory, the operating system automatically stops some programs from running, in order to free up memory. Programs that have been activated, but have not been used recently are subject to shutdown by the operating system. In order to help prevent the operating system from stopping Communicator Mobile, close all programs that are not currently in use, and then restart Communicator Mobile.
Issue: Communicator
Resolution: When you make or
receive a call on a Windows Mobile powered device, the GPRS connection is put
on hold. Therefore, when you are in a call, Communicator is unable to
communicate with the server. If Communicator is unable to communicate with the
Office Communications Server for a period of five to ten minutes or more,
Communicator disconnects. Furthermore, on some smartphone devices, when you
press the END (call) button to disconnect from a call or to lock the device,
the GPRS connection is disconnected. Communicator
To ensure
that Communicator Mobile automatically tries to reestablish a network
connection and sign in to the server, select the Reconnect if network lost check box in Communicator Mobile Options. If
Communicator Mobile is configured to automatically sign in, Communicator Mobile
will retry sign-in five times, beginning 15 seconds after it is initially
disconnected.
If you do
not want to disconnect GPRS with the END (call) button, you can set the value
of the following registry key to 1:
HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections\(GPRS
connection name)\AlwaysOn.
Issue: You have been granted Team level access to a contact’s presence status information, but you are unable to view the details of that contact’s meeting schedule or meeting location.
Resolution: Currently, there is no resolution. A fix may be available for a future release.
Issue: When you use the Group by Availability feature, contacts that are unavailable, including contacts that are Away, are sorted into the Offline group instead of an Unavailable group.
Resolution: In the current release, Communicator Mobile does not sort the Contact List in the same way that Communicator (2007 release) sorts the Contact List. Currently, there is no resolution. A fix may be available for a future release.
Issue: You cannot add a user of a public IM service provider to an existing conversation. Similarly, you cannot invite additional participants to an existing conversation with a user of a public IM service provider.
Resolution: Currently, there is no resolution. A fix may be available for a future release.
Issue: If you use the Communicator Mobile Home screen add-in program to open Communicator Mobile, or use the Home screen add-in program immediately after ending a call, the program is unresponsive.
Resolution: After the call ends, wait for several minutes before using the Home screen add-in to open Communicator Mobile. Alternatively, you can use the Back button on the smartphone to open Communicator Mobile, instead of using the Home screen add-in program.
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
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.