Is there a way to disable CAS proxying or redirection on the internet facing CAS? The reason I am posting this question is because we need to separate the 2 OWA access (internal and external) and we only have 1 internet facing site for OWA. We have multiple sites hosting CAS/HUB/MBX in our environment.

dont understand what you're trying to do here. I assume youre using 2010? Exch will proxy/redirect OWA request so it will locate the appropiate CAS server where the mailbox is loacated. If you want to seperate internal and extrnal url, why can you configure the internal and external urls's. Have a read of the bellow http://technet.microsoft.com/en-us/library/bb310763.aspx Sukh

Hi, I’m a little confusion. Since there is only one Internet facing site for OWA, if you don’t want proxy, how do you access the mailbox on the non-Internet-facing site externally? Do you want to access their mailbox via themselves’ CAS URL? If there is only 1 Internet-facing site, you have to configure the external URL as null on non-Internet-facing CAS server so that the request can proxy to it. As an additional information, please refer to the link below: http://blogs.technet.com/b/exchange/archive/2009/12/02/3408921.aspx Thanks. Novak Wu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

How is thing going on? If there is any question, please feel free to post it here. Thanks. Novak Wu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The preference is to only use the internet facing CAS so segmentation settings are only customized on this server.

Thanks for the feedback. So the question is how can I separate the segmentation settings for Internal and External use of OWA? Not sure what the goal is. Are you saying you want segmentation to be different per user depending on whether the are connecting inside or outside of your org?

If you have multiple AD sites, with a CAS in those sites, then you MUST proxy to those sites if those other AD sites are not internet-facing.

Different segmentation settings for Internal OWA access and External OWA access. What I am finding is that it's a one sided segmenation setting for OWA access (internal or external).

Thanks for the feedback. So the question is how can I separate the segmentation settings for Internal and External use of OWA?

One way you might be able to do this is to creare multiple OWA directories and direct internal/external to the appropiate one. Set you segmentation on each directory as you need.Sukh

Different segmentation settings for Internal OWA access and External OWA access. What I am finding is that it's a one sided segmenation setting for OWA access (internal or external). This could be a management headache that could get complicated with rollups and service packs. I'm sure there is a good business reason for it, but I can't think of any :) You could create multiple OWA vitual dirs, but that could be a path you may not want to go down. There are also policies you can create on a per user basis.