|
Posted by seh on August 28, 2006, 3:18 pm
Please log in for more thread options Steve,
Thanks for the info. I've tried the +r SeInteractive and -r SeDeny for
admin. I'll try it for all other groups as well. I'm assuming in your
response, for the -r it would be SeDenyInteractive...?
Thanks,
seh
"Steven L Umbach" wrote:
> Assuming you have access to the server over the network as an administrator
> as evidenced by your ability to access and administrative share such as C$
> then NTRights should work. Keep in mind that the privilege you specify with
> NTRights is case sensitive which means that SeInteractiveLogonRight and
> SeDenyInteractiveLogonRight need to be typed exactly as shown. Also the
> server may need to be rebooted after changing user rights. I would try
> giving everyone +r SeInteractiveLogonRight and then grant everyone, users,
> authenticated users, and administrators -r SeInteractiveLogonRight as any
> user that is included in deny logon user right will not be allowed to logon
> even if they have allow user right. If none of that helps you could also try
> using psexec from SysInternals/Microsoft to access the command prompt on the
> locked out server and use secedit to reset user rights back to default
> defined levels being sure to add areas / user_rights to the end of the
> command as shown in the KB article below. If you don't specify /areas the
> command will disable many critical services on Windows 2003.
>
> Steve
>
> http://www.sysinternals.com/Utilities/PsExec.html --- psexec
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;313222
>
> > Does anyone know how to reset the policy settings back to the default out
> > of
> > the box settings? We had a "power user" decide he needed to update his
> > stand
> > alone server with member server updates. Now everyone is locked out and
> > unable to log in. I can map a drive to the box and connect to the box w/
> > mmc. I've ran ntrights to add LogonRights, but it still fails. It cycles
> > between to errors, Policy doesn't allow you to log on locally and Not in
> > the
> > Allow Remote Login.
> > Any suggestions?
> > Thanks,
> > seh
>
>
>
|