Link to home
Start Free TrialLog in
Avatar of pramod1
pramod1Flag for United States of America

asked on

exchange

HOW AUTODISCOVER INTERNALURI WORKS for owa, active sync,

does autodiscover play any role
Avatar of Amit
Amit
Flag of India image

Avatar of pramod1

ASKER

2007
Avatar of pramod1

ASKER

can u just explain in 4 simple words what is the relation of owa, active sync url in terms of autodiscover
Explain this in 4 lines is not possible. I advise you to read this KB:
https://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Avatar of pramod1

ASKER

cant you explain how owa or active sync is concerned with autodiscover?
ASKER CERTIFIED SOLUTION
Avatar of Amit
Amit
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of pramod1

ASKER

I asked following:

one last question : so right now autodiscover is pointing to internal fqdn but when users hit squid proxy server where owa url is mail.domain.com/owa configured when they open owa they are still on mail.domain.com/owa so here u mean autodiscover is not playing any part

 as they don't see e2k7.domain-mail.lan where as when we go through load balancer we hit internal owa url of exchange which is ex2k7.doamin mail.lan where u are telling me toi change it to mail2.domain.com/owa so just to be on same page
 owa users who are using proxy server url mail.domain.com/owa wont have any issues if we change autodicover url

haven't got an answer
Avatar of pramod1

ASKER

so to pull external url mail2.com.com/owa what I need to check in IIS
Avatar of pramod1

ASKER

as per adam I need to change autodicover internal uri and as per u I have to look in iis
Avatar of pramod1

ASKER

1 person mentioned that if redirection is hardcoded in iis it will go there

so then no autodiscover change I have to do?
Avatar of pramod1

ASKER

very confused
Can you bypass proxy squid server or do this. In your machine, you edit the host file and directly point to CAS or Exchange server and test it. Let me know the result.
Avatar of pramod1

ASKER

I did edit the hosts file on my machine it goes to my internal url of owa when I open owa page.
Man, I forgot I wrote that post a while ago lol.

So I read through this, and I am a bit confused. If you want to know your existing AutoDiscover URL it can be found using the following command:

Get-ClientAccessServer | Select Name, AutoDiscoverServiceInternalUri

Open in new window


This will update the Active Directory SCP for the service, but remember that this URI is only used for internal clients. External clients will use the hard coded method that is within Outlook, as they would not be able to hit the Active Directory environment to look up the SCP (Service Connection Point) for the AutoDiscover service.

AutoDiscover really only has to do with (for all extensive purposes) MAPI (Outlook) and ActiveSync (EAS). OWA does not use AutoDiscover at all... I guess my question is what is the issue? Are users trying to use a browser to hit OWA and are getting SSL errors or being redirected to the wrong location? Clients receiving OL SSL errors?