<div>
I would simply create a file named &quot;index.html&quot; in the wwwroot folder that had the following code inside of it (no need to get fancy here):<br />

<pre><code class="code-1 nolinks" id="code-123612"><span>&lt;HTML&gt;</span>
<span>&lt;HEAD&gt;</span>
<span>&lt;meta HTTP-EQUIV=&quot;REFRESH&quot; content=&quot;3 rl=https://mail.company.org/Exchange&quot;&gt;</span>
<span>&lt;HEAD&gt;</span>
<span>&lt;BODY&gt;</span>
<span>You are being redirected to the appropriate page. If you do not wish to wait &lt;a href=&quot;https://www.company.org/exchange&quot;&gt;click here...&lt;/a&gt;</span>
<span>&lt;/BODY&gt;</span>
<span>&lt;/HTML&gt;</span>
</code></pre>
</div>


<div>
dfxdeimos - <br />
<br />
Knowing that the purpose of the needed <a href="https://mail.company.org" rel="ugc">https://mail.company.org</a>&nbsp;to <a href="https://mail.company.org/Exchange" rel="ugc">https://mail.company.org/Exchange</a>&nbsp;is to hopefully fix an issue with a Smartphone - does that change your response?<br />

</div>


<div>
No, but it should change the question that you ask. <br />
<br />
If you are trying to use OWA via a smart phone browser (unless its full featured like an iPhone) you are going to be dissapointed. Smartphones will usually use OMA (basically text based OWA) or ActiveSync.<br />
<br />
Perhaps you would be better of asking the question that relates to the problem that you are actually having, not the perceieved solution and how to execute it.<br />
<br />
Cheers
</div>


<div>
<div class="content wysiwyg-content">
Hi -<br />
<br />
I have a new single Exchange 2003 Sp2 Server built to replace an existing. &nbsp;<br />
<br />
We've installed an SSL cert, and configured IIS to redirect users that type in <a href="http://mail.company.org" rel="ugc">http://mail.company.org</a>&nbsp;to <a href="https://mail.company.org" rel="ugc">https://mail.company.org</a>. &nbsp;Works great, enabled FBA too for the nice login. &nbsp;To accompish this, I added an additional Web Site called 'HTTP to HTTPS Redirection', and set the TCP port to 80 and changed the Default Exchange Site to 81. &nbsp; &nbsp;The 'HTTP to HTTPS Redirection' site then is configured to redirect traffic to the Default Web Site, which has the SSL Cert configured. &nbsp;<br />
<br />
However, there is one additional customization I need to have, and that is to have the URL <a href="https://mail.company.org" rel="ugc">https://mail.company.org</a>&nbsp;(note the HTTPS this time), redirect to <a href="https://mail.company.org/Exchange" rel="ugc">https://mail.company.org/Exchange</a>. &nbsp; My last attempt at this ended up screwing up IIS pretty bad and I had to reinstall IIS and the Exchange. &nbsp;This time around I'll stop the store and take a snapshot before any changes.<br />
<br />
I can provide screenshots if needed. &nbsp;High points!<br />
<br />
Jason
</div>
</div>


Hi -

I have a new single Exchange 2003 Sp2 Server built to replace an existing.  

We've installed an SSL cert, and configured IIS to redirect users that type in http://mail.company.org to https://mail.company.org.  Works great, enabled FBA too for the nice login.  To accompish this, I added an additional Web Site called 'HTTP to HTTPS Redirection', and set the TCP port to 80 and changed the Default Exchange Site to 81.    The 'HTTP to HTTPS Redirection' site then is configured to redirect traffic to the Default Web Site, which has the SSL Cert configured.  

However, there is one additional customization I need to have, and that is to have the URL https://mail.company.org (note the HTTPS this time), redirect to https://mail.company.org/Exchange.   My last attempt at this ended up screwing up IIS pretty bad and I had to reinstall IIS and the Exchange.  This time around I'll stop the store and take a snapshot before any changes.

I can provide screenshots if needed.  High points!

Jason

IIS Changes needed for specific https:// redirection for Exchange 2003

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.