I am building an Exchange environment in a new AD site in my environment.  After installing the CAS role on two servers at this site, I am not able to really use them.  Going to the ECP virtual directory and logging in just forwards me to the OWA page for my admin account.  Likewise doing a get-ecpvirtualvirtualdirectory from the Exchange Shell on any server be-it in my first site or the new site only returns results for the old site.  It hangs what seems like indefinitely after returning those results and trying to contact the new CAS servers.

Site A (Old site):
Domain Controllers (many)
2 CAS Servers
6 Mailbox Servers (4 in one DAG - 2 in another DAG)

Site B (New site):
2 Domain Controllers (same subnet as Exchange servers - In AD Sites and Services)
2 CAS Servers
0 Mailbox servers currently (slated for install next week)

AD seems fine.  No replication issues, and the subnet is in ADSS as it should be.  Would the lack of on-site mailbox servers be the problem here?  I'm having my networking team investigate possible problems on their end, but so far that has not been fruitful.  

Hi,

According to your description, I understand that login ECP will auto jump to OWA page, and run Get-EcpVirtualDirectory always return results of old site.
If I misunderstand you concern, please do not hesitate to let me know.

Do you login ECP or EAC? If you want to login ECP, please login OWA then click all setting to review setting in ECP with administrator account.
Which version are you used in your environment? If youre in a coexistence scenario, please use https://CAS name/ecp/?ExchClientVer=15 to login ECP for Exchange 2013. More details about Exchange admin center, for your reference: https://technet.microsoft.com/en-us/library/jj150562(v=exchg.150).aspx

Would you please run Get-EcpVirtualDirectory | FL Identity,*URL* in each site to double check the configuration of ECP virtual directory? Besides, please run Get-ExchangeServer | FL in each side to check available Exchange server, then ensure all Exchange services works fine in your new sites.

Thanks

Hi Allen,

We are in a coexistence scenario although our 2010 Environment is about to be decommissioned and serves no mail or services. We are going to the right url for the eac (I call it the ecp out of habit).  Likewise a get-ecpvirtualdirectory | fl identity,*url* returns matching config across sites.  Again, this works fine in one site.  We've had the environment stood up for a year now.  It's just an issue with the new site CAS's that have no mailbox servers there.  Same domain.

Thanks.

Paul

Hi,

Backend servers have gone in, and this is still a problem.

Paul

Exchange is going to redirect your OWA/ECP session to the CAS located in the site where your mailbox is.  If you want people in site B to use the CAS Servers in site B, then you would need to add mailboxes and mailbox servers to site b.  

Hi,

Backend servers have gone in, and this is still a problem.

Paul

What CU is this for 2013? CU7 fixes some of these issues.