Hi all. 

I'm a bit lost, it's my first exchange 2013 install and my first coexistence scenario. So I need help. 

I've got an existing Exchange 2007 SP3 CU 12 organization, with 3 servers : 

- Server38 and Server39 as Mailbox Server, CCR Cluster, virtual node is Server40

- Server41 as CAS Server. 

I want to migrate everything to Exchagne 2013 SP1 on Windows 2012 R2. I have 2 servers : 

- Server12 and Server13 are Multirole servers, CAS ans MBX. I have configured a DAG. It's working. 

To provide HA on CAS service, I put this in order : http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/

Clearly, I want my CAS Server to be accessed with mail.domain.com instead of Server12.domain.com or Server13.domain.com

So I configure Outlook Anywhere like this : "Set-OutlookAnywhere -InternalHostname mail.domain.com -InternalClientsRequireSsl $false"

Now, I don't really imagine how I can use this platform during coexistence. 

I want to set users on my new servers, but autodiscover is configured in DNS to point Server41. 

Users can access to their mails via OWA and Outlook. 

How can I configure autodiscover? Must I change autodiscover record in DNS to point to new servers or should I let it on Server41? 
How will Outlook work when I migrate one user to the new servers? Will I have to change config? 

Thanks

• Edited by Iom84 Wednesday, April 02, 2014 9:12 AM

Hi 

As mentioned you need to point the Autodiscover record and point it to the Exchange 2013 CAS server in both internal and public DNS to redirect the connections to the Exchange 2013 CAS

You need to change all the internal and external url's to point to Exchange 2013 CAS server by running the below commands

Set-ClientAccessServer -Identity 2013 CAS -AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
Set-WebServicesVirtualDirectory -Identity  2013 CAS\EWS (Default Web Site) InternalUrl https://mail.mydomain.com/EWS/Exchange.asmx
Set-OABVirtualDirectory -Identity e2013ht\OAB (Default Web Site) -InternalURL https://mail.mydomain.com/OAB
Set-ActiveSyncVirtualDirectory -Identity 2013 CAS\Microsoft-Server-ActiveSync (Default Web Site) -InternalURL https://mail.mydomain.com/Microsoft-Server-Activesync

For Outlook Anywhere, 

Set-WebServicesVirtualDirectory Identity 2013 CAS\EWS (Default Web Site) ExternalUrl https://mail.mydomain.com/ews/exchange.asm

Thanks for your very fast reply :). 

I did the redirection of all my Exch2013 virtual directories to mail.domain.org, which points to my 2 multiroles Servers. 

I created a DNS entry mail.domain.org in my domain. 

I created a legacy.domain.org to point to my old CAS server (Exch 2007)

Autodiscover internal DnS entry points to mail.domain.org. 

But I can't connect a user migrated on Exchange 2013 in Outlook. Autoconfig is unable to connect to server. 
Any idea? 

• Edited by Iom84 Friday, April 04, 2014 3:09 PM

Comments edited

No one? :(

Hi,

Do you mean the mailbox which is moved from Exchange 2007 to Exchange 2013 cannot connect to the new server in Outlook? How about other users? Please also check whether the migrated users can access the mailbox by using OWA 2013. Also create a new mailbox in Exchange 2013 to check whether the account can be configured in Outlook properly.

Please reset your IIS service and check whether you can manually configure this Exchange 2013 account in Outlook. If there is any error description when the user fails to configure account in Outlook, please collect any error logs and post it here for more analysis. We can also check the autodiscover service by using Microsoft Remote Connectivity Analyzer:

https://testconnectivity.microsoft.com/

Thanks,

There were issues with certificate not correctly integrated in IIS. 

AUtodiscover has been set correctly, iis rebooted, and all worked. 

Thanks

Thanks for the update 

I am also having some challenges on the CAS side for my 2007 to 2013 migration:

1- I have 2 legacy CAS servers in separate sites with the same public domain name. I can assign one to legacy.company.com but what do I do with the other one? legacy2.company.com?

2- When I setup E2007 I had a big issue with internal autodiscover URL and naming. The public FQDN is different than the internal FQDN. (owa.company.com vs. cas2013.company.internal). Given the coexistence situation, I don't know how to migrate this internally without the users getting those pesky SSL prompts from Outlook stating the server has a different name than the SSL cert shows. 

hi,i have a similar issue;

We have existing Exchange 2007 SP3, and we just installed 2 Exchange 2013 SP1 in DAG configuration to co-exist with Exchange 2007. Everything went smoothly with the installation and configuration.

The OWA is working perfectly fine BUT our problem is with the Outlook anywhere, All new users(Outlook 2010,outlook 2013) cannot connect to the new Exchange server 2013. The Error is The action cannot be completed. The connection to Microsoft Exchange is unavailable.Outlook must be online to complete this action. The exchange 2007 clients are still ok connected to exchange 2007.

i already added 2 autodiscover record in the DNS with the ips of 2 exchange 2013 servers. i can ping now autodiscover BUT still has the ERROR. We also run the EXRCA tool and it fails to Autodiscover. Please help setup the correct autodiscover.
mail2 exchange 2007 outlook anywhere
mail3 exchange 2013 SP1 server
mail4 exchange 2013 SP1 server
mail5 outlook anywhere for the 2 exchange 2013(single namespace for the 2 exchange 2013 server)

The autodiscover details below;

Get-ClientAccessServer | FL AutoDiscoverServiceInternalUri

AutoDiscoverServiceInternalUri : https://mail2..com/autodiscover/autodiscover.xml

AutoDiscoverServiceInternalUri : https://mail5..com/autodiscover/autodiscover.xml

AutoDiscoverServiceInternalUri : https://autodiscover..com/autodiscover/autodiscover.xml

Awaiting for any help....