Re: ADSI to detect if New Virtual Web/FTP Servers allowed

From: Kristofer Gafvert (kgafvert_at_NEWSilopia.com)
Date: 03/26/05


Date: Sat, 26 Mar 2005 08:45:20 -0800

Hi,

I'm not really sure how this would be accomplished. There is no parameter
or anything that tells you if the webserver is "locked down". And i'm not
sure how such parameter would look like, because what is the meaning of
"locked down". Does it mean the same on all IIS servers? Does it have
anything to do with the number of connections? The number of websites that
can be run? Anything else? As you can understand, it would be useless to
implement such thing.

You can create multiple websites on Windows XP Pro, so there is no such
limitation. (you can however have no more than one running)

I belive that if you do not want to check the OS, you will have to have
your code fail (which doesn't necessary mean that your application crash,
if you catch the error).

But honestly, i do not understand your statement with future OSes. What
says that the API you are using is supported in future OSes? What says
that the IIS SDK will not change?

So you cannot write code that will never fail in the future, when your
code depends on something else.

What i am trying to say is that you will have to check your code every
time a new version of IIS is released, and make sure that it works with
the next release.

-- 
Regards,
Kristofer Gafvert
www.gafvert.info - My Articles and help
www.ilopia.com
James Han*** wrote:
> I'm writting an application in C# that can add web servers etc.  The 
problem
> is that i need to detect if the IIS Server is locked down because of 
Windows
> 2000 pro or XP Pro or whatever.  I don't want to do an OS check because 
it
> will fail with new OSes that get released.
>
> Is there some information somewhere in the metabase or other API that 
will
> give me a clue that IIS is running on a machine that doesn't allow 
multiple
> virtual web servers (i.e. Windows XP Pro) without having to just try to
> create the web server and have it fail?
>
> Thanks!