Entourage does not have the capability to set up Conference Room group views for scheduling.

Entourage does not support synchronization of Tasks with the Exchange Server. Even though Tasks are properly migrated, they will not show up in Entourage because synchronization never takes place.

You can, however, view your migrated Tasks via OWA Premium (OWA Lite does not support opening or editing Tasks). There is currently no method available to export Tasks from Outlook and import them to Entourage.

When attempted to book a conference room, one of the following errors may occur:

• "The operation failed. An object could not be found. Cannot directly book a resource for this meeting."
• "You marked "Bldg-Room" as a resource. You cannot schedule a meeting with "Bldg-Room" because you do not have the appropriate permissions for that account..."

In order to book this conference room, you will need to contact the owner of the conference room. The owner must set conference room permissions to allow resource scheduling. The owner can follow these instructions to setup resource permissions.

To find the owner of the conference room, you can look up the room in the Global Address list (Tools > Address Book in Outlook), and the owner name will show under "Title".

Categories that are set for meetings on an individual's calendar are viewable only by that individual. Any persons who have shared or delegate permissions to view that calendar will still see the meetings, but will not see any categories that the owner may have set for those meetings, or the color coding distinctions. This behavior is seen in Entourage to Entourage sharing, and Entourage to Outlook sharing only.

This problem is due to the Macintosh interface with Exchange. We will begin to see more parity between the platforms, but it will take time.

When an Outlook user shares his/her calendar, the message that goes out to the person with whom the calendar will be shared contains a pointer to instructions applicable only to Outlook. If the person is using Entourage, the instructions are meaningless - the message sent to the recipient is an Exchange-generated email that provides instructions applicable only to Outlook users. The message looks like this:

Subject: Sharing request: Calendar
User, JPL (JPL.User@jpl.nasa.gov) has requested permission to view your Microsoft Exchange Calendar. For instructions on how to grant permissions, see the following article. (Instructions are for Outlook users only.)

This limit can be increased up to 1,080 days or, if the "Always decline if end date is beyond this limit" option is disabled (unchecked), NO limitation will be imposed. These settings must be configured via OWA Premium.

Note: Users should never schedule recurring meetings without an end date.

The following applies only to those who had a large amount of email migrated from the old email server to the new UMS server:

The first time you logon to your new – or reconfigured – email client (Outlook, Entourage, Apple Mail, Thunderbird, etc.), you may experience a long delay while the server messages are being cached (copied) to your local system. (Caching is a feature which allows you to process email even when you are not connected to the JPL network.) Depending upon the client, you may be able to process email (although slowly) while the caching is being done in the background or you may not. Some users believe that they are not receiving new email messages because it takes so long for them to appear in the Inbox. This only happens the first time you logon to your client, but it can take several hours if there is a lot of server data to copy.

Encrypted email stored on the server will be migrated when your account and server data are migrated; locally stored encrypted email cannot be migrated to your new client with the local migration tools provided for you. You can Forward encrypted email from your old email client to your new UMS client.

When your account is migrated to the new UMS server, all of your server data and folders are also migrated to the new UMS server. If you were using the POP protocol, you probably won’t see very much on the new server because most of your data, along with your folders such as your Inbox, your Sent Items folder, your Deleted Items folder, etc. are stored with your local client.

If, however, you were using Eudora with the IMAP protocol, you can expect to see your Inbox, and other folders on the new email server - because they were stored on the old email server -but you will not see your Sent Items folder. This is because Eudora always stores the Sent Items folder locally. Eudora does not give you the option of storing Sent Items on the server – no matter which protocol you are using.

To move your Sent Items folder from Eudora to your new email account, you must use the migration procedures. This is because Eudora stores messages in the Sent Items folder in a different format than any other folder and use of the migration procedures will preserve that formatting. If you attempt to move messages out of the Sent Items folder into any other folder (either locally or on the server), you will have formatting issues.

Microsoft Outlook has a limitation on the maximum size of a distribution list that it can create. The maximum size of the distribution list varies based on the size of the contact information in each list entry. For most people, Outlook created distribution lists should be able to contain between 40 and 60 contacts.

To work around this limitation, there are two alternatives:

1. 1. Create a distribution list using the JPL Directory Groups interface.
2. 2. Split your Outlook created distribution list into multiple parts, each smaller than the maximum size.

Note: Lists created using alternative #1 have essentially no size limitations. If the list contains only JPL addresses, the recommended alternative is the JPL Directory Groups interface.

For more information on distribution lists at JPL, see the JPL Email Mailing Lists.

For more information on the Outlook created distribution list size limitation, see the Microsoft Support page.

To remove the attachment from a message in Entourage 2008:

• Open the message window or the preview pane, then right click (Ctrl+Click) on the attachment and choose Remove.
  Note: After removing the attachment, the received date/time of the message shown in Webmail is changed to date/time that the attachment was removed.

To remove the attachment from a message in Outlook 2007:

• Open the message in your Inbox, then right click the attachment and choose Remove.

Although Eudora accepted lists of addresses separated by commas, the To:, CC:, and/or the BCC: fields must be separated by semi-colons for Outlook and Entourage.

If you use BOSS as a source of mailing lists, or if you click the "email attendees" option in MeetingMaker, please be aware that the commas must be replaced with semi-colons for Outlook and Entourage.

The following is Microsoft's resolution for this issue:

Follow these steps to configure Outlook to recognize the comma as a valid email address separator:

1. 1. On the Tools menu, click Options.
2. 2. Click Email Options, and then click Advanced Email Options.
3. 3. Under When sending a message, click to select the Allow comma as address separator check box.

Note: You can use a semi-colon (;) to separate e-mail addresses when you click to select the Allow comma as address separator check box.

The solution is to set OWA and your Outlook client to send messages as plain text. For step-by-step instructions see How to Prevent Winmail.dat File From Being Sent to Internet Users from Microsoft.

Group address books and nicknames that were imported from Eudora must be recreated, not imported into Entourage.