Re: Using Virtual Directory to remote folder

From: Jeff Cochran (jeff.nospam_at_zina.com)
Date: 03/07/05


Date: Mon, 07 Mar 2005 21:58:57 GMT

On Mon, 7 Mar 2005 15:05:50 +0100, "Lamberti Fabrizio"
<lambu@from_italy.it> wrote:

>I've created a medium large library of ASP routine and I've published on a
>web server part of a NT domain.
>
>Now I need to publish this ASP modules on other web servers part of the same
>NT domain.
>
>For not having the problem of synchronization and versioning of ASP modules
>on different webservers I've decided to create Virtual Directory pointed to
>directories of the first webserver.
>
>What about my solution ?

What about it? Did it work? I assume you have the access across
domains issues covered, and are prepared for all sites going down if a
network break on the main server disconnects it, correct?

>Is there any other similar solution ?

You could copy them to the other servers.

>Is the creation of virtual directory pointed to network share a good idea or
>not ?

Centralized control, single point of failure, network access
permission issues. You decide which is more important or relevant to
your setup.

Jeff



Relevant Pages

  • Re: Using Virtual Directory to remote folder
    ... >web server part of a NT domain. ... >Now I need to publish this ASP modules on other web servers part of the same ... network break on the main server disconnects it, ... Centralized control, single point of failure, network access ...
    (microsoft.public.inetserver.iis.security)
  • Re: Using Virtual Directory to remote folder
    ... >web server part of a NT domain. ... >Now I need to publish this ASP modules on other web servers part of the same ... network break on the main server disconnects it, ... Centralized control, single point of failure, network access ...
    (microsoft.public.inetserver.asp.general)

Loading