Solved

Changing Autodiscover HTTP redirect URL

Posted on 2011-03-25
17
3,873 Views
Last Modified: 2012-06-27
When i originaly installed CAS 2010 in my exchange 2003 organization i used hostname"cas.domain.com/.." for external URLs.  We then decided to change hostname to mail.domain.com.  So i set the external url on all virtual directories including the 'autodiscover' to the new hostname using EMS.  When i run remote connectiveity analyzer, i see that in the step where it tests the HTTP redirect it still goes to the old url.  I checked all virtual directories,  i used -Getxxx : fl *  to view each directory and all of them showed the new external url "mail.domain.com".  I also check them in IIS.  They are all using the new host name.  Also, users (still on exchange 2003) get the the popup to allow redirect to to 'cas.domain.com/..." which is the old host name.   I have the redirect url set to use the new name.  The SAN certificate has the new name.  AD objects attributes show the new name.  But something is still referening the old the name.  Here is the error in ExRCA.
---------------------------------------------------------------------------------
ExRCA is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service.
  The redirect (HTTP 301/302) response was received successfully.
   Additional Details
  Redirect URL: https://cas.domain.com/Autodiscover/Autodiscover.xml
 
 Attempting to test potential Autodiscover URL https://cas.domain.com/Autodiscover/Autodiscover.xml
  Testing of this potential Autodiscover URL failed.
-----------------------------------------------------------------------

What is it that i'm missing here?  Why is it still redirecting to the old URL?  I also have to mention that i actualy removed and recreated all virtual directories (OWA, EWA,..) and it sitll tries to redirect to old url.   Any help on this will be greatly appreciated.
0
Comment
Question by:Zeetan
17 Comments
 
LVL 8

Expert Comment

by:praveenkumare_sp
Comment Utility
does the exchange 2010 users work fine ?

exchange 2003 does not have autodiscover to work

what is the primary smtp address of the users in exchange 2003 ?

what email address they used to create the outlook account ?


answering these questions will help not only me even u to understand where the issue is
0
 

Author Comment

by:Zeetan
Comment Utility
There are no exchange 2010 users.  Everyone is still on 2003.   The issue is that the old external url (cas.domain.com) is still being used.   I know that because i see it in ExRCA results and more importantly when the users get the popup to allow redirect to the old url.   I need to know where could that URL be refereced?   given the the fact that i have viewed alll setting as explained in my previous port and they all showed the new URL.
0
 
LVL 49

Expert Comment

by:Akhater
Comment Utility
Get-clientaccessserver | fl name,*uri*

It shld return CAS.domain.com in your case,

Change it by running set-clientaccessserver
0
 

Author Comment

by:Zeetan
Comment Utility
Hi Akhater,   when i run "Get-clientaccessserver | fl name,*uri* it only shows the locat internal hostname of the server which is (servername).    I think the main issue for me is that the autodiscover service redirect URL when it tries to use HTTP is referecing the old external URL (cas.domain.com). See below..

---------------------------------------------------------------------------------
ExRCA is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service.
  The redirect (HTTP 301/302) response was received successfully.
   Additional Details
  Redirect URL: https://cas.domain.com/Autodiscover/Autodiscover.xml
 
 Attempting to test potential Autodiscover URL https://cas.domain.com/Autodiscover/Autodiscover.xml
  Testing of this potential Autodiscover URL failed.
-----------------------------------------------------------------------

How do i change the redirect to use the new URL  mail.domain.com?




 

0
 
LVL 49

Expert Comment

by:Akhater
Comment Utility
ok let me ask you another question, do you have an srv records in your EXTERNAL dns zone _autodiscover pointing to cas.domain.com ?

if you don't know drop me your domain i will do the test for you (way to contact me in my profile)
0
 

Author Comment

by:Zeetan
Comment Utility
No i don't have any srv records in my external zone pointing to cas.domain.com.  Both autodiscover.domain.com and mail.domain.com point to the public ip of the cas server.  
0
 
LVL 49

Expert Comment

by:Akhater
Comment Utility
It cant be exrca works like that

A. Check for domain.com/autodiscover it it fails
B. Check for autodiscover.domain.com if it fails
C. Chech for srv records

So,if you have an autodiscover A record it will use it!

Create for me a test user/ pass so i can help out
0
 

Author Comment

by:Zeetan
Comment Utility
Thanks Akhater...I'd love to give you test user to help me resolve this but it may get me in trouble:)..im sure you understand.   Ok so below is a paste of the ExRCA test details for the part that is failing.  Thisi is the test where it attempts to contact the autodiscover service using the HTTP redirect method.  The problem is that the Redirect URL it uses is the old external name (cas.domain.com).  It will then of course tries to resolve the old name and checks for srv record but it can't find it because it no longer exists.  All other test are succesful and show the new external name which is (mail.domain.com).   Below is the failing test and  I have bolded the part in question.    

-----------------------------------------------------------------------------------------------------------------
Attempting to contact the Autodiscover service using the HTTP redirect method.
  The attempt to contact Autodiscover using the HTTP Redirect method failed.
   Test Steps
   Attempting to resolve the host name autodiscover.domain.com in DNS.
  The host name resolved successfully.
 
 
 Testing TCP port 80 on host autodiscover.domain.com to ensure it's listening and open.
  The port was opened successfully.
ExRCA is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service.
  The redirect (HTTP 301/302) response was received successfully.
   Additional Details
  Redirect URL:https://cas.domain.com/Autodiscover/Autodiscover.xml
Attempting to test potential Autodiscover URL https://cas.domain.com/Autodiscover/Autodiscover.xml
  Testing of this potential Autodiscover URL failed.
------------------------------------------------------------------------------------------------------------------
0
Are end users causing IT problems again?

You’ve taken the time to design and update all your end user’s email signatures, only to find out they’re messing up the HTML, changing the font and ruining the imagery. What can you do to prevent this? Find out how you can save your signatures from end users today.

 
LVL 49

Expert Comment

by:Akhater
Comment Utility
OH well that's it then :)

open your IIS find your autodiscover virutal direcotry you have a redirection option on your right hand side check it ;)
0
 

Author Comment

by:Zeetan
Comment Utility
This was the first thing i checked when i first had this issue.  The redirection on the autodiscover virutal directory show the correct address: mail.domain.com.  Strange!! I know.   Where else could that setting be stored?
0
 
LVL 49

Expert Comment

by:Akhater
Comment Utility
any ISA/TMG servers ?
0
 

Author Comment

by:Zeetan
Comment Utility
Nope, no ISA.  The CAS is behind a load balancer which configured to send requests to "mail.domain.com" and "autodiscover.domain.com (443, 80, etc..) to the CAS server.  I checked with the network folks previously and they said that they don't have anything configured for cas.domain.com
0
 
LVL 49

Expert Comment

by:Akhater
Comment Utility
there is one last thing that it could be

open iis go to your autodiscover virtual directory and click Explore

any file there like default.html .asp something ?

can u share a screenshot of this directory
0
 

Author Comment

by:Zeetan
Comment Utility
I explored the autodiscover virtual directory and didn't see anything.  I even opend each files and searched for the old name and didn't get any resutls.   Here is a screenshot
autodiscover.bmp
0
 

Expert Comment

by:mbrooks27
Comment Utility
http://support.microsoft.com/kb/940726 should help and resolve the issue.
0
 

Accepted Solution

by:
Zeetan earned 0 total points
Comment Utility
Only reinstalling the CAS got rid of the old name.  
0
 

Author Closing Comment

by:Zeetan
Comment Utility
Only reinstalling the CAS got rid of the old name but im sure there is a better way to do it.
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now