If your users want that instantaneous response of online mode, then push them to OWA instead. I don't see any autodiscover errors etc but I'm not real sure where to go with this as I am not the expert by any means.Ĭached Mode is the default and is considered the best-practice. Then they book things over top of the time that should be occupied and it's a mess.Īlso finding that sometimes emails just sit in people's outboxes (rare) and decide not to send.
#Outlook for mac 2016 share caching update
if 1 admin person updates a meeting room resource cal and sends that update out to 4 people, 1 person's calendar might be updated correctly within an hour or so but the others may be out of date for a while. Maybe related, but we often finding that calendars aren't updating in a timely fashion either. But I feel like staff should be able to work in Online mode if they want to? I don't know.
If put in Cached mode with a limit of say 12 months, it's much better. Even if it's a fresh mailbox, Outlook tends to freeze for a bit when working within it if or composing email, etc. There are no quotas here and it's kind of nuts. There is no load balancing in place that I'm aware of.Ģ VM's are on 1 host, 2 VM's are on another.Įach VM has been given 24GB of memory and are working on Server 2016 Standard.Įach server is hosting an active database and 3 passive databases. What information is needed to best start troubleshooting this?Įx 2016, 4 servers in a DAG. I'm not even sure where to start with this? I'm not an Exchange guy but somehow have found myself cast into the role as the Exchange guy.
0 kommentar(er)
