Science fiction and technology writer

HitScan

Mon Dec 3 15:38:33 2001

So I'm testing Win2K on this public workstation to see if it fixes the problems I've been having with my NetGEAR wireless crap, and I see Group policies. Ooooh. The new version of Policy editor. It's really easy to use, has tons of options, etc. I noticed as I was messing with it that it has no place to select a user or a group. How odd. I thought nothing of it since I didn't plan on saving anyhing (In the IIS snap-in you had to save the console settings, at least in NT 4) I notice there's no disk icon. Like a true 'tard I close the edior thinking it'll be useful later when I go over more stuff.

Lo and behold! nothing fucking works! SHIT SHIT SHIT SHIT. So, It appears that most settings take place immediately, and apply to EVERYBODY ON THAT BOX. That's just fucking gravy right there. Looks like I have to bring in my legit Win2K CD now to try and salvage the damn thing, or start all over again from Format C:.

:mad::mad::mad::mad::mad::mad::mad::mad::mad::mad:
:mad::mad::mad::mad::mad::mad::mad::mad::mad::mad:
:mad::mad::mad::mad::mad::mad::mad::mad::mad::mad:
That's pretty close to how I feel anyway.

[size=7]Why the fuck have it apply to all users including the administrator?[/size] Someone sure made my day. Bitches.

OscarWilde

Mon Dec 3 16:48:21 2001

PEBCAK

Bought to you by Battlefront Productions...
:cheesy:

and no i'm not saying PEBCAK to you seriously incase you get teh wrong idea

HitScan

Mon Dec 3 18:47:29 2001

Silliness or not, it does hold some small measure of truth. I don't suppose it would have damaged me in some tangible way to read something, or even anything about it before fuxing around in it, but it's still a SHIT way for a tool to work. INSANE IN SOME MEMBRANE OR SOMETHING LIKE THAT, Y0. I hear if you have a 2K DC with Active Directory it's great. I am yet to possess such a beast. I ph34r the day may not come soon enough to prevent me from having to get really pissed of again because we all know I'm good at that. And bitching, I'm good at that too.

DuffMan

Mon Dec 3 19:11:09 2001

Yes this is PEBCAK, though perhaps MS should take some of the blame for not keeping consistant. Also I think you can recover from this without reformatting.

Imitation Gruel

Mon Dec 3 19:36:46 2001

8K. Again.

This forum r00lz me.

HitScan

Mon Dec 3 19:48:53 2001

Yes this is PEBCAK, though perhaps MS should take some of the blame for not keeping consistant. Also I think you can recover from this without reformatting.

Hell, I hope so. The Resource Kit is of no help. Microsoft.com is of no help, I'm hoping that when I bring in my legit win2K disk tomorrow I'll be able to get in through the recovery console or use the repair reinstall or whatever that's called.

IG: Did you get 8K last time? wouldn't that be ironic, heh.

8K1!

DuffMan

Mon Dec 3 19:50:54 2001

There's a file you can delete that contains all the users and information, and lets you reset the admin password. I forget what it is, but it has SAM in the name somewhere.

Imitation Gruel

Mon Dec 3 20:31:02 2001

IG: Did you get 8K last time? wouldn't that be ironic, heh.

Probably. But whether I started a thread on it or not, I don't remember. I may not even have commented on it. I know I started threads for 9K and 10K though.

HitScan

Mon Dec 3 20:58:05 2001

There's a file you can delete that contains all the users and information, and lets you reset the admin password. I forget what it is, but it has SAM in the name somewhere.

That's what I planned to do, it's just that I have to wait until I have a bootable copy of the CD in my hands. (tomorrow) I'm just pissed and needed to bitch, heh.

DrPizza

Thu Dec 6 04:09:42 2001

I didn't think deleting the SAM would affect policies as they're applied later.

Which policy editor did you set this in? There are several.

HitScan

Thu Dec 6 21:54:48 2001

DrP: I was in gpedit.msc
I know it has nothing to do with the SAM, I've been trying to research things as I go. I got into the recovery console, and deleted the registry.pol files from winnt\system32\grouppolicy\users and ..\machine, but that didn't seem to help a damn thing. The repair installation complained that the C: drive was corrupted and it couldn't continue, but I don't buy that as it boots up just fine. (albeit in a totally locked down state :mad: )

If you've got any better ideas I'd appreciate it.

OSY 1.0 Thread Viewer

Windows 2000 Group policies.