Freigeben über


IIS and Virtual Server Conversations

Question:

In preparation to installing Virtual Server, and acknowledging the fact that it needs IIS, I would like to know:

  1. Is there any specific setup to perform on the IIS before I configure VS? Or, will it just need to be there?

    Also, since now I have web server software installed, I would like to configure it to make use of CGI (Perl!) and I am studying a description to do that right now - it mentions creating a directory where I can store the scripts AND a virtual directory under the IIS that points to this directory - now, this substitution of one directory for another was something that you could do in DOS, as I recall, so:

  2. Is this 'virtual directory' stuff something that is specific to IIS? Because the Windows filesystem wouldn't understand such a 'critter'.

TIA

Answer:

  1. You just need to make sure IIS is installed prior to install Virtual Server 2005 R2. This allows you to install the Admin Website component of Virtual Server, whose setup takes care of everything else
  2. "Virtual Directory" stuff is specific to IIS.

IIS stores the Virtual-to-FileSystem mapping inside of its configuration file, and whenever it receives a HTTP request for a URL in the Virtual namespace, IIS translates it to a resource in the FileSystem namespace using its configuration.

At this point, you can have any other mapping in effect in the FileSystem namespace (for example, NTFS junction points) to do further name mapping, but we are getting a bit more complicated now...

FYI: Virtual Server does not need IIS to administer/function. I use Virtual Server all the time without IIS. See this blog entry:
https://blogs.msdn.com/david.wang/archive/2005/06/21/Virtual_Server_2005_Administration_on_IIS.aspx

//David

Comments

  • Anonymous
    December 23, 2005
    Thank you, David.

    I printed the schematic graph, that may be just the sort of thing I can lean on, when things get rough.

    In all of my career as a hobby builder - maintainer - operator - programer of computers, I've always felt there was nothing about a computer that I couldn't understand, except documentation. IIS documentation is just about the most convoluted piece of knowledge I have come across, it's like a university course, an extremely demanding technical approach that aims to push everything else asside in order for it to be absolutely clear, logic and correct across multiple interpretations. This is fine if you do nothing else for six months. As for me, I cannot bridge the gap, I have far too many interests - do you know of any kind of book or web resource that gives IIS a more conversational treatment? (I havn't yet more than browse through your blog, which seems rather more than just interesting)

    I know, it is really all very simple. I'ts just unfortunate that you'll have to be a genius to see the simplicity! Working with it would rapidly make it clear to me on it's own, but it might be a long and winding trail, on my own, since I wouldn't have much [need] for doing any serious work with it.
  • Anonymous
    December 23, 2005
    The comment has been removed
  • Anonymous
    December 23, 2005
    The comment has been removed
  • Anonymous
    December 23, 2005
    The comment has been removed
  • Anonymous
    July 09, 2007
    Hello! I'm newbie here and that's why I need some help. Can you give me any info or any links where I can get general help on using forum. I think that this info will be usefull for all newbies. Thanks a lot! P.S. Pardon me for my making this thread in wrong section

[url=xgloq.net]Texas[/url]...I'm lovin' it :)

  • Anonymous
    June 05, 2008
    The comment has been removed
  • Anonymous
    June 07, 2008
    Andrew - By default, IE does not auto-login with user credentials when the target servername is dotted address. This prevents accidental leaking of internal username/password to external websites. This includes IP-Address as well as FQDN-Address. You need to make sure that the specific dotted address is placed in an IE zone which does allow auto-login with user credentials to address the login prompt. //David