Our Exchange 2007 sp3 CAS server is working fine for OWA. I am trying to split the ActiveSync and OWA. I am planning to add a 2nd CAS VM server to be used for ActiveSync only. I have done this in the lab and by default the 2nd server became my default OWA. While I am researching, I Like to know if there is a best practice white paper on this somewhere. Thanks

Why are you trying to split it? The only way the second server would become your default OWA is if you change the DNS entry people use to get to OWA. A user enters a URL to get to OWA, and that points to an IP address that ends up at a CAS. Unless you have more than one site and have redirection enabled, or something like HTTP-to-HTTPS redirect configured, nothing would redirect the session to another CAS.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

We are implementing third party software for smart phones. Software is require to use ActiveSync server and vendor is asking to split the traffic between OWA and Activesync. In the lab, as soon as I finished installing CAS-2 server, when start my OWA which is set for CAS-1 will redirect to CAS-2. I have not setup anything in the DNS. I am assuming this will not happen in production because it is set to use first CAS, but sure.

I would set the externalURL on the ActiveSync virtual directories on any internet-facing CAS to the CAS server you want them to connect to so autodiscover directs them correctly To prevent mobile devices from connecting to the other CAS You could also disable the ActiveSync virtual directory on the CAS you dont want them to connect to as well.

CAS-1 will be used for OWA only. CAS-2 will be used for ActiveSync only. TechNeth has link on how to to disable ActiveSync on CAS-1. How do I disable OWA on CAS-2 that is used for Activesync only?

CAS-1 will be used for OWA only. CAS-2 will be used for ActiveSync only. TechNeth has link on how to to disable ActiveSync on CAS-1. How do I disable OWA on CAS-2 that is used for Activesync only? A redirection perhaps? Or just simply stop the OWA App Pool? Set permissions on the virtual directory perhaps to deny? I would keep it simple regardless, something you can easily undo. If you have an intelligent load-balancer with SSL offloading deployed, you could inspect the traffic on the load balancer and redirect the connections to the CAS you want as well.

I was hoping to make the lease changes by following the best practice. I would probley stop all appPools except active sync, but not sure what else could break. Most likely we will be OK. I will be purprise to learn that we the first to spilit ActiveSync and OWA using a third party software!

I was hoping to make the lease changes by following the best practice. I would probley stop all appPools except active sync, but not sure what else could break. Most likely we will be OK. I will be purprise to learn that we the first to spilit ActiveSync and OWA using a third party software! I would ask the vendor how they recommend you implement this

Hello, Just add the second CAS server and enable the ActiveSync on it. Make sure the ActiveSync url is pointed to the new CAS. Also notice, when you install the new CAS, other web services, such as autodiscover (SCP) and availability services, are installed automatically. To avoid confusion for Outlook client sit’s better to set the autodiscover to NULL by running “Set-ClientAccessServer –AutodiscoverServiceInternalUri” command. Thanks, Simon

Installed CAS-2 today in Prod. All Good. Next planning to disable ActiveSync on prod OWA CAS-1 and install certificate on CAS-2 and test devices. Thanks