Publish New Webs in their own Virtual Directory

  • Thread starter Thread starter Jimmy May
  • Start date Start date
J

Jimmy May

Publish New Webs in their own Virtual Directory

I'm relatively new to web design & IIS. I'm a bit
confused about (among many other things), the placement of
web sites when published to a web server. The way
I "like" to do things is to have the new web listed
directly underneath (parallel to) IIS' Default Web Site.

In other words, in MMC:

Internet Information Services

When I have a virgin server, the web gets published as the
Default Web Site.

When I have a server that already has a default web site,
the new web site gets publishes as a subweb, WITHIN the
Default Web Site. In other words:

Internet Information Services
I don't want that! I want to create

The only way I've managed to get around this is to create
a Virtual Directory in advance. But on some servers, I
don't have the privileges to do that.

My questions:
1) Is there a way I can do this from FrontPage, i.e.,
publish new sites to servers OUTSIDE the Default Web Site?
2) How can I "clean up" the Default Web Site that's been
littered with a site that wasn't intended to be the
Default Web Site?
Thanks!

Jimmy May
317-590-8650
jimmymay<@>earthlink.net
 
They need all to be under the root FP SE web

| >>Server Name
| >>>>Default FTP Site
| >>>>Default Web Site (can be an empty web)
| >>>>>>MyNewWeb
| >>>>>>AnotherWeb
| >>>>>>YetAnotherWeb


--



| Publish New Webs in their own Virtual Directory
|
| I'm relatively new to web design & IIS. I'm a bit
| confused about (among many other things), the placement of
| web sites when published to a web server. The way
| I "like" to do things is to have the new web listed
| directly underneath (parallel to) IIS' Default Web Site.
|
| In other words, in MMC:
|
| Internet Information Services
| >>Server Name
| >>>>Default FTP Site
| >>>>Default Web Site
| >>>>My New Web Site
| >>>>Another Web Site
| >>>>Yet Another Web Site
|
|
| When I have a virgin server, the web gets published as the
| Default Web Site.
|
| When I have a server that already has a default web site,
| the new web site gets publishes as a subweb, WITHIN the
| Default Web Site. In other words:
|
| Internet Information Services
| >>Server Name
| >>>>Default FTP Site
| >>>>Default Web Site
| >>>>>>My New Web Site
|
| I don't want that! I want to create
|
| The only way I've managed to get around this is to create
| a Virtual Directory in advance. But on some servers, I
| don't have the privileges to do that.
|
| My questions:
| 1) Is there a way I can do this from FrontPage, i.e.,
| publish new sites to servers OUTSIDE the Default Web Site?
| 2) How can I "clean up" the Default Web Site that's been
| littered with a site that wasn't intended to be the
| Default Web Site?
| Thanks!
|
| Jimmy May
| 317-590-8650
| jimmymay<@>earthlink.net
|
|
 
I'm disappointed to see your answer to 1), but it's good
to know with certainty. With regard to 2), I understand
your point, so I'll try to explain. Though I'm a
certifiable, er, ah, certified DBA, I'm new to IIS, and
I'm in charge of a new Web Server that will as soon as
possible be in production and will hold all the existing
webs for an organization that does a bit of hosting.
Also, I'm in charge of another server that will be getting
a lot of exposure--it's got to look good and it has to be
done right, yet I barely know what I'm doing.

As I struggle to learn all the nuances of Windows Server
2003, IIS 6, FrontPage 2002, and SharePoint Services, I
need to be able to start from a clean slate, &/or
segregate byproducts of my experiments (read: mistakes)
from what Windows needs.

The problem is something I've noticed before, and here's
how it manifested itself last night. I have a brand new
server with no Default Web Site, and as an experiment I
published a sample web to it. It ended up as the Default
Web site which was completely NOT what I wanted.

I know all this stuff will be second nature to me soon,
but I don't have time to wait for "soon".

Thanks for your help!
 
Back
Top