PLEASE HELP - WIN SERVER 2003 - LOCKED OUT!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Server 2003 - Error: "

Local policy was accidentally set to disable local logins for a group of users. WE CAN BOOT UP-but are COMPLETELY LOCKED OUT.

There may be some unaffected users, but they would be default accounts that we can't reference.

Please let me know if there is a way to change the local policy through command prompt.

Is there any system restore or go back for Windows 2003?

Is there a way to enable remote desktop without logging in!?

Suggestions for reinstallations/upgrades

Any suggestions? Anything will be helpful.

I don't want to loose files and settings.

THANK YOU VERY MUCH!
 
HELP ME PLEASE!!!! said:
Server 2003 - Error: "

Local policy was accidentally set to disable local logins for a group of
users. WE CAN BOOT UP-but are COMPLETELY LOCKED OUT.
There may be some unaffected users, but they would be default accounts that we can't reference.

Please let me know if there is a way to change the local policy through command prompt.

Is there any system restore or go back for Windows 2003?

Is there a way to enable remote desktop without logging in!?

Suggestions for reinstallations/upgrades

Any suggestions? Anything will be helpful.

I don't want to loose files and settings.

THANK YOU VERY MUCH!

It seems you have found a new and highly successful way of shooting yourself
into the foot. Why would you want to lock yourself out of your own machine?

If you can reach the server via a network-connected machine then the
following steps may repair the damage:

1. Get a free copy of psexec.exe from www.sysinternals.com
2. Get a copy of ntrights.exe. It comes with the Win2000 Resource Kit.
3. Working from the networked PC, start a remote session on the
server with this command:
psexec \\YourServer cmd
4. Run this command in the remote session:
ntrights -u "Everyone" -r SeDenyInteractiveLogonRight

If your server is not configured for networking then you will probably have
to treat this event as a valuable lesson in what not to do on a server.

About the files you don't want to lose: If they are valuable, and if you
don't back them up each week, then you're heading for another disaster. I
strongly recommend that you start looking ahead instead of trying to fix
problems retrospectively.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top