This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 74%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDM%3C/text%3E%3C/svg%3E)
Since Exchange 2019 no longer has a dedicated CAS role like previous versions how could I go about setting up a server that just ran OWA and ECP access? I have an application that has to be installed on the server running OWA but can not be installed on the currently setup Exchange servers.
Thanks
I would ask the application vendor or owner. If it cant be installed on Exch 2019 as it is now, you have three choices:
It can run on Exchange 2019, just not on one of the existing installs. There would be conflicts, that is why I need another install of Exchange 2019, but it only need to have OWA access interface.
Thanks
Ok, then you should be ok the it sounds like :)
There is of course no way to separate the roles in 2019, so the new server can have a single database on with no user mailboxes.
Set the SCP and existing client URLs to the other mailbox servers that handle client requests.
https://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2016/
(applies to 2016/2019)
Thanks for the quick answer. I will try it out tomorrow when I have more time.
Thanks again!
Something odd happened. So my original servers are all behind a hardware load balancer. the new server I was going to use for OWA only has not been put into the load balancer at all and does not have any open ports for external access. Yet some users externally are making connections to the new server. It does not have any mailboxes on it at all, completely empty mailbox database. How can I prevent users from using the new server at all?
Thanks
Yea, that was from my previous comment:
Set the SCP and existing client URLs to the other mailbox servers that handle client requests.
https://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2016
Set these values to the load balancer values on the new server so clients will connect to the servers in the load balancing pool and not the new server
In other words, these URLS and SCP for autodiscover should all match on every server - even the server not in the load balanced pool.
See all 8 steps in that doc
So my next step in that process would be to configure the new Exchange server to use ADFS and Windows Web Application Proxy. Im following https://www.petenetlive.com/KB/Article/0001546
The problem is that if this works I will want to do it again for a different domain, since our Exchange is handling multiple domains. But on the step to set-organizationconfig it seems to be able to be set for only one adfsissuer. How can I work around that and have multiple adfsissuers in the same exchange environment for multiple domains?
Thanks