I've sometimes seen this pop up on one of our contracts when the proxy exclusions sometimes get mixed up.
Manually adding the casarray to the exclusions sorts it on the machine. Then we get the service desk to bounce the incident to the team that look after the policies. T On 23 Mar 2015 19:32, "Robert Peterson" <[email protected]> wrote: > Wondering if this is a result of a missing configuration or not… > > > > Had a user getting the “server not available” error when she would attempt > to turn off a previously set OOF. > > Tried rebuilding profile, and removed from “cached” mode, which I feel has > worked in the past. > > Neither of these made a difference. > > > > We have a Exchange 2010 Fail-Over cluster, and I noticed the database > holding her mailbox, was mounted on its non-preferred server, must have > moved at some point. > > > > When I moved the database back to its original server, immediately we > could access her OOF setting via Outlook 2010 and turn off her replies. > > > > Is this normal or something misconfigured somewhere? > > > > Thanks, > > Robert > > >
