Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HTTP Virtual Server Question

Status
Not open for further replies.

JabbaTheNut

Programmer
Jul 29, 2002
176
US
I have established a new website in IIS 5.0. I now have the "Default Web Site" and the new "My Web Site". I have replicated all of the Exchange 2000 OWA virtual directories from the "Default Web Site" into "My Web Site". OWA works beautifully under the new web site. My problem relates to the "Default Web Site". It is as follows:

I deleted all the Exchange 200 OWA virtual directories from the "Default Web Site". This prevents OWA requests from being picked up by the "Default Web Site". However, when I reboot the server, all the previously deleted virtual directories reappear. How do I permanently remove these virtual directories? The "Default Web Site" virtual directories in question are the following:

Exchweb
Exchadmin
Exchange
public

Any thoughts? Game Over, Man!
 
You have Exchange installed.
The easy way would be to disable this virtual site and create a new one.
By deleting all this content has probably broken Outlook web access - did you want to do that?
 
I want to run Exchange 2000 OWA from "My Web Site" instead of "Default Web Site". When I created "My Web Site", I also created the required virtual directories for OWA 2000. All works great. However, I now want to disable access to OWA through "Default Web Site" (I am using "Default Web Site" for something else). When I delete the virtual directories there, they reappear every time the server is rebooted. How do I disable access to OWA 2000 in "Default Web Site" while retaining access to OWA 2000 in "My Web Site"? Game Over, Man!
 
hmmm. seems odd this one.
I'd create a host header under 'advanced' and give it some weird value like 'noserverhere.noserverhere.noserverhere' - then no one would ever talk to this virtual server. And put it on a silly port number.
But still doesn't answer your original question - I've done plenty of OWA servers with internet sites bolted on but never come across this problem. Sounds like the Metabase is possibly in trouble... - anyone know of any metabase integrity tools?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top