We have good Bandwidth connectivity from clients to Exchange servers, so
we've always allowed the Outlook clients to decide to run OffLine Cache mode
if they choose. Now management is considering and AD Policy to force all
users into cache mode.

Any issues having all users default into Outlook cache mode?

In ,
Del typed:
We have good Bandwidth connectivity from clients to Exchange servers,
so we've always allowed the Outlook clients to decide to run OffLine
Cache mode if they choose. Now management is considering and AD
Policy to force all users into cache mode.

Any issues having all users default into Outlook cache mode?

You don't mention your version of Exchange, but in general, I would
definitely use it. It is far better overall....from a network bandwidth
perspective, and also junkmail filtering in Outlook.

Just remember that changes you make in AD that affect the GAL (new
users/mailboxes, deletion of old ones, renames/modification) won't appear
instantaneously - the offline address book has to be rebuilt on the server,
and the clients need to download the new offline address book. Make sure
Exchange is fully patched - and patch Office/Outlook to SP2.

All mailbox servers are Ex2003 SP2, The Outlook clients vary but most are
at least up to Outlook XP (2002) level.

We will work with the Outlook team to suggest/patch them to SP2 Level.
Mostly management is desiring the ability to work offline when Exchange
servers are unavailable, ie Nice to have a local copy of the calendar in an
OST if the Exchange server is unavailable.


"Lanwench [MVP - Exchange]"
ahoo.com wrote in message
...
In ,
Del typed:
We have good Bandwidth connectivity from clients to Exchange servers,
so we've always allowed the Outlook clients to decide to run OffLine
Cache mode if they choose. Now management is considering and AD
Policy to force all users into cache mode.

Any issues having all users default into Outlook cache mode?

You don't mention your version of Exchange, but in general, I would
definitely use it. It is far better overall....from a network bandwidth
perspective, and also junkmail filtering in Outlook.

Just remember that changes you make in AD that affect the GAL (new
users/mailboxes, deletion of old ones, renames/modification) won't appear
instantaneously - the offline address book has to be rebuilt on the
server, and the clients need to download the new offline address book.
Make sure Exchange is fully patched - and patch Office/Outlook to SP2.

In ,
Del typed:
All mailbox servers are Ex2003 SP2, The Outlook clients vary but
most are at least up to Outlook XP (2002) level.

We will work with the Outlook team to suggest/patch them to SP2 Level.
Mostly management is desiring the ability to work offline when
Exchange servers are unavailable, ie Nice to have a local copy of
the calendar in an OST if the Exchange server is unavailable.

But of course. It's better even if your server is available. Faster,
generally.





"Lanwench [MVP - Exchange]"
ahoo.com wrote in
message ...
In ,
Del typed:
We have good Bandwidth connectivity from clients to Exchange
servers, so we've always allowed the Outlook clients to decide to
run OffLine Cache mode if they choose. Now management is
considering and AD Policy to force all users into cache mode.

Any issues having all users default into Outlook cache mode?

You don't mention your version of Exchange, but in general, I would
definitely use it. It is far better overall....from a network
bandwidth perspective, and also junkmail filtering in Outlook.

Just remember that changes you make in AD that affect the GAL (new
users/mailboxes, deletion of old ones, renames/modification) won't
appear instantaneously - the offline address book has to be rebuilt
on the server, and the clients need to download the new offline
address book. Make sure Exchange is fully patched - and patch
Office/Outlook to SP2.