• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

changing admin password in Win2k?

smp

Diamond Member
I would like to know how to change the admin password in win2k, I need to change it.
thanks..
 
If you have admin access already just press cntrl-alt-del and then hit change password. If you are not an admin or have forgotten the password things get more complicated...
 
Two ways

Logged in as Admin press CTRL + ALT + DEL. Then go Change Password

or

Start > Settings > Control Panel > Users and Passwords then select the Administrator account and click the Set Password box.
 
Zoltarc,

I believe your second suggestion would only work if you were logged into a different admin account. Or is there some way to alter this behavior in local (or domain) policies? On the systems I've seen the "Set Password" button is not available to you for changing the password under the currently logged in account.

Regards,
Jim
 
On my computer when I go to the Users and Passwords control panel a dialog box tells me that I can only access this when I type in the name and password of an admin (dunno if the Run as service needs to be enabled though...).

Oda
 
There is a very useful tool in win2k. Just right click on my computer and click manage. You can do anything u want from that panel (if u have admin access)
 
Well, heck yes! I knew I was forgetting something! Just use Manage, right-click on the user and choose "Set Password" from the context menu! (Even works on the currently logged in account.)

Sigh. I'll just never get used to all of these newfangled GUIs. 😛
 
Thanks all. The thing I was trying before (duh, forgot about ctrl, alt, del 😱) was the user profiles, and I was logged in as root so I couldn't change it from there. The manager seems pretty cool.

I have more though.... Say for example that you enable a user account for your sister, will she be able to burn CD's and stuff with that? If not, how do you set the permissions yourself? I mean, instead of using 2K's built in permission schemes.. if I wanted to change a couple things for the 'user' account, like to enable something? How would that be done? Can it be done?
 
There's a lot of trouble over that very issue these days. It's caused partially, I think, by the fact that CD writing software kind of occupies a strange zone of influence over the system. It behaves kind of like a kernel mode driver and kind of like a user mode application. That's an uneasy mix, and probably explains a lot of the bad behavior people have seen from these apps under W2K. (I have never seen ANY kind of software other than CD writing software manage to lock up a W2K machine. Only drivers are supposed to be able to do that. And you're supposed to be able to get around that problem by using only WDM-adherrent drivers on your system.)

The way I have dealt with this using the Adaptec/ROXIO Easy CD Creator 4.0x and DirectCD 3.0x software is to create the user account as an admin user and to apply special restrictions to it to prevent that user from going where I don't want that user to go. As an added security buffer, I create a regular user account, then use the Run As feature of W2K so that the user accesses the CD writing function (just that one function) as that limited admin user. This is easier to do as a domain admin, I think, than it is to do as local admin on a standalone. Moving from the other direction by creating an account that is member of a lower level group and trying to increase its access/permissions just doesn't work. Right now, most (all?) of the CD writing software I've seen essentially requires admin permissions to work. You can't get there from User (or even from Power User). That's not really the way NT / W2K permissions work. (At least that's how it appears to me. I'm a relatively recent convert to the Microsoft camp, so I could certainly be mistaken.)

Mostly, I think we have to hope that the purveyors of this sort of software get their you-know-what together and release updates that get us past this rather thorny problem.

Hope you find a solution. And, if it's a neat one, that you post it for the rest of us!

Regards,
Jim
 
Back
Top