Discussion Locked

Install OWA in non-default Web Site

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

It is very easy and smooth to install OWA into the default web site. My questions are:

1. How can I install the OWA into a non-default web site?

2. If can not install diretory, how to create a virtual application/directory in another web site after the default installatioin is done?

I spent some time to figure out how to do the second option, but failed.

If I point the virtual root to exchange/webdata, the virtual directory does not work at all.

If I point the virtual root to exchange/webdata/USA, and copy the global.asa to the /USA directory, it will work except view mail/contacts, etc. The error is similare to what is in KB 192930.
The ULR path should be like:
/exchange/forms/IPM/Note/frmRoot.asp?
but now is/exchange/forms/IPM.NotefrmRoot.asp?

Since the path is calculated by some components, virtual root pointed to /webdata/usa will not work.

Thanks for your help!

-Yuemo

3 replies

by judds

I have done this, the easy and fastest way I found; I redirected the default website, to //<

by yuemo

It helps. But I tried other hard way, to put the original default web site contents into a new non-default web site, and keep exchange to be in the default web site.

Thanks!

This discussion is closed to new replies.