OWA Redirect Did Not Work After Replacing New Certificate

Yesterday one of my customer ran into some issue after replacing a new certificate for Exchange.

My customer's  public certificate is going to expired soon, they had requested us to replace it with a private certificate instead. Everything works fine after replacing the certificate, and I’ve verified with the them before I leave.

After few hours somehow I was told that OWA redirect is not working anymore and user cannot login into OWA. Please read the similar symptom here:

This error actually only happen if the Exchange server has redirect from HTTP to HTTPS features implemented. The redirect will eventually create infinite loop although you run “iisreset” and all the authentication method(owa,active_sync,outlook_anywhere,ecp and etc) will not work unless you manually configure them.

Troubleshooting Steps:

1. check the Exchange virtual directory using EMS, type Get- WebServicesVirtualDirectory and to make sure the URL is correct

2. goto IIS manager -> default website ->HTTP redirect -> make sure the box is check “redirect request to this destination” and insert the the url ending with /owa.

3. check the box “Only redirect requests to this content in  this directory” (not subsidiaries), with status code (found 302)

4. On the default website, click SSL settings and uncheck "Require SSL" .

5. Remove the enforced redirect for following directories:

• aspnet_client
• Autodiscover
• ecp
• EWS
• Microsoft-Server-ActiveSync
• OAB
• PowerShell
• Rpc

5. run iisreset in CMD

Everything working back to normal after steps above is done.