Re: iis lockdown & admin logout

From: David Wang [Msft] (someone@online.microsoft.com)
Date: 03/05/03 

From: "David Wang [Msft]" <someone@online.microsoft.com>
Date: Wed, 5 Mar 2003 11:15:52 -0800

If either of you can help provide necessary repro instructions (OS install
and any other SW installed), we would look at it (and the general area) to
determine a fix/solution. 

--
//David
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Wayne & Carr" <NoSpam@spam.net> wrote in message
news:uRNBpve4CHA.2296@TK2MSFTNGP10.phx.gbl...
You have just ran into a Major problem, That myself had in my network
On my server, that usually gets about 500+ hits per day.
I tried everything that everyone told me to do, And it did not work.
If you are running the "WinNT 4.0 Server" And the new "iis lockdown"
Then, I think that there seems to be an issue with it and running it on NT4.
Not sure, this is just my own personal opinion.
Though I got a log of good suggestion from people in the newsgroup(s),
known of them worked.
I indeeded up having to reinstall my server from scratch "AGAIN".
Because there is one thing that you have to look at.
When you installed the "iis lockdown" tool, and you got the runtime error,
>From that point on, you basically have lost all rights to your server.
Which is a pain in the A**, but there is basically nothing that I am aware
off
And that all the suggestions that I got in, no one was able to tell me,
Yes this worked for me, It was all just,"Try this, Read more into the iis
lockdown next time,
and so forth,"
So, unless you can find someone that has "Successfully" fixed this issue,
There is not much that
you can do, But I would wait, and if you are running a productive server,
(Like I am here)
Then you are most likely wanting to get it back LIVE a.s.a.p.
Think about doing to reinstall,
It takes me about 4 hours, from shut down, to being back Fully online again,
To do mine.
Then pointing records, and setting up DNS, is an additional 1 hour.
So basically about 5hours, and it is ready.
Sorry that this is not what you are wanting to hear.
Take Care
Wayne

Relevant Pages

  • Re: SUS, IIS Lockdown and Terminal Server
    ... This has been discussed in the SUS newsgroup ... Server Requirements and Recommendations for Installing Microsoft Software ... If you are going to install SUS on an existing server, ... Better integration with IIS lockdown tool ...
    (microsoft.public.win2000.security)
  • Re: New Event Log Errors!
    ... Somehow along those lines I'd also installed the Certificate Authority ... Did you apply the last Server Pack for SBS Server? ... Please install Windows Support Tools on the win2k3 sp1 problematic ... Microsoft is providing this information only as a convenience to you: ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)