In this short post, we will look at preventing a CAS server from proxying traffic.

Let’s suppose you are migrating from Exchange 2010 to 2013 or even 2016 and you do not want your Exchange 2010 Server/s to act as a proxy target.

You could run the following command to enable this:

  • Set-ClientAccessServer –identity CASServer1 –IsOutOfService $true

Once that command is run, CASServer1 in this example will not receive any more proxy traffic from other CAS servers until you set the command to false.

Hope it helps.

Discover more from COLLABORATION PRO

Subscribe now to keep reading and get access to the full archive.

Continue reading