First off, that was bad!
TechNet Article ID: Q276590 talks about doing this type of thing, but it will not help you. The recommended solution is to log onto another domain member (like a workstation) and run NTRIGHTS.EXE, a tool from the Resource Kit.
Since you have one machine, this is not gonna help you!
So, the only idea I have to help is for you to hack into your Windows installation. A hack I like that should work in this instance is for you to do a 2nd install of Windows on the server,and change the logon.scr file in c:\winnt with cmd.exe. YOu do that, then boot up into your locked-out original Windows install and wait 15 minutes for the default screen saver to kick in. Don't touch the keyboard or mouse during this time so the default screen saver in invoked (where the "Press CTRL+ALT+DEL" window bounces around the screen).
When you replace logon.scr with CMD.EXE, what will happen after 15 minutes is a command prompt will open up under the Local System account access. Thissystem account has Full Control rights to the domain!
YOu then open up MMC.EXE, and then add the local policy snap-in.
Change the rights back to the way they were before you "experimented" with them.
Close MMC, then close the command prompt, and you should be able to log in again!
At least, that is the theory.
Here are 2 URLs for you. The first is the TechNet article I mentioned at first (that really doesn't help you but it is nice to have):
http://support.microsoft.com/support/kb/articles/Q276/5/90.ASP
And here is a link to a page that lists the LOGON.SCR hack in fuller detail:
http://is-it-true.org/nt/atips/atips262.shtml
Go about 2/3 of the way down the page, and you will see it.
Hope this helps.
