Re: SBS 2003 Standard/Exchange Server issue

Well if that's it then;

http://www.petri.co.il/download_office_system_2003_sp2_adm.htm

should help.

Cary W. Shultz wrote:
KJ,

I bet that is the problem....having the .adm file and then 'maiking it
available'. I know that I had a hard time with the many moons ago...

Cary

"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23xvEKXL8HHA.5404@xxxxxxxxxxxxxxxxxxxxxxx
Northwest Upgrades Plus wrote:
I am trying to access the Group Policy, but I am not sure where to
do the following at?????

Where are you getting stuck, where to load the adm template into the
GPMC?

To enforce Unicode mode in Outlook

In Group Policy, load the Outlook 2003 template (Outlk11.adm).
Under User Configuration\Administrative Templates\Microsoft Office
Outlook 2003, click Exchange Settings.
Double-click Exchange Unicode Mode - Ignore Archive Format.
Click the Enabled radio button to enable configuring the policy.
Select the Ignore existing format of the Archive PST check box, and
then click OK.
Double-click Exchange Unicode Mode - Ignore OST Format.
Click the Enabled radio button to enable configuring the policy.
In the Choose whether existing OST format determines mailbox mode
drop-down list, select Create new OST if format doesn't match mode.
Users will be prompted for the file name of the new OST file.

Northwest Upgrades Plus wrote:
This is exactly what I did, but it still shows up as non unicode.
Next step??????

This part too?
================
Outlook next checks the file format for the user's default archive
file (if one exists). You can set a policy that will automatically
create a new Unicode default archive file as well. (Users can still
access ANSI archive files.) Unlike the policy that manages new
Unicode OST files, you cannot provide the option for users to defer
creation of a new default archive file.

Finally, if a user's mail delivery location is a PST file, Outlook
checks the delivery PST file to determine if the file format is
Unicode. However, you cannot require a new Unicode PST file to be
created to replace the existing PST file if Outlook determines that
a user has an ANSI PST file. In this scenario - where Outlook
delivers to ANSI PST files and you want to require Unicode mode for
users - you can instead create and deploy new profiles to users
with the delivery location set to new PST files, which will be
Unicode by default.

Pointing Outlook to use a new delivery PST file automatically -
without users themselves specifying the change - might lead users
to believe that their existing mail has vanished. Older mail is
still in the original PST file but that file is no longer in the
user's profile and is therefore not accessible by default. Users
would need to manually add the older PST file back to their
profile to access the information. Because the PST file being
removed from the user profile can be perceived as data loss by
users -though the data still exists, it is not where users can
readily see and access it - the option to automatically switch to
a new Unicode PST is not provided.


========

Northwest Upgrades Plus wrote:
I have a client that is getting an Outlook 2003 Error about the
.ost file being full. It says to switch to Unicode mode, and
when checking the local system it shows it is not in Unicode
mode. However, it is using Cached mode, which is what the MS
Web Site says to do in order to change to Unicode mode. Any
suggestions?

http://office.microsoft.com/en-us/ork2003/HA011402611033.aspx

For a start on remedying
--
/kj

--
/kj

--
/kj

--
/kj


.

Loading