MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

Exchange 2016: Http to Https Redirection

Some of the org require you to do the http to https redirection for error correction and redirection in a cloud setup where every org can type mail.orgdomain.com or users may not type https and /owa. In this case they should still reach to the correct owa url https://mail.cloud.com/owa

In this blog I am explaining simple steps which should will not require any reconfiguration post every CU update. In case you have configured redirection using error code 403.4 then you might require to configure it again when you deploy next CU.

 

These are very much same steps, we had explained for Exchange 2013 – http://msexchangeguru.com/2013/10/30/http-redirect-owa-ecp/

 

This is for all servers and not just single server so repeat the below mentioned steps on all the servers.

-Open IIS Manager
-Expand and Highlight Default website and click HTTP Redirect


-In the properties of HTTP redirect type the below mentioned url and click Apply

            https://mail.domain.com/owa

 

-Click on Default Web Site now and double click on SSL Settings then uncheck the checkbox which is in front of “Required SSL”

                              -Now click apply to save it.
                              -Configure the other sub Virtual Directories as per below table.

Vitual Directory

SSL enabled

HTTP Redirect

Default website

No

Yes

aspnet_client

Yes

No

Autodiscover

Yes

No

ECP

Yes

No

EWS

Yes

No

mapi

Yes

No

Microsoft-Server-ActiveSync

Yes

No

OAB

Yes

No

owa

Yes

No

PowerShell

No

No

Rpc

Yes

No

                   -Run IISreset /noforce

That’s it. Simply done.

 

Prabhat Nigam

Microsoft MVP | CTO @ Golden Five

Team@MSExchangeGuru

2 Responses to “Exchange 2016: Http to Https Redirection”

  1. Kewal Kishore Says:

    No changes required on Back End Website?

  2. Prabhat Nigam Says:

    No, we never do anything on backend.

Leave a Reply

migrate exchange to office 365

Categories

Archives