HI All

i am on site with a client doing a windows 8.1 roll out they have office 2010 clients.

they have recently upgraded to exchange 2013,

I am trying to configure the outlook client (2010) to autodiscover the profiles on first launch so the wizard does not appear

have done this many times before however for somereason this site the client cannot auto discover the exchange autodiscover address

I was wondering if anyone knows what settings I need to set to have this correctly configured

cheers

C

How are you trying to provision the profile?  Using Group Policy or a prf file? 

Run Get-ClientAccessServer | FL identity, auto*

Hi,

could you plz send the result of the below command on Exchange Management Sell EMS

get-clientaccessserver | fl identity, *uri*

try to access the autodiscover URL by

HTTPS://ServerName2013/autodiscover/autodiscover.xml

and feed me back

Hi chirs,

Thank you for your question.

Are there any error when we click outlook?

Frist of all. We make sure the 8.1 client could ping Exchange server without any problems(include DNS resolve), and client has been joined domain.

Then check if we could logon OWA and type the url which Attias provide. Delete the profile and create a profile to check if the issue persist.

Check if there are any issues on other 8.1 clients with outlook 2010.

Then run Get-OutlookAnywhere server  <servername> and post the result to ibsexc@microsoft.com for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

HI Guys

thank you for your responses we actually found that the load-balancer is not able to resolve the users SAN against their email address for some reason so they are working on that to fix 

thank you for your quick responses 

Chris

• Proposed as answer by Abdelrahman M-Attia 21 hours 54 minutes ago

HI Guys

thank you for your responses we actually found that the load-balancer is not able to resolve the users SAN against their email address for some reason so they are working on that to fix 

thank you for your quick responses 

Chris

HI Guys

thank you for your responses we actually found that the load-balancer is not able to resolve the users SAN against their email address for some reason so they are working on that to fix 

thank you for your quick responses 

Chris

How would the load balancer know that information? 

Do the Primary Email Addresses match the users UPNs in AD?. They really should. Things work much better that way - especially autodiscover

I have seen the default iApp template with F5's want to do some NTLM look up for some reason.  I forget why they do it, but if you don't give it an AD Server to Authenticate against it throws you in a credential loop.

HI Guys

thank you for your responses we actually found that the load-balancer is not able to resolve the users SAN against their email address for some reason so they are working on that to fix 

thank you for your quick responses 

Chris

• Proposed as answer by Abdelrahman M-Attia Friday, May 22, 2015 9:33 AM

I have seen the default iApp template with F5's want to do some NTLM look up for some reason.  I forget why they do it, but if you don't give it an AD Server to Authenticate against it throws you in a credential