Even though we have a low latency uncongested 10Mb/10Mb fibre WAN to Sydney where the Exchange 2010 environment lives, the delays between opening mailboxes, navigating calandars was too painful for them (So laggy Outlook 2010 would go into not responding) We chose to enable the caching for extra mailboxes and sync across the WAN. :) What I described was the workaround, there is just no solution to retain snappy response from Outlook/Exchange if the attached mailboxes aren't cached locally (Online mode compared to Connected mode) We even noticed this issue across WAN's whereby we have a head office and the datacentre Exchange environement are 30Km away from each other with a 1Gbps metro-ethernet connection in between.So it's almost as if even if you are on the same LAN as Exchange, if the mailbox isn't cached, attached mailboxes will be slow.I'm guessing to some extent this issue may be dependant on how Exchange 2010 is configured, load, server performance etc, for us this is large enterprise.
great internet dating openers - Additional mailbox not updating
This will have and look to have the same effect as adding a shared Mailbox to the tree, but it will create an additional OST and cache it locally.
Note that when you give full access to a users mailbox in Exchange/Outlook 2010, Outlook 2010 automatically adds the Mailbox onto the tree to the user you shared the Mailbox too so end users don't have to manually add, so this 'feature' has to be blocked to prevent two identical Mailboxes being presented in the tree (One cached locally, one not) The attribute in AD to prevent this is 'ms Exch Delegate List Link' – Clear all contents of this on the AD Account of who's Mailbox is being shared.
Can anyone tell me the effect of Exchange from a storage group perspective if you have cached several mailboxes into a single OST?
These mailboxes are really slow, how ever i was just curious were we could make it cached locally for just the one mailbox or do we have to change the settings for all shared mailboxes? it is either on or off for shared mailboxes in outlook.
We ended up leaving the users mailbox in cached mode and the shared ones in online mode.
we did this because most of the shared mailboxes had GB's of data and would be useless caching it, let alone caching it in a remote office over the WAN.One thing we did do early on when setting up the storage for the shared boxes was have a completly separate storage group and DB's so the DB's only grew as people filed stuff in the shared ones.We used Group policy to disable the tickbox in Outlook Accounts - Outlook 2010 can also assign multiple mailboxes to a single profile (finally! Just add the mailbox like you would any regular account.I like it better than the Additional Mailbox option, since it caches by default (though you can set per account), lets you pick between to mailboxes to Send As, and sent emails go into the correct Sent Items folder.I know some of this was doable in 2007 with some reg hacks, but works so much cleaner in 2010.We had this same issue inside our business, mostly with PA's who manage lots of mailboxes & calendars.