jnikodym
asked on
Outlook 2013 Scheduling Assistant
When i start a meeting request in Outlook 2013 and click the scheduling assistant button, i cannot see the free/busy info for the attendees. It tells me "your server location could not be determined". We also use outlook web access. Through web access i do get the free/busy info.
ASKER
We don't use a proxy server. How should the autodiscover be setup?
Hi again,
If the Outlook client is member of the domaine and authenticated on it, it should use an SCP (Service Control Point) objct in AD to locate CAS Servers.
But in some situation it may happen that the AD interrogation fails.
In that case, Outlook looks for the autodiscover DNS record. Let's suppose the SMTP suffix of your mailbox is @mydomain.com then Outlook ask DNS servers to resolve "autodiscover.mydomain.com
This DNS record should exist and your internal DNS servers should be able to resolve it to an IP and this IP should point on your CAS servers. If you have any Load Balancing in front of your CAS servers the autodiscover record should point on the virtual IP of the LB.
When the name autodiscover.mydomain.com is resolved, Outlook tries to reach the URL https://autodiscover.mydomain.com/autodiscover to obtain an XML file that will give it all the URLs to reach informations it needs (free/busy, OoOff, etc...)
So you should check :
1) the existence of the autodiscover record
2) the DNS servers should be anle to resolve it
3) the IP given by DNS servers must match the IP of the CAS servers or the IP of the Load Balancer
4) on the CAS servers the IIS configuration must contain a autodiscover virtual directory
5) the certificate on the Exchange CAS servers should contain the name "autodiscover.mydomain.com
Have a good day
If the Outlook client is member of the domaine and authenticated on it, it should use an SCP (Service Control Point) objct in AD to locate CAS Servers.
But in some situation it may happen that the AD interrogation fails.
In that case, Outlook looks for the autodiscover DNS record. Let's suppose the SMTP suffix of your mailbox is @mydomain.com then Outlook ask DNS servers to resolve "autodiscover.mydomain.com
This DNS record should exist and your internal DNS servers should be able to resolve it to an IP and this IP should point on your CAS servers. If you have any Load Balancing in front of your CAS servers the autodiscover record should point on the virtual IP of the LB.
When the name autodiscover.mydomain.com is resolved, Outlook tries to reach the URL https://autodiscover.mydomain.com/autodiscover to obtain an XML file that will give it all the URLs to reach informations it needs (free/busy, OoOff, etc...)
So you should check :
1) the existence of the autodiscover record
2) the DNS servers should be anle to resolve it
3) the IP given by DNS servers must match the IP of the CAS servers or the IP of the Load Balancer
4) on the CAS servers the IIS configuration must contain a autodiscover virtual directory
5) the certificate on the Exchange CAS servers should contain the name "autodiscover.mydomain.com
Have a good day
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Microsoft update caused the issue.
update for others...
http://caspan.com/2014/01/outlook-2013-no-freebusy-information-could-be-retrieved-your-server-location-could-not-be-determined/
We contacted Microsoft to find the very easy solution to this problem. Our versions of office were downloaded from Microsoft’s site that came part of Dell computers we buy. Microsoft call this version of office Click-to-Run Office. In this version of Office, for some reason Microsoft has decided to leave it up to the user to decided when to install updates. The user is given no information regarding when updates are available and it is up to the user to manually install these updates. To find these updates I had to open Office, go to File > Office account from there you can chose to install updates.
This fixed our issue because the user had installed some Windows updates that interfered with Office. MS released a patch for Office to fix it. Logically if you don’t install the update you don t get the fix. So we had to spend $249 US to be told to look for updates we have been taught for so many years are just automatic. Felt so dumb it was such a simple solution but to the same extent all previous versions always auto updated with Windows.
http://caspan.com/2014/01/outlook-2013-no-freebusy-information-could-be-retrieved-your-server-location-could-not-be-determined/
We contacted Microsoft to find the very easy solution to this problem. Our versions of office were downloaded from Microsoft’s site that came part of Dell computers we buy. Microsoft call this version of office Click-to-Run Office. In this version of Office, for some reason Microsoft has decided to leave it up to the user to decided when to install updates. The user is given no information regarding when updates are available and it is up to the user to manually install these updates. To find these updates I had to open Office, go to File > Office account from there you can chose to install updates.
This fixed our issue because the user had installed some Windows updates that interfered with Office. MS released a patch for Office to fix it. Logically if you don’t install the update you don t get the fix. So we had to spend $249 US to be told to look for updates we have been taught for so many years are just automatic. Felt so dumb it was such a simple solution but to the same extent all previous versions always auto updated with Windows.
Some articles on the web mention the same symptoms. Did you try any of them yet ?
As an example, some report problems with proxy exception in IE. So the first thing to test is to completly remove the proxy on your IE configuration and just try to see if it changes anything. If yes you'll then have to find which exception you need to add in your IE configuration. Free/Busy informations are now retrieved through a https url that should point to the CAS servers. If this URL is misconfigured on the CAS server your client may be sent to an unreachable server. If you have a IE proxy configure it may be the proxy that can not reach the CAS server.
Also, client use the autodiscover process to locate the CAS servers for Free/Busy and Out-of-Office rules so your autodiscover process may be misconfigured.
Have a good day