What is the difference between Cached exchange mode and offline fo

[Guest]

We are migrating from Outlook 2000 to Outlook 2003 with Exchange 5.5 as the
server. In this process I lost the ability to filter junk mail. I read that
I need to run Outlook in Cached Exchange mode to be able to add domains to
have messages filered into a junk folder.

I have a laptop so I need the ability to read my email offline and
synchronize when reattached to the network. Enabling Cached Exchange mode
appears to copy my mailbox locally. If this is the case can I get rid of my
offline storage folders (.ost file)? Also, what is the difference between
these two modes and when should one be used over the other?

We have over 5000 users and I have concerns about having many users enabling
Cached Exchange mode. What affect does using Cached Exchange mode have on
the Exchange 5.5 server?

 

[Lanwench [MVP - Exchange]]

We are migrating from Outlook 2000 to Outlook 2003 with Exchange 5.5
as the server. In this process I lost the ability to filter junk
mail. I read that I need to run Outlook in Cached Exchange mode to
be able to add domains to have messages filered into a junk folder.

I have a laptop so I need the ability to read my email offline and
synchronize when reattached to the network. Enabling Cached Exchange
mode appears to copy my mailbox locally.

Not copied - sync'd.

If this is the case can I
get rid of my offline storage folders (.ost file)? Also, what is the
difference between these two modes and when should one be used over
the other?

Cached mode also uses an OST file, but more gracefully than previous
versions in which you had to manually create it & set it up to sync. With
cached mode enabled, you're always working on the cached copy of your
mailbox & offline address book, and it can smooth out any bumps in the road,
as it were, with server availability/network problems.

We have over 5000 users and I have concerns about having many users
enabling Cached Exchange mode. What affect does using Cached
Exchange mode have on the Exchange 5.5 server?

Shouldn't have any that I know of, but try posting in m.p.exchange.clients
for more help.Note that Exchange 5.5 and NT4 are nearing total end of life
for support - I encourage you to look into upgrading your network to AD and
Exchange 2003.

 

[Guest]

Thank you for the quick reply.

I noticed that the OST file I now have on my system is as large as the size
of my online mailbox. That is why I thought it copied the mailbox. Now that
I understand that Cached Exchange Mode is just a variant on OSTs, I don't
think it will have an affect on the Exchange 5.5 server.

From further reading I believe OL2k3 will provide more functionality when
used with Exchange 2k3. I know we will be migrating our Exchange servers to
a newer version and would assume it to be 2k3. We wanted to migrate to a
full AD environment prior to upgrading Exchange. That is near complete.

Thanks Again!

 

[Guest]

Some issues I have found with Cached Exchange mode in the short time I have
been trying it out.

Cached exchange mode uses a local copy of the OAB. By default the OAB
rebuilds at 5am. Any additions/changes to the OAB won't be seen by cached
mode users until after the next 5am after the additions/changes were made and
after the user downloads the new OAB.

I setup my CEO for cached mode (mainly for the junk mail filtering since we
are still on Exchange 2000). One day he wasn't receiving any new
email...nothing new was showing up in his Inbox. Checking from a different
machine as him with a non-cached profile the mail showed up. Changing his
profile on his machine to non-cached mode and the mail showed up.
This was in his first week of using cached mode so he didn't have great
enthusiasm for cached mode. He was underwhelmed and isn't using cached mode
any more.

 

[Guest]

Good information,

I will be passing this on to the rollout project manager.