Redirect /owa page for Outlook Web Access

By default, in order to access Outlook Web Access, user need to key in /owa. This is troublesome and most of the time user will just type the url without http://url.com.my/owa. In this guide, i will show you how to set redirect the request to /owa for Exchange Outlook Web Access.

1. Go to Internet Service Manager (IIS), click on Default Web Site and select HTTP Redirect.














2. Tick redirect request to this destination
and enter /owa and Under Redirect Behavior, click to select the Only redirect requests to content in this directory (not subdirectories) check box.
In the Status code list, click Found (302). Lastly click Apply.

This action is for request using http://email.ms4u.info. (not applicable for SSL request)














3. If you are using certificate, you must enter https://email.ms4u.info/owa . This allow the system to redirect http request to https and then redirect to owa virtual directory.














4. After set either Step 3 and 4, you need to execute the command iisreset /noforce for the new setting to take effective.

5. On the Exchange Management Console, go to Server Configuration and Click Client Access. Select the tab Outlook Web Access and go to the owa properties.














6. Modify the Internal and External URL.



















Now you can access Outlook Web Access without key in /owa..

Email cannot send out but can receive email..

This is a true story which happened to me twice: one at customer site (a month ago) and my setup lab environment (today).
Customer is using leased line from Telekom Malaysia and i'm using Streamyx line. Both from the same Internet Service Provider (ISP).

Scenario:- Email cannot send out to Internet but can receive email.

Here is my troubleshooting step:-

a) Enable protocol logging for SMTPSend.

Use Exchange Management Console > Organization Configuration > Hub Transport > Send Connector > On the General Tab > Change the protocol logging level from None to Verbose.













b) To view the log, go to E:\Exchange Server\TransportRoles\Logs\ProtocolLog\SMTPSend
(your path may be different depend on your installation).
Open the SEND.log files.












You will see a lot of transaction email which try to send via port 25.

I've tried to
1. ping to the destination public IP but received reply indicated the target host is alive.
2. Change dns forwarder to 4.2.2.2. Still the same problem.

Resolution:-

Telekom Malaysia has prevent sending email by using port 25 (most likely to prevent open relay/spam). You need to forward outgoing email to smtp-proxy.tm.net.my

a) To configure relay to Smart Host.
Go to Organization Configuration > Hub Transport > Send Connectors > Network Tab > Select Route mail through the following smart hosts > add > Enter smtp-proxy.tm.net.my














b) After configure the smart host, verify by going to the SMTPSend log again. You will see the successful email transaction as listed below.










Note:-

Remember to disable protocol logging level by setting to None after troubleshooting.