This section describes issues known to exist in Instant Messenger at the time of release in the following sections:
Idle detection is not implemented on Mac OS.
If a user leaves an Instant Messenger session, the absence is not automatically detected.
Workaround: Mac OS users need to explicitly set their presence status as AWAY, prior to leaving.
Custom statuses cannot be removed.
Workaround: The least used statuses are eventually removed. To remove one immediately, add five new customized statuses and the oldest one will disappear.
Changes users make on the Settings dialog box Privacy tab are saved as the changes are made, not when the user clicks OK.
For this reason, if you click Cancel after making changes on this tab, the changes are saved anyway.
Users cannot set priority for Idle or Away status when Instant Messenger is launched from the Java plug-in
The options for setting priority for idle and away status are not displayed in the user interface when Instant Messenger is launched using the Java plug-in. This does not occur when launching Instant Messenger from Java Web Start.
Launch Instant Messenger using Java Web Start.
Select Tools|Settings to bring up the Settings dialog box.
Select the Advanced Tab.
Set priority for Idle and Away as desired. More information for these options is available from the online help.
Cannot use Instant Messenger 2005Q4 or earlier with redirect server.
Older versions of Instant Messenger do not support XMPP redirection.
Workaround: Upgrade Instant Messenger to 2006Q1 or later
(Windows Only) Desktop Integration Settings option is missing when the client is launched from the Java plug-in on Windows
The Java plug-in does not support desktop integration. As a result, the Desktop Integration Settings option is missing from the General tab of the Settings dialog box.
Workaround: Invoke the application from Java Web Start.
The Instant Messenger Login dialog box does not necessarily display the server the end user last successfully logged into.
This behavior is inconsistent with the behavior for username, where the last successfully used username is displayed in the Login dialog box.
On the Login dialog box, click More Detail.
Select the appropriate server from the Server drop-down list.
If a client connected over SSL becomes disconnected and attempts to reconnect, the user will be prompted to accept the certificate again.
Instant Messenger unexpectedly disconnects.
In deployments with Access Manager, if Access Manager times out, Instant Messenger disconnects and cannot reconnect until the Instant Messaging server is restarted.
Workaround: Download the product patch from SunSolve Online.
Problems with Instant Messenger after reconnecting to server.
If Instant Messenger becomes disconnected from the server, it may not function properly when it reconnects. For example, presence information may not be displayed correctly, and conference rooms will not work.
Workaround: To join a conference room after a disconnect occurs, click the chat icon instead of double-clicking the conference on the Conferences tab. In addition, you can download the product patch from SunSolve Online.
User connections terminated by Access Manager do not log users out of Instant Messenger.
If Access Manager terminates a user's current session, the user is still logged in to Instant Messenger.
Users cannot log in to Instant Messaging if the user's password contains a leading or trailing space.
An additional carriage return might be added when cutting and pasting text in Instant Messenger.
On MAC OS, trying to print from the Java Web Start client hangs Instant Messenger.
Workaround: Copy the message and paste it in some other application, then print.
When multiple Instant Messaging policies are applied to a user, the policies can contradict one another.
For example, when the “Regular” and “Conference Room Administrator” policies are attributed to a user, the user is unable to manage conference rooms.
Workaround: Edit the regular user policy by clearing the “Ability to manage conference rooms” checkbox. This will ensure that the two policies do not conflict.
Empty contact groups disappear in Instant Messenger
If you create a new contact group in Instant Messenger but do not assign any contacts to the group, then logout and log back in, the contact group no longer appears in the contact list.
Workaround: Add a contact to the contact group before logging out of Instant Messenger.
Privacy profile not enforced on contacts when added to a group.
In a deployment with a pool of servers, if you move a contact from one contact group to another, the privacy profile for that group does not take effect on the recently moved contact.
Workaround: Sign off and back in to Instant Messenger after making changes.
If you import a contact list that contains entries from multiple domains, only those entries in your domain are imported.
Calendar reminder is blank.
If the Calendar server alarm type is set to text/xml, that is:
caldb.serveralarms.contenttype = "text/xml"
The Reminder field in the Instant Messenger Task Due Reminder alert window is blank.
Workaround: Set this field to "text/calendar" .
Confusing behavior occurs when inviting a user to a conference when that user does not have the correct permissions to join the conference.
It appears as if you invited the user, when in fact, the user never received the invitation.
Access permission changes do not take effect in conference rooms.
If you change access permissions for users already in a conference room, the changes do not take effect until you relaunch the conference room window.
Workaround: Close and relaunch the conference room window to update access permissions.
You cannot enter the same conference room from multiple concurrent Instant Messaging sessions.
Alerts with embedded images are not rendered faithfully.