Using cached exchange mode vs not using cached exchange mode

We are using Outlook 2003 and Exchange 2000 server. Getting prompts about
using cached exchange mode. What is the default setting for this? Use or do
not use? What the benefits/drawbacks of using cached exchange mode. We are
in a 2003 domain environment.

Default is on for mailbox and off for public folder favorites.

I recommend use because it does isolate the customer from intermittent
connectivity issues from the Exchange & GC servers. Since the user is
primary working out of the offline address book and OST, it means less round
trips to the server when looking at the same message lots of times. Less
round tripping to the server means that one should be able to have a higher
user per server count.

The biggest drawback I hear about at work is that it can take up to 24 hours
before the end user sees a change to the global address list. This is
because the default behavior of Outlook 2003 is to update the OAB once a
day.

Oh and before I forget, cached mode is required in order for the junk email
feature to work in Outlook. When its off, its whatever it is at the server.

"Jim in Cleveland" wrote in
message ...
We are using Outlook 2003 and Exchange 2000 server. Getting prompts about
using cached exchange mode. What is the default setting for this? Use or
do
not use? What the benefits/drawbacks of using cached exchange mode. We
are
in a 2003 domain environment.

I have to disagree with you.
True using cahced mode does prevent the increased round trips to the
server but speaking directly from experience and working in both arenas
I have found that using Exchange under normal mode doesn't produce that
much more traffic. Also if every DC in the Org is also a GC and running
DNS then you really will have limited issues with updates to the GAL
and server traffic. If you are running a clustered or even an non
clustered environment as long as the DC's are also GC's and DNS servers
You should be fine.Also remember that Microsoft does NOT support
Exchange nor outlook if you are running in Cached mode.
neo [mvp outlook] wrote:
Default is on for mailbox and off for public folder favorites.

I recommend use because it does isolate the customer from intermittent
connectivity issues from the Exchange & GC servers. Since the user is
primary working out of the offline address book and OST, it means less round
trips to the server when looking at the same message lots of times. Less
round tripping to the server means that one should be able to have a higher
user per server count.

The biggest drawback I hear about at work is that it can take up to 24 hours
before the end user sees a change to the global address list. This is
because the default behavior of Outlook 2003 is to update the OAB once a
day.

Oh and before I forget, cached mode is required in order for the junk email
feature to work in Outlook. When its off, its whatever it is at the server.

"Jim in Cleveland" wrote in
message ...
We are using Outlook 2003 and Exchange 2000 server. Getting prompts about
using cached exchange mode. What is the default setting for this? Use or
do
not use? What the benefits/drawbacks of using cached exchange mode. We
are
in a 2003 domain environment.

"Also remember that Microsoft does NOT support Exchange nor outlook if you are running in Cached mode."

Care to cite where Microsoft will not support this configuration? A Technet or MSDN article citation will do. Even a white paper...


--�
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Deme asked:

| I have to disagree with you.
| True using cahced mode does prevent the increased round trips to the
| server but speaking directly from experience and working in both
| arenas I have found that using Exchange under normal mode doesn't
| produce that much more traffic. Also if every DC in the Org is also a
| GC and running DNS then you really will have limited issues with
| updates to the GAL and server traffic. If you are running a clustered
| or even an non clustered environment as long as the DC's are also
| GC's and DNS servers You should be fine.Also remember that Microsoft
| does NOT support Exchange nor outlook if you are running in Cached
| mode.
| neo [mvp outlook] wrote:
|| Default is on for mailbox and off for public folder favorites.
||
|| I recommend use because it does isolate the customer from
|| intermittent connectivity issues from the Exchange & GC servers.
|| Since the user is primary working out of the offline address book
|| and OST, it means less round trips to the server when looking at the
|| same message lots of times. Less round tripping to the server means
|| that one should be able to have a higher user per server count.
||
|| The biggest drawback I hear about at work is that it can take up to
|| 24 hours before the end user sees a change to the global address
|| list. This is because the default behavior of Outlook 2003 is to
|| update the OAB once a day.
||
|| Oh and before I forget, cached mode is required in order for the
|| junk email feature to work in Outlook. When its off, its whatever
|| it is at the server.
||
|| "Jim in Cleveland" wrote
|| in message ...
||| We are using Outlook 2003 and Exchange 2000 server. Getting
||| prompts about using cached exchange mode. What is the default
||| setting for this? Use or do
||| not use? What the benefits/drawbacks of using cached exchange
||| mode. We are
||| in a 2003 domain environment.