Chapter 8 Sun Java System Connector for Microsoft Outlook 7.3 Release Notes

These Release Notes contain important information available at the time of the general release of Sun Java System Connector for Microsoft Outlook 7.3. These Release Notes contain the following sections:

Third-party URLs are referenced in this document and provide additional, related information.

Note Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

About Connector for Microsoft Outlook 7.3

Sun Java System Connector for Microsoft Outlook enables Outlook to be used as a desktop client with Sun Java Communications Suite.

Connector for Microsoft Outlook is an Outlook plug-in that must be installed on the end-user's desktop. Connector for Microsoft Outlook queries the Sun Java System Messaging Server for folder hierarchies and email messages. It converts the information into Messaging API (MAPI) properties that Outlook can display. Similarly, it uses WCAP to query the Sun Java System Calendar Server for events and tasks which are then converted into MAPI properties. With this model, Sun Java System Connector for Microsoft Outlook builds an end-user Outlook view from three separate information sources: mail from Messaging Server, calendar information from Calendar Server, and contacts from the address book server.

When users create and modify items through Outlook, Connector for Microsoft Outlook passes the new message along to the appropriate server depending on its message type. It sends new outgoing email to an SMTP mail server for delivery, and sends modified email messages back to the user's IMAP folder for storage. New calendar events and tasks are converted into a standard format to be stored in the Calendar Server database.

The address book service makes use of WABP and allows a user to have their personal address book accessible from both Outlook and Sun Java System Communications Express.

Note Please note, the package that is Sun Java System Connector for Microsoft Outlook does not include any migration tools. You need those tools if you have users that are currently on Microsoft Exchange and would like to use Outlook with Sun Java Communications Suite. Sun provides a migration service to help move data and users from an existing Exchange deployment to Sun Java Communications Suite.

What's New in This Release of Connector for Microsoft Outlook

See the What's New document.

Deprecated and Removed Features for Connector for Microsoft Outlook 7.3

1. Support for Microsoft Outlook 2000.
2. Support for Microsoft Outlook 2002/XP.

Requirements for Connector for Microsoft Outlook 7.3

See Requirements for Communications Suite 6 and Requirements for Connector for Outlook.

Connector for Microsoft Outlook Installation Notes

Connector for Microsoft Outlook is an Outlook plug-in that requires installation on the end users' desktop. A deployment and configuration program is provided to aid the organization in deploying Connector for Microsoft Outlook.

Note Before you install Sun Java System Connector for Microsoft Outlook, please check the SunSolve website (http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage) for the latest information about any required patches.

The installation and deployment is a three-step process.

Installing Connector for Microsoft Outlook

1. Install the administrator package.
2. Create an installation package for the end user.
3. Deploy the installation package.
   
   The Connector for Microsoft Outlook packages ships an installer for the administrator package. The system administrator should prepare a special installation package called the Setup Wizard for the end user. The Setup Wizard installs and configures the Connector for Microsoft Outlook software on the end user's desktop. This installation package is designed to simplify and automate the installation process.
   For installation, configuration, and deployment instructions please see the following:
   • Sun Java System Connector for Microsoft Outlook 7.2 Installation Guide describes how to install the administrator package. The steps to install Sun Java System Connector for Microsoft Outlook 7.3 is same as installing Sun Java System Connector for Microsoft Outlook 7.2.
   • Sun Java System Connector for Microsoft Outlook 7.3 Administration Guide describes how to create an installation package for the end user using the Deployment configuration Program.
   • Part VI, Deploying Connector for Microsoft Outlook, in Sun Java Communications Suite 6 Deployment Planning Guide describes the deployment of the Connector for Microsoft Outlook.

Converting Data

One of the optional steps that can be performed during setup and configuration of Connector for Microsoft Outlook is the conversion of data that resides on the desktop. This conversion process is invoked only if the administrator checks the Convert existing profile option during the creation of the end user installation package. Please note, this conversion process is not intended to, nor does it replace the need for server-based migration. Sun provides a migration service to help move data and users from an existing Exchange deployment to Sun Java Communications Suite.

LDAP Attributes

In order for Connector for Microsoft Outlook to function correctly, the following LDAP attributes in the Sun Java System Directory Server should be indexed for at least presence and equality to improve the overall performance:

• icsCalendar
• mail
• mailalternateaddress

For more information on these attributes, see the Sun Java System Calendar Server 6.3 Administration Guide and the Sun Java System Messaging Server 6.3 Administration Guide.

Connector for Microsoft Outlook Compatibility Issues

Please refer to the following Technical Notes for information about compatibility issues with Connector for Microsoft Outlook and other products or applications:

• Configuring Calendar Server for Connector for Microsoft Outlook: describes specific configuration tasks and other considerations for Calendar Server to work with Connector for Microsoft Outlook.
• Tuning Communications Express to Work With Connector for Microsoft Outlook: describes interoperability issues and tuning tips when using Communications Express with Connector for Microsoft Outlook.
• Tuning LDAP to Improve Searches in Communications Services Clients: provides tips for improving searches in Communications Express and Connector for Microsoft Outlook.

Problems Fixed in This Release of Connector for Microsoft Outlook

For a complete list of problems fixed in this release, see the README file delivered with the Connector for Microsoft Outlook core software patch.

Known Limitations and Issues in Connector for Microsoft Outlook

This section describes the limitations and known issues that exist in this release of Sun Java System Connector for Microsoft Outlook.

Limitations in Connector for Microsoft Outlook

Some limitations exist in this release of Sun Java System Connector for Microsoft Outlook. The key limitations are:

• Every distinct identity in the Directory Server (for example, users, resources, conference rooms) must have an email address.
• Rich text in the appointment and meeting description field is lost once the same calendar event is modified in the Communications Express client.
• Message recall functionality is not available.
• Description of events is not available when checking availability.
• Free/Busy lookup does not display TENTATIVE or OUT-OF-OFFICE color coding.
• The properties for Sun Java System Connector for Microsoft Outlook cannot be modified using the Tools→Services option from the Outlook menu. To modify the properties:
  1. Exit Outlook.
  2. Right click the Outlook icon and select Properties.
     
     The Properties dialog appears.
  3. Select Folders - < your user name>from the list of services.
  4. Click Properties.
• Free/busy lookup using SSL is not supported.
• Installing Sun Java System Connector for Microsoft Outlook on Exchange servers is not supported.
• Recurring tasks are not supported.
• Offline limitations:
  • During an offline session, if any item in a Calendar, Task, mail, or Contact folder is modified using Outlook, and then another client on the server is used to modify the same item, the changes made offline are lost when the user returns to online mode in Outlook. The changes made by the other client on the server remain.
  • When creating a new event in offline mode, the invitation is saved to the user's Outbox. If, while still in offline mode, the user opens the invitation, the invitation disappears from the Outbox once it is closed.
• Junk Mail Filter does not work for Outlook 2003 and Outlook 2007.
  
  The Junk Email feature available in Outlook 2003 and Outlook 2007 (select Tools→Option) does not function with Connector for Microsoft Outlook. Senders that are set to be filtered using this tool are not filtered.
  
  Because Outlook's Junk Email feature relies on the client to filter unwanted messages, Sun recommends using a server-side solution. In client filters, like the one Outlook utilizes, the messages arrive in the user's Inbox, which is then moved to the Junk folder. This could potentially create unnecessary network traffic and slower response time.
  
  Users may use the Tools→Mail Filter option, which utilizes the server-side filtering function. A more efficient solution would be to use a server-side virus or junk mail filter that is compatible with Sun Java System Messaging Server. Unsolicited email may be rejected at the MTA (message transfer agent) level and never arrive in the user's Inbox, saving resources and disk space. For a list of third-party partners, see http://www.sun.com/software/products/communications/partner&#95;library/index.xml

Known Issues in Connector for Microsoft Outlook

This section describes the known issues at the time of this release of Sun Java System Connector for Microsoft Outlook. If known, IDs are included in parentheses.
The categories of issues discussed in this section are:

• General Issues in Connector for Microsoft Outlook
• Installation and Upgrade Issues in Connector for Microsoft Outlook
• Calendar Issues in Connector for Microsoft Outlook
• Mail Issues in Connector for Microsoft Outlook
• Address Book Issues in Connector for Microsoft Outlook
• Localization Issues for Connector for Microsoft Outlook
• Communications Express Interoperability Issues for Connector for Microsoft Outlook
• Microsoft Exchange Interoperability Issues
• Microsoft Outlook Issues

General Issues in Connector for Microsoft Outlook

6550994 and 6766033

Non Default Contacts Folder Not Getting Deleted in Communications Express and Convergence
Workaround: Delete the contacts folder from the Deleted Items list in addition to deleting it from Outlook.

6689448

Close button on Mail Filters Page Does Not Work in Mozilla Firefox
Workaround: If the Close button on Mail Filters page or on the Out of Office Message page does not work in Mozilla Firefox browser, go to the Program Files\Mozilla Firefox\greprefs folder. Edit the all.js file by setting the value of the dom.allow_scripts_to_close_windows preference to true.

6570441

Vista: Not able to create user profile using silent installation
Workaround: Able to proceed with silent installation after enabling hidden administrator. With Administrator account, this issue is not reproducible. This is Windows Vista specific. This behavior is not seen in other flavors of Windows.

Steps to enable default administrator account in Vista:

1. Run the command compmgmt.msc.
2. Select Local Users and Groups from Left side Tree View.
3. Select Users. This will show all the users present on the machine.
4. Right click on "Administrator".
5. Click properties. Administrator Properties dialog box will be displayed.
6. Clear the option "Account is Disabled".(By default, this option is selected so the administrator account is disabled).

6604704

Outlook 2007: Not able to create profile using installation package
When you run the installation package to create a new profile, you get the following error and the profile is not created.

"Outlook is not installed on this machine. Please install Outlook 2000 with the Office 2000 Service Pack 3 or Outlook 2002 with the Office XP Service Pack 2, and then run this program again."
Issue is because of the missing registry sub-key.
HKEY_CLASSES_ROOT\Outlook.Application

You may experience this issue if you install a Microsoft Office 2003 program after the 2007 Microsoft Office system is installed. For example, you experience this issue in the following scenario:

1. You install the 2007 Office system.
2. You modify the 2007 Office system installation to remove Microsoft Office Word 2007.
3. You install Microsoft Office Word 2003.

Workaround:

1. Exit all 2007 Office programs.
2. Click Start, click Run, enter appwiz.cpl in the Open box, and then click OK.
3. In the Add or Remove Programs dialog box, click Microsoft Office Version 2007, and then click Change.
4. In the Microsoft Office Version 2007 dialog box, click Repair, and then click Continue.

For other details see:
http://support.microsoft.com/kb/930010

Note Outlook 2000 and Outlook XP/2002 are not supported.

Installation and Upgrade Issues in Connector for Microsoft Outlook

4930092

Unauthenticated Shared Drive Path Displays Warning.
For fields requiring a shared drive path, or UNC (Universal Naming Convention) be entered (for example, the shared path to the location for Microsoft Web Publishing Wizard on the Processes Tab of the Deployment Configuration Program), a validation warning is displayed that states the path does not exist if the user is not authenticated for the specified shared drive.
Workaround: The specified shared drive should be accessible by anonymous authentication, allowing anybody to access the shared drive.

No ID

Upgrade defaults to previous servers and ports.
When upgrading from the Connector for Microsoft Outlook 6 2004Q2 version to the Connector for Microsoft Outlook 7.2 version, if the server names and port numbers have changed, the upgrade only takes into consideration the old server names and port numbers.
Workaround: None.

6547273

Error Message Is Displayed On Upgrade of Outlook Connector After Upgrading Microsoft Outlook
When you perform the following procedure:
1. Install Outlook 2003 with Outlook Connector 7.2.
2. Upgrade Outlook 2003 to Outlook 2007.
3. Upgrade to Outlook Connector 7.3.

The following error message appears:

Installation of Sun Java System MAPI Service Providers has failed
Workaround: Uninstall the existing version of Outlook Connector. Reinstall Outlook Connector whenever you upgrade Outlook.

Calendar Issues in Connector for Microsoft Outlook

The following issues relate the calendar portion of Sun Java System Connector for Microsoft Outlook:

6589461

Outlook 2007 Cannot Open the Internet Calendar (.ics) File When a Nondefault Calendar Is Shared Through Email.
When you open an Internet Calendar email attachment in Outlook 2007, for example, Sample.ics, the following error message is displayed:

The file "Sample" is not a valid Internet Calendar file. You cannot create a new folder here.

Workaround: Perform the following steps:

1. Save the Sample.ics file from your email on your desktop.
2. From Outlook Connector File menu, select Import and Export.
3. Select the Import an iCalendar (.ics) or vCalendar file (.vcs) option from the actions list and click Next.
4. Click the Sample.ics file that you have saved on your desktop.
   The Do you want to open this calendar as a new calendar or import its items into your calendar? dialog box appears.
5. Click Import.
   The contents of the Internet Calendar file are imported to the default calendar folder.
   

6680260/6690282

Inconsistency in Passing Ownership Permission to Other Users
Consider the following scenario:

1. Login as user1 in Communications Express.
2. Grant ownership permission of a calendar to user2 by clicking Edit button in the Manage Calendars tab.
3. Login as user2 in Outlook Connector and subscribe to the calendar of user1.
   You will not be allowed to grant ownership permission to user3.

Workaround: Use the Communications Express client and grant permissions to user3.

6595737

When a Resource is Double Booked, Outlook Incorrectly Shows The Second Event as Created
When a resource is booked for two recurring events in the same time slot, and the first instance of the recurring event is deleted, the event is not created in the Calendar Server. However, Outlook 2003 displays the event in the calendar.
The following error message is displayed:
Operation failed. Double Booking is not allowed.
Workaround: None.

5104189

Creating a new calendar profile brings up the old calendar reminders.
When logging in for the first time to a newly created calendar profile in Outlook that is set to your default Calendar Server, Outlook alarms pop up for old events as well as for future events. This applies only for recurring events where the entire series does not take place in the past.
Workaround: None.

6190293

Names of subscribed calendars not visible in Calendar view.
When you first subscribe to a calendar, the calendar name is labeled as "Calendar", not the name of the subscribed calendar.
Workaround:
To see the name of the subscribed calendar, log off Outlook and then log back into Outlook. The subscribed calendar's name should be displayed.

6292026

Opening a shared calendar link does not hook into subscription (Outlook 2003).
In Outlook 2003, clicking the calendar icon at the bottom of the left pane, displays the calendar view. Within that calendar view, clicking "Open a Shared Calendar" displays a dialog that allows the user to enter the user name of a shared calendar. When the user name of a known shared calendar is entered, the error "Unable to display the folder. Your profile is not configured to support this operation for this user." is displayed. This occurs also with contacts and tasks.
Workaround:
To view a shared calendar, select the shared calendar folder in the folders list.

6409671

Unable to remove attachment from an instance of a recurring event.
If a user creates a recurring event that includes an attachment, then attempts to remove the attachment from a single instance of the recurring event, the attachment is not deleted because an attachment usually gets created for a series and not for a single occurrence.
Workaround: None.

6723948

Microsoft TNEF messages are sent when sending calendar attachments.
Sending iTIP and iMIP calendar attachments are not supported.
Workaround: None.

No ID

The following are additional issues related to the calendar portion of Connector for Microsoft Outlook that do not have IDs:

• If delegate accepts or declines an invitation from the organizer's Shared Inbox, the calendar event is added to delegate's calendar, but not to the organizer's calendar.
• All Day events may become a non-All Day events (one event scheduled from 12:00am until 12:00pm) if the desktop time zone is different from the Calendar Server calendar time zone.
• Changing permissions of a calendar requires restarting Outlook for the new permission setting to take effect for the Calendar folder in the Shared Calendar.
• Tasks displayed in Shared Calendars are the login user's tasks, not the subscribed user's tasks. The calendar view always shows the login user's tasks.
• If you create a recurring invitation in Outlook, but delete a single instance of that event, the recipients (attendees) will not see the deleted invitation if Calendar Server has not processed the initial recurring invitation before the deletion.

Mail Issues in Connector for Microsoft Outlook

The following issues relate the mail portion of Sun Java System Connector for Microsoft Outlook only:

2142968 and 6482360

Message recall does not work.
When a sender attempts to recall a message that was sent, the recall attempt fails. The recalled message is not deleted from the receiver's mailbox.
Workaround: None

Address Book Issues in Connector for Microsoft Outlook

The following issues relate to the Address Book portion of the Sun Java System Connector for Microsoft Outlook.

6225049

Deleting a contact from Communications Express does not delete it from Outlook.
The Communications Express configuration parameter delete_perm in the db_config.properties file needs to be set to false in order for Outlook to capture contact entries which have been deleted from Communications Express. The entry should be:
delete_perm=false
The default is true. The entry can be found at /var/opt/SUNWuwc/WEB-INF/config/ldapstore/db_config.properties .
Workaround: Manually fix the entry.

6752539

Cannot Delete a Contact Photo from Outlook Connector
When you right-click the contact photo and select Remove Picture, the photo is not deleted from the contact.
Workaround: None.

6228253

Login to Address Book Server Through Outlook Fails When Address Book is in SSL Mode.
Workaround:
Open Communications Express or Convergence (depending on which address book server you have configured your profile) in Internet Explorer and permanently accept the self-signed certificate.

6267180

Shared contact does not get removed from Address Book after you have unsubscribed.
After you have unsubscribed to a shared contact, it is not removed from the "Show Names from the" list of the Address Book.
Workaround: There are two workarounds:

• If the subscribed contact has been added to the "Show Names from the" list of the Address Book," you should clear the "Show this folder as an email Address Book" option from the "Outlook Address Book" property page before you unsubscribe from the contact.
• Remove the contact directly from the address book properties.
  In Outlook 2003:
  Select Tools > Email accounts.
  Choose "View or Change Existing Directories or Address Books" and select "Outlook Address Book" to change.
  Select the item to remove from your address book.
  In Outlook 2007:
  Select Select Tools > Account Settings.
  Click on Address Books.
  Select "Outlook Address Book" from the list of services set up in your profile.
  The Microsoft Outlook Address Book properties window is displayed.
  Select the item to remove from your address book and click Close.
  Note that user must logout and login again for the change to reflect.

Localization Issues for Connector for Microsoft Outlook

The following issues affect the localized versions of Sun Java System Connector for Microsoft Outlook:

6767897

Cancel Button in the Edit Filter Window Does Not Work in the French Locale
In the French locale, when you click Cancel in the Edit Filter window, the Cancel button does not work.
Workaround: Click the Close button to cancel the Edit operation.

6648138

English Names Are Displayed For IMAP Folders in French Locale
In the French locale, when you create a profile with Communications Express or Microsoft Outlook style folder mappings, folders such as Deleted Items, Sent Items, and Drafts are displayed in English. Only the Inbox folder name is displayed correctly.
Workaround: None.

6777127

Help Button Does Not Work in Korean Locale
In Korean locale, when you click the Help button from Out of Office Message or Mail Filters window, the Help page is not displayed.
Workaround: To view the Help, go to the following location and click the required topic from the contents:

Help --> Sun Java System Connector for Microsoft Outlook Help

6306873

Cannot Enter Non-ASCII Characters In The Full Name Field In The Install Wizard in Korean Locale
In the Korean Install wizard, when you enter non-ASCII characters in the Full Name field, the characters are displayed incorrectly.
Workaround: None.

6767893

Deplacer vers le haut (Move Up) Button in the Mail Filters Page is Not Displayed Correctly in French Locale
Workaround: None.

6672540

Multibyte Shared Calendar Name is Displayed as Question Marks
When you subscribe and query the multibyte shared calendar of another user, the calendar name is displayed as question marks.
Workaround: None.

6313321

Cannot convert IMAP profile name in Japanese.
If an IMAP profile already exists, and this profile has never been used by Outlook, the conversion fails.
Workaround: None.

6541324

After Deploying Outlook Connector in Traditional Chinese, Folder Names in Outlook 2007 Do Not Display Correctly
When you install Outlook Connector on a machine running Windows 2003 with Outlook 2007, the folder names are garbled.
Workaround: None.

6742345

Message Received in Simplified Chinese With HZ Encoding Is Garbled
When you send a message in Simplified Chinese with HZ encoding, the message is garbled on receipt.
Workaround: Choose from the following outgoing message encoding options:

• Plain Text format – GB2312 or GB18030 combination
• HTML or RTF format – any combination
  

Communications Express Interoperability Issues for Connector for Microsoft Outlook

The following issues relate to the interoperability between Sun Java System Connector for Microsoft Outlook and Sun Java System Communications Express:

6752413

Contact Folder Named "Calendar" Created in Communications Express Replaces the Default Calendar in Outlook Connector
When you create a contact folder named "Calendar" (case-sensitive) in Communications Express, it replaces the default calendar folder in Outlook Connector. Thus, all data in the calendar folder is lost.
Workaround: None.

4949659

Address Change in From: header
The name in the From: header changes if an attendee replies to an event invitation and attaches the winmail.dat calendar invitation. For example, Joe (using Outlook) sends an invitation to an event to Bob. Bob replies to Joe, using an email client that automatically sends the original winmail.dat calendar attachment back to Joe. When Joe opens the reply, the From: header is changed to Joe.
Workaround: None.

4969029

Email ID is a must for Outlook.
If a person with a calendar ID but no email ID is invited to an event in Communications Express, this person is not displayed as an attendee in Outlook. An email ID is required for Outlook.
Workaround: None.

5032872

When you unsubscribe, the calendar does not get removed from the folder list.
If you subscribe to or unsubscribe from a calendar in Communications Express, the information is updated in Outlook only after Outlook has been restarted. Additionally, if the LDAP configured for lookup is a replica, the subscription list is not updated until the replica is updated.
Workaround: None.

6175103

Error generated when Outlook synchronizes with server.
If a task is created (either in Outlook or Communications Express) while Outlook is synced with the server, then the task is deleted and the user attempts to switch to the Tasks folder in Outlook, an "Unable to display all cells due to low memory" error is generated.
Workaround: Switch to another folder and then back again to the Tasks folder.

6229276

Configuration parameter needs to be set in order for address book server contacts to be properly synchronized.
Workaround: The Communications Express configuration parameter delete_perm in the db_config.properties file needs to be set to false in order for Outlook to capture contact entries which have been deleted from Communications Express. The entry should be:
delete_perm=false
The default is true. The entry can be found at /var/opt/SUNWuwc/WEB-INF/config/ldapstore/db_config.properties .

6351914

Limitations in calendar alarms.
Because of the difference in how Outlook and Communications Express handle alarms and reminders, changes in one interface are not reflected in the other. Outlook utilizes pop-up windows as alarms, while Communications Express (Calendar Server) sends email reminders. In order to not replicate alarms when both interfaces are used (having both a pop-up and email reminder sent), Connector for Microsoft Outlook allows alarm synchronization upon creation of events in a single direction only. For example, when a new event is created using Communications Express, the alarm is copied to the Outlook event (as a pop-up). But when creating an Outlook event, the alarm is not set on the server.
Workaround: To allow the synchronization to work from Outlook to Communications Express, a registry value can be set in outlook: HKEY_CURRENT_USER\Software\Sun Microsystems\Outlook Connector\Sync Cal To turn this on, set the value to 1, and to turn it off, set the value to 0 (or remove the key. Note that setting the registry value will only have effect when creating new events. Modifying existing events only affects the alarm type associated with the client performing the modification.

No ID

The following are additional issues related to Communications Express interoperability that do not have IDs:

• RTF formatting in Outlook is not preserved if the description text is edited using Communications Express.
• Differences exist in privacy classes between Outlook and Communications Express.
  Outlook has two privacy classes (Private and Public), while Communications Express has three classes (private, Date and Time only, and Public). In Outlook, a private event is created as a "Date and Time only" event in Communications Express. A public event in Outlook maps to the public event in Communications Express. Similarly, a Communications Express "Date and Time Only" event maps as a private event in Outlook, and a public event maps as a public event in Outlook. A Communications Express private event also maps to Outlook as a private event. To create a private event in Outlook so it appears as a private event in Communications Express, select "Free" from the "Show time as:" field. The Communications Express private event cannot be seen in a shared Calendar folder by another user.
• There are differences in the way free/busy is implemented in Outlook and Communications Express.
  The default private event is free in Communications Express. If the event is to be included for free/busy lookup, then it should manually be set to busy. In Outlook the default events are busy for both private and public events.
• If you export an event from Communications Express to a file in Outlook format, you cannot import the event from the same file into Outlook.
• Incompatibilities exist in how recurring tasks are implemented in Outlook and Communications Express.
  Recurring tasks in Outlook do not conform to RFC 2445 while Communications Express is specifically designed to work with RFC 2445-compliant information. This causes problems when recurring task information is passed between Outlook and Calendar Server.
  Information stored locally by Outlook does not always match information which is stored on the Calendar Server. Sun Java System Connector for Microsoft Outlook, for example, does not transfer any information dealing with the recurrence of a task to the Calendar Server. Any tasks created in Outlook (recurring or non-recurring) appears in Communications Express as single tasks. A task that is created in Communications Express only uses the recurring information from the Calendar Server when that task is written for the first time in the Outlook client and not during any modification of any existing task on Outlook.
  For these reasons, recurring tasks viewed in Outlook and tasks viewed in Communications Express appear different in many cases. We recommend that users who work with recurring tasks choose either Outlook or Communications Express and not attempt to work with recurring tasks in both clients interchangeably.
• If a message is sent from Outlook in Rich Text format, the message contains a plain text body with no formatting and a WINMAIL.DAT attachment.
  The WINMAIL.DAT attachment contains the Rich Text message along with any other attachments that may have been added. Because the format is Microsoft proprietary, only Outlook can read the WINMAIL.DAT attachment. Communications Express (and any other client) sees only the unformatted text message and a WINMAIL.DAT attachment. It is recommended that HTML format be used instead of Rich Text format to send messages.
• If contacts groups in Outlook contain external SMTP mail recipients or other contacts groups, they are not seen by Communications Express.
  Communications Express and Convergence cannot send mail to these recipients.
• Communications Express and Convergence cannot decode and display Microsoft TNEF format.
  Outlook saves calendar events and tasks (any calendar folder not under the Calendar folder tree), contacts (any contacts folder not under the Contacts folder tree), notes, and journals in the Messaging Server. Because the data is saved as Microsoft TNEF format, Communications Express and Convergence cannot decode and correctly display them.

Microsoft Exchange Interoperability Issues

The following issues relate to the interoperability between Sun Java System Connector for Microsoft Outlook and Microsoft Exchange:

6174201

Free Busy Proxy for Exchange does not return complete Free/Busy information.
Workaround: None.

6255190

Cannot recover deleted items.
After selecting "Empty Deleted Items Folder," Connector for Microsoft Outlook does not allow for recovery of deleted items.
Workaround: None.

No ID

Receipt of a message with embedded OLE objects and HTML in RTF from Exchange (versions 5.5, 2000, and 2003) to Connector for Microsoft Outlook does not work.
Workaround: None.

Microsoft Outlook Issues

The following are issues with Microsoft Outlook:

Note These issues are general issues with Microsoft Outlook, and are not specific issues with Connector for Microsoft Outlook.

6365369

Limitations for non-default calendars.
Limitations exist when attempting to perform operations on a non-default calendar with Outlook:

• Free/Busy information is not displayed.
• Reminders cannot be set on an event.
• Attendee responses to invitations from non-default calendars are not tallied.
  Workaround: None.

Redistributable Files for Connector for Microsoft Outlook

Connector for Microsoft Outlook does not use any redistributable files.