ASP on IIS6 (opposite question; was RE: [thelist] ASP.NET on IIS 5?)

Shane Miller smiller at
Thu Sep 23 23:17:32 CDT 2004

To reiterate --- it was nothing obvious.

I had performed everything indicated in 812614, and several other articles.
I'm not a neophyte.

Your statement about the lockdown policy is partly true.  Yes, I had locked
the machine down tightly and also in part according to my own procedures.
All the KB articles about IIS 6, Windows2003 Server, ASP, etc were properly
applied and it still didn't work --- however, typically the various
resources don't always work on anything other than default installations, or
installations modified according to published procedures.  Departing from
the published procedures is rather sporting.  

But, in conclusion:

1.  I think that the knowledge base for IIS 6 and Windows 2003 server still
has some growing to do.  That's self-evident but also true based on my
experience, having spent lots of time over the years in the KB for a number
of Microsoft products. 

2.  Microsoft is deprecating "classic" asp.  Also self-evident.

Overall, I've found Windows2003 Server and IIS6 to offer unparalleled ease
for the administrator --- but there is still room for improvement in the
documentation, especially for those who work "out of the box".

Shane Miller

-----Original Message-----
From: thelist-bounces at
[mailto:thelist-bounces at] On Behalf Of Ken Schaefer
Sent: Thursday, September 23, 2004 8:52 PM
To: thelist at
Subject: Re: ASP on IIS6 (opposite question;was RE: [thelist] ASP.NET on IIS

So the tediousness of getting ASP working again had more to do with
your lockdown policy than any inherent problem with "re-enabling ASP"

As for permissions, you could have used this:
Default permissions and user rights for IIS 6.0



On Thu, 23 Sep 2004 20:28:53 -0700, Shane Miller
<smiller at> wrote:
> Hi,
> It was tedious because when we locked down the machine just before taking
> to production, we really locked it down --- I don't recall exactly what we
> did but it was extensive, much more than the normal procedure.  We didn't
> anticipate wanting classic asp to run on that machine, ever.  And, we made
> the decision to enable it after it went into production.  It's normally a
> simple procedure, but --- anyone who has been an NT administrator for long
> knows things don't always go as expected.  So we couldn't simply run basic
> reinstall procedures without bringing services down for awhile, which we
> wanted to avoid.  Eventually what I did was find a Knowledge Base article
> that detailed default file permissions, but for Windows 2000, but I was
> to adapt that to our Windows2003 Server.  We didn't document much as we
> went, but I posted to a newsgroup, I'll see if I can drum it up and will
> reply to the list as it contains some more detail on the problem.
> Shane Miller

* * Please support the community that supports you.  * *

For unsubscribe and other options, including the Tip Harvester 
and archives of thelist go to: 
Workers of the Web, evolt ! 

More information about the thelist mailing list