A tip is that even if you do not enable Outlook Anywhere, as long as the RPC over HTTPS service is installed you can still make an Outlook Anywhere connection. Enabling Outlook Anywhere only really makes it so Autodiscover sees it and starts handing the specified FQDN back. So what you can do here is not enable Outlook Anywhere on 2010 CAS Servers, on the client machine testing against Exchange 2010, disable Autodiscover in the registry, and then manually set the client to point to the 2010 Outlook Anywhere FQDNs withou them being specified.

Situation: I have a very large 2007 infrastructure, published externally via ISA2006. All connections are via Outlook Anywhere, AutoDiscover, OWA and ActiveSync.

I have built a large Exchange 2010 infrastructure alongside the 2007 one, all within the same AD Forest, single Domain (2007contoso.com) and 1 single AD site.

Problem: Autodiscover is published (using redirection) through the ISA and points to a 2007 CAS farm…. there are NO 2010 servers in the CAS farm that ISA points to. AutoDiscover works fine….all our clients are STILL using Exchange 2007 mailboxes.

HOWEVER, I have set the Outlook Anywhere, ActiveSync, OWA and EWS URL's on the 2010 Servers to use a temporary namespace….lets say 2010contoso.com. I have created ISA rules and an external DNS record for 2010contoso.com (So that I can set my test mobile devices, Outlook 2007 client etc to this new namespace). I was quite sure I could not actually test Autodiscover for 2010, because i would have to flick the current autodiscover over to the 2010 one, and I'm not ready for that change.

I did not think however that there would be an issue using the 2010 environment, with this new namespace, for some testing of other connection types.

UNFORTUNATELY, as soon as I enabled Outlook Anywhere on the 2010 servers, my external users started getting this 2010.domain.contoso.com url for Outlook, and could not connect.

I am trying my hardest to find any Microsoft information to explain why Autodiscover is returning external urls's that are set on the 2010 CAS servers?? ISA is ONLY sending Autodiscover and Outlook Anywhere connections to the 2007 CAS servers….. so why would Autodiscover then generate an XML file that contain data from the 2010 environment. I just cant understand it. None of my users are Exchange 2010 mailbox users yet, so surely 2010 CAS server url's should never be returned….

Part of my concern for this also has to do with the fact I wanted to test ActiveSync in a similar fashion. I want to create ISA rules for 2010.domain.contoso.comMicrosoft-Server-ActiveSync that point to the 2010 CAS servers and can then redirect the connection back to the mobile user who should then be sent back through ISA to their 2007 CAS environment…… but I'm now completely faithless that a different Activesync URL on the 2010 CAS servers wont get sent back by Autodiscover TO Exchange ActiveSync devices over version 12.1, which leverage AutoDiscover.

Apologies for the length of this, but any advice would be much appreciated.
Tom

Also let me whether I can use the same setup (Internal Windows CA Different Outlook anywhere Proxy URL-msstd:webmail.internaldomainname.net) and add the autodiscovery.externalurl.com entry in the existing Certificate.

OR

I need to create a new Certificate including the autodiscovery.externalurl.com in the new certificate and assign the services to the new certificate (Internal Windows CA Generated)

Doubt: (totally Confused here)

autodiscovery.externalurl.com i meant here is my owa URL which is the current autodiscovery URL if I run the following command
[PS] C:Windowssystem32>Get-ClientAccessServer | FL Name,AutoDiscoverServiceInternalUri
Name : CASSERVER1
AutoDiscoverServiceInternalUri : https://owa.rh-bridge.com/Autodiscover/Autodiscov…
Name : CASSERVER2
AutoDiscoverServiceInternalUri : https://owa.rh-bridge.com/Autodiscover/Autodiscov…
[PS] C:Windowssystem32>Get-ClientAccessServer | FL Name,AutoDiscoverServiceexternalUri
Name : CASSERVER1
Name : CASSERVER2
[PS] C:Windowssystem32>

What I am missing here?

Manju

We have issue in the autodiscovery or Availability Service or (OutlookanywhereOOF).

URL Details:

Company Name: Company.com

OWA URL : owa.rh-bridge.com

Outlook Anywhere : webmail.internaldomain.net

I Ran test-outlookwebservices -Identity m.gowda@company.com -ClientAccessServer "CASSERVER1" |fl

Id : 1013

Type : Error

Message : When contacting https://OWA.RH-bridge.com/Autodiscover/Autodiscov… received the error The remote server returned an error: (401) Unauthorized.

Id : 1006

Type : Error

Message : The Autodiscover service could not be contacted.

I try to access the URL https://owa.rh-bridge.com/Autodiscover/Autodiscov… and got the below response.

<?xml version="1.0" encoding="utf-8" ?>
-<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006"&gt;
-<Response>
-<Error Time="08:48:25.1001679" Id="2365811618">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>
================================================================================
I Ran Get-WebServicesVirtualDirectory |fl and the external and internal URL part is as below
InternalUrl : https://owa.rh-bridge.com/EWS/Exchange.asmx
ExternalUrl : https://webmail.corporateroot.net/EWS/Exchange.as…
AdminDisplayName :
================================================================================
I Ran Get-OabVirtualDirectory |fl and the External URL field is empty (Is it related?)
Server : CASSERVER1
InternalUrl : http://owa.rh-bridge.com/OAB
InternalAuthenticationMethods : {WindowsIntegrated}
ExternalUrl :
ExternalAuthenticationMethods : {WindowsIntegrated}
=========================================================================
I Ran Get-OutlookAnywhere |fl here i suspect the external host name is it correct here….
ServerName : CASSERVER1
SSLOffloading : True
ExternalHostname : webmail.corporateroot.net
ClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Ntlm}
================================================================================
I Ran Get-OutlookProvider |fl here I added the msstd:webmail.corporateroot.net now but no change…
CertPrincipalName : msstd:webmail.corporateroot.net
Server :
TTL : 1
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : EXPR
DistinguishedName : CN=EXPR,CN=Outlook,CN=AutoDiscover,CN=………,DC=net
Identity : EXPR
==========================================================================
MY Qs…
1. Are the URLs used here are proper ?
2. Meaning the OA URL and the external OWA URL are different. Is it ok?
3. Whyy these errors appear in the above tests…
4. When I RUN https://www.testexchangeconnectivity.com/ the Auto discovery URL is pointing tocompany.com and failing. Is it correct.
But the Company.com URL is really required to get the Auto discovery to work? Where I am failing.
Provide me a solution to the issues I am facing here…..
Manju

Added:

I am not able to ping the OutlookAnywhere URL from internal LAN (webmail.internaldomain.net)

Here ;

1. My certificate is given by internal Windows CA.
2. We use ISA 2006 for the OWA publishing
3. I dont have Autodiscover.externalurl.com in the certificate
4. On outlook anywhere we are not able to get freeusy or OOF information on the OUtlook anywhere

Please throw light on this !!!