Forum Discussion
ECP Redirect to url for exchange server in another AD Site
Hello Raechel Moermond
If i understand correctly , you want to reach your ECP Url on the On Prem Hybrid , but without luck.
Have you checked that he ECP Virtual Directories for the INTERNAL url are correct ? ( the URL you try to reach basically ) ? Also Important did you checked the OWA Url matches the ECP Url , also Internal ?
And finally whatever URL is the ecp e.x : https://hybrid.au.someone.com/ecp , the FQDN must be included on your Certificate , or at least a Wildcard Certificate for the Domain should exist
A common mistake also is the DAG. Remember the DAG is NOT the CAS Endpoint , just a reminder here maybe it switches something. It really gets me though the issue like it is an issue that is going on for a long time..... Don't fear to change the Exchange and have a look on your Virtual Dirs ECP in relation with OWA. You can also recreate them without messing anything at all and to tell you truth it is not a common thing to point to the autodiscover Endpoint. Use a DNS resolvable FQDN, and avoid Server Names.
- Hi, If you still have issue, please let me know so that I may help you resolve it.
- Hi, Yes, I have this issue.
Let me tell you configuration:
1. Multiple sites
2. Each site have 2 Exchange servers 2019 and configured with DAG on each site.
3. First installed exchange server 2019 ECP address redirect however, I each site have own ecp addresses.
4. The Admin account, I used either from same site or other site, it has same issue.
5. Admin Account doesn't have mailbox.
Please let me know if you need more info.What about OWA? is it the same with that too?
Please also, refer to my last comment, and provide the output to me, so I have a better understanding about how ECP is configured there (Don't Forget To Replace Sensitive Information, Like Your Domain Name, With Dummy Text)
Run those commands on one of servers in each site (results should be the same, however)
yeah I resolved it. I don't remember how...it may have simply been resolved when I decommissioned all the other servers. but it's been a few years since this happened. Sorry I can't be more help.
