W2k Pro and XP Pro do not have operator tab.
"Andrew Clancy" <contactATachrenDOTorg> wrote in message
news:#LtyyPXgEHA.1184@TK2MSFTNGP12.phx.gbl...
> Thanks Greg - but I dont have the operators tab in windows 2000 pro for
some
> reason?
> Is there a group policy I can apply that achieves the same?
>
> Does this solve my .Net project creation problems too?
>
> Thanks,
> Andy
>
>
>
> "Cowboy (Gregory A. Beamer) [MVP]" <NoSpamMgbworld@comcast.netNoSpamM>
wrote
> in message news:e0d5PIWgEHA.3192@tk2msftngp13.phx.gbl...
> > Windows 2000
> > Easy: Log in as admin and add their accounts to the Operators tab.
> >
> > Windows XP
> > Create a stub to run as admin, as the operators tab is gone.
> >
> > --
> > Gregory A. Beamer
> > MVP; MCP: +I, SE, SD, DBA
> >
> > ************************************************
> > Think Outside the Box!
> > ************************************************
> > "Andrew Clancy" <usenet@achren.org> wrote in message
> > news:dd2d6f95.0408130915.6f6d2df3@posting.google.com...
> > > Hi,
> > >
> > > I am trying to set up VS Developer users with non-administrator rights
> > > debug ASP (3) in VB.Net, and of course manage IIS MMC. This has
> > > succeeeded on 3 machines, including my own - but since then it hasnt
> > > been able to work, with seemingly exactly the same install & debug
> > > setup. All machines are Windows 2000 with IIS 5.0.
> > >
> > > My main 2 problems are:
> > > 1. the user cannot see the web site properties in MMC.
> > > 2. I get all of the errors from this kb article
> > >
http://support.microsoft.com/default.aspx?scid=kb;EN-US;320451 > > > (but tried the resolution and it's not it)
> > >
> > > I have tried re-installing IIS, VB.Net & ASP.Net 1.1 (in that order),
> > > doing the usual permission stuff (adding the user to debugger & vs
> > > developer group, file permissions on inetpub and temp asp.net files,
> > > etc etc). Frontpage is installed (this shouldnt matter as it is a
> > > local box not remote debugging). And I've tried aspnet_regiis.exe
> > > reg'ing aspnet_isapi.dll). I've tried everything!
> > >
> > > This is an absolute pain as we are all still developing in ASP 3 and
> > > moving forward has taken 18 months sofar and got nowhere - any ideas
> > > would be great!
> >
> >
>
>