jonmenefee
asked on
exchange 2013 autodiscover
Hey guys
I have three exchange 2013 servers, two onsite and 1 offsite. They are all connected via Database Groups and those are just fine. It seems like everyone in the office connects just fine to the onsite servers and some of the clients that are offsite will connect to one of the two servers onsite, but I have one client that when he connects he only connects to the 1 offsite server. Is there a way to direct this person to connect to one of the two onsite servers in the autodiscover settings or am I at the mercy of the auto connect?
Thanks
I have three exchange 2013 servers, two onsite and 1 offsite. They are all connected via Database Groups and those are just fine. It seems like everyone in the office connects just fine to the onsite servers and some of the clients that are offsite will connect to one of the two servers onsite, but I have one client that when he connects he only connects to the 1 offsite server. Is there a way to direct this person to connect to one of the two onsite servers in the autodiscover settings or am I at the mercy of the auto connect?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Both guys were right but Adam gave a Lot more information and that's what I needed to get this problem resolved. Thanks a lot!!
They way autodiscover works is very simple - it provides an .xml file with configuration to the client.
This XML file, along with all important connection information, contains Exchange external URL (which is specified in Outlook Anywhere configuration).
Usually balancing is performed via Network Load Balancing, where NLB accepts requests from Exchange external URL; or Round Robin DNS, where, for example, externalmail.domain.com resolves into 2 different IP addresses.
This is strange that one 1 client connects to the offsite server.
P.S. I suppose we're talking about CAS connections, not database.