How to stop other administrators from removing administrators password?

korrupt

Posts: 666   +2
Hey, I am an administrator on my pc along with another person. Obviously I want my files to be private, but if the other administrator can simply remove my password, it doesnt work too well.

Is there any way to stop Admins from removing other admin's passwords without losing other admin priviliges?

Regards,

Korrupt
 
Encrypt the folders that you do not want any one to get to. Only the user of the encrypted files has access to it.

(Only if you have XP PRO)
 
It's not too hard to change an admin password in XP Pro outside of Windows too... So doing so probably won't help you much if the other users are familiar with computers.

The only real 'solid' way to prevent other admins changing your password is demoting them to power users and so on...
 
Nodsu, that is not going to happen lol:(

Rick, the other person is as computer illiterate as a broomstick.

Is there no way to edit this in the registry? It's possible to remove the shut down button etc, so IMO it should be possible to remove the "remove password" button....

No more Idea's anyone??

Regards,

Korrupt
 
Have you tried looking in the user and security policies area and see if there is an option to choose who can remove and set passwords and only set yourself.
 
The other person does co-own the pc lol...

How would I get into the user and security policies area

Korrupt
 
For starters, change the name of your account to something that he wouldnt expect to be you.

Furthermore, if you dont use the default administrator account. Try ctrl+alt+del (two times) at the login of windows xp. This will show u a basic login screen, where u can login as the default administrator. If your computer does not have the 'show default administrator' tweak, he cannot see it in useraccounts, and thus not change your password.

Fyi, this info is all out of my skull, and i havent tested it all, so please try and let us know.
 
smore9648 said:
Encrypt the folders that you do not want any one to get to. Only the user of the encrypted files has access to it.

(Only if you have XP PRO)
this is dangerous!
the encryption is tied to the login password; change the password and you've lost control of the encrypted files! really dumb implementation :knock:
search the MS KB articles for details.
 
Hmm.. I experimented with this a little, and it seems to me that it's not possible to both deny changing the password and have it working so that the user can log in.

I removed SYSTEM's "Set Value" permission from the username & password registry key, and when I tried to do anything with the user, the system said the user didn't exist. I guess it needs writing permissions in order to log when something's happened.
 
jobeard said:
this is dangerous!
the encryption is tied to the login password; change the password and you've lost control of the encrypted files! really dumb implementation :knock:
search the MS KB articles for details.

Its not dumb. As long as you know what are doing you will be fine.
But this is not the solution he is looking for.
 
smore9648 said:
Its not dumb. As long as you know what are doing you will be fine.
right, it's far worse; it's unconscionable to implement such a feature
without a warning the user of the consequence of not having a recovery agent.
this 'feaure' is viable only for systems with a domain controller, otherwise it's a virtual trap!

All password guidelines say to change passwords frequently; even as soon as 30 days.
oh what fun -- but hey, you're suppose to know all about the consequences :)
give me a break. :eek: :blackeye:
 
jobeard said:
right, it's far worse; it's unconscionable to implement such a feature
without a warning the user of the consequence of not having a recovery agent.
this 'feaure' is viable only for systems with a domain controller, otherwise it's a virtual trap!

All password guidelines say to change passwords frequently; even as soon as 30 days.
oh what fun -- but hey, you're suppose to know all about the consequences :)
give me a break. :eek: :blackeye:


I think you mean inconceivable not unconscionable.

Why would you have a password policy on a standalone system? :stickout:

I am done talking about this because this is not the solution he is looking for.
 
Back