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

Ken Schaefer ken.schaefer at
Thu Sep 23 22:51:37 CDT 2004

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 it
> 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 able
> 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

More information about the thelist mailing list