RE: Make OWA client default website?
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Fri, 17 Mar 2006 08:43:10 GMT
Hi John,
Thanks for using the SBS newsgroup.
From your description, I understand that you want to enable users to accessthe OWA using URL: https://publicFQDN and currently the OWA site can be
visited at https://publicFQDN/exchange.
If I am off base, please don't hesitate to let me know.
To redirect the Default Web Site to point to the Exchange virtual
directory, follow these steps:
1. Start the Microsoft Management Console (MMC) IIS snap-in.
2. Right-click Default Web Site, click Properties on the shortcut menu, and
then click the Home Directory tab.
3. Under When connecting to this resource, the content should come from,
click A redirection to a URL.
4. In the Redirect to box, type /exchange.
5. Under The client will be sent to, click A directory below this one.
6. Stop and start the Default Web Site.
Note that when prompt to choose sub-directories to override Inheritance,
choose NONE.
This method is easiest. the only impact is that you cannot access the
''Welcome'' page since the link is used for OWA now. However, in SBS 2K3,
you can use RWW instead which has all the features and links the
''Welcome'' page has and more.
If you have installed ISA on the server box, you¡¡can implement the task by
using a path redirection on the Path tab in the Web Publishing Rule.
Double click the OWA publishing rule, go to the Path tab, Add a new path as
following:
External Path: /
Internal Path: /Exchange\
In the case of OWA publishing, the external path is /* (which represents
all folders and directories on the site) and the internal path is
/Exchange\. Notice that you must use a backslash at the end of the path
because the OWA Web Publishing Rule Wizard already entered the /Exchange/
path.
These path redirections do the following:
When the user enters https://publicFQDN/exchange in the browser to connect
to the OWA site, the connection is directed to the /Exchange folder on the
OWA Web site.
When the user enters https://publicFQDN/exchweb, the connection is
redirected to the /Exchweb folder on the OWA Web site
When the user enters https://publicFQDN/public, the connection is
redirected to the /Public folder on the OWA Web site.
When the user enters https://publicFQDN/, the connection is redirect to the
/Exchange folder on the OWA Web site.
The reason why this works is because the OWA Web site is kind enough to
help users who don't understand the difference between UNC paths and URLs.
The OWA Web site will accept the backslash as a valid request and convert
it on the fly to a forward slash. This allows you to use the Internal Path
statement /Exchange\ and /exchange/* in the Path tab, where it would
otherwise not be possible to do this if you had to enter forward slashes
for both entries because the ISA firewall will not allow you to enter
multiple path mappings that use the same path prefix.
Just to make this clear, the reason why we must enter /Exchange\ in order
to get the redirect is that we already have a redirect for /Exchange/*,
which is associated with connections users make when they enter
https://publicFQDN/exchange. We can't enter the same path twice, so we need
to trick the ISA firewall's Web Publishing Rule by using /Exchange\
instead, which is associated connections made to https://publicFQDN/.
Hope the above information helps. I am happy to be of assistance to you and
look forward to your reply.
Have a nice day!
Sincerely,
Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Thread-Topic: Make OWA client default website?of
thread-index: AcZJJG/9qKKh0Ti+TLmj0ZxzYI3hjg==
X-WBNR-Posting-Host: 67.164.186.135
From: =?Utf-8?B?Sm9obg==?= <John@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Make OWA client default website?
Date: Thu, 16 Mar 2006 10:07:07 -0800
Lines: 3
Message-ID: <D7231640-F521-4B52-A93A-3B2A4C073550@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.windows.server.sbs:253304
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs
Can IIS be configured to make the Outlook Web Access client the default
website on a server so you only have to type in the server's URL instead
the server's URL followed by /exchange?
.
- Prev by Date: RE: Registry editing tools not allowed... (second post)
- Next by Date: RE: Administrator Profile Deleted...Help!
- Previous by thread: RE: Setting emails to be delivered at a later time on exchange 2003
- Next by thread: Re: WM5.0 Import certificate from SBS problem
- Index(es):
Relevant Pages
|
