Exchange Server

This is very good · Guest

Hi,

I have a problem, I upgraded my exchange server 2000 to exchange 2003.before
That I migrated all mailboxes to .Pst files with Exmerge utility.After I
installed exchange 2003, I wanted to import that into outlook 2003, But I get
an error message:
You are about to add a non Unicode capable store to yourprofile. This store
should not be used to storeMultilingual Unicode data. Do you want to continue?
What's going on here? I have never seen this upgrading from Outlook 97 to
2002. Are the files corrupted?Please help, thanks

Antoine Golio · Guest

Unicode Options for Outlook 2003

Microsoft Office Outlook® 2003 can now provide full Unicode® support.
Using Outlook in Unicode mode is especially advantageous for organizations
with multilingual needs and - because Outlook Unicode-formatted files have
higher storage capacities than non-Unicode files - for users who need very
large Outlook files.

Taking advantage of Unicode support in Outlook depends on users'
Microsoft Exchange Server version and other criteria that are checked when
users run Outlook. If the criteria for using Unicode are met and users are
running in Unicode mode, Unicode is used throughout Outlook when used with
Exchange Server (for e-mail messages, the Address Book, and so forth).

To determine whether to use Unicode mode or non-Unicode (ANSI) mode,
Outlook evaluates a set of requirements and options. One requirement for
Unicode mode is that users must have Exchange 2000 or later accounts.
Outlook also checks the formats - Unicode or ANSI - of users' Offline Store
(OST) files and the default archive files. Finally, Outlook checks the
format of users' PST files that are used as a delivery location (if any).

Encoding Options in Outlook 2003

Microsoft® Office Outlook® 2003 can automatically select an optimal
encoding for outgoing e-mail messages. This feature increases the likelihood
that when you send a message with Outlook, users receiving the message will
see all the characters rendered properly, even if the users run older e-mail
programs. Automatic messaging encoding results in less configuration work
for administrators and a better experience for users.

Outlook scans the entire text of the outgoing message to determine a
minimal popular encoding for the message. Outlook selects an encoding that
is capable representing all of the characters and that is optimized so that
the majority of the receiving e-mail programs can interpret and render the
content properly.

This table shows a few examples of how this works.

If the message contains these characters:
Outlook selects this encoding:

English (ASCII) text (A-Z, a-z)
US-ASCII

German (Latin 1) text (A-Z, a-z and Umlauts)
Western European (ISO)

Greek text (A-Z, a-z and Greek characters)
Greek (ISO)

Japanese text (A-Z, a-z, Hiragana, Katakana, Kanji)
Japanese (JIS)

Multilingual text (different scripts)
Unicode® (UTF-8)

This works for users sending Internet mail through the POP/SMTP or
IMAP transport, or for messages sent through Microsoft Exchange Server 5.5
SP 1 or later.

--------------------------------------------------------------------------

Note To use the automatic message encoding feature, users sending
the message must have Microsoft Internet Explorer 5.5 or later installed.

"This is very good" <Thisisverygood@discussions.microsoft.com> a écrit dans
le message de news: F4D8E941-F31D-42E2-8F1D-7BC5B969AF09@microsoft.com...

	Exchange Server Forum Index -> Exchange General	All times are GMT
Page 1 of 1