I'm trying to put Exchange client components into inactive state

Set-ServerComponentState -Identity exch1 -Component ServerWideOffline -State inactive -Requester Maintenance

or

Set-ServerComponentState -Identity exch1 -Component OwaProxy -State inactive -Requester Maintenance

After that I'm still able to use OWA. Is it properly wo

Hi,

Its block the OWAproxy. You can use the following command to see the status for all the supported components:

Get-ServerComponentState Identity <ServerID>

For more reference:

http://blogs.technet.com/b/exchange/archive/2013/09/26/server-component-states-in-exchange-2013.aspx

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

So if it blocks OWA proxy, the OWA should working or not?

Hello Jacek Kochan,

You can check the details about OWA proxy and redirect by the following article:

https://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx

If you would like to disable OWA for all the users, you can try the following command:

Get-Mailbox | Set-CasMailbox UserName@DomainName -OWAEnabled $False

To re-enable them:

Get-Mailbox | Set-CasMailbox UserName@DomainName -OWAEnabled $Ture

More switches:

https://support.microsoft.com/en-us/kb/2573225?wa=wsignin1.0

Hope this helps.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

Unfortunately the article do not provide answer for my question. There is no information about behavior of switch OWAProxy and other proxy components to inactive state. Also I'm not interested with disabling OWA for users. My question was simple - whether proxy component should be working or not when it switched to inactive state by Set-ServerComponentState in case of for example maintenance jobs on particular server. I noticed that after switching to inactive it still working, so I want to find out, what I'm doing wrong.

Hello,

OWA proxy happens when you have multiple sites and multiple CAS servers. For example:

1. A company has two sites in country A and B.

2. Country A has Exchange Server A with all roles installed. This CAS is internet facing.

3. Country B has Exchange Server B with all roles installed. This CAS is not internet facing.

4. OWA url is https://contoso.com/owa point to the CAS server in Country A.

The OWA proxy will happens when the users on Country B access their OWA. CAS1 receives the OWA request from Internet and found the Users is on MBX B. Then it will proxy the request to CAS B.

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

 

Hi,

Is there any update on this thread?

Thanks,

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

Still i haven't noticed any impact of disabling proxy components with working clients.

Inactive state of transport works as expected. Telnet to connector ends with "421 4.3.2 Service not active".

Inactive state of proxy components has no influence on client connections. For example I am able to  open OWA conection direct to this server trying to open mailbox resided in different site.