- runas bug?
- Posted by jg on March 4th, 2006
regedit does not take on proper impersonation when administrator uses
runas /user:somePowerUser cmd.exe
then from the cmd prompt for somePowerUser windows
regedit
proof: the current is not for somePowerUser but the administrator's
Granted that values that can not be changed by somePowerUser, nonetheless, I
still don't think it is correct behaviour
why do I want to do regedit from somePowerUser instead of administrator? I
need to confirm the SID for the somePowerUser before I modify them
- Posted by Jim Hill on March 5th, 2006
jg wrote:
No biggie. Every user's registry is under HKEY_USERS. To find the
right one (relatively) easily, fire up regedit, start from that key,
and find "Shell Folders" in just the keys. You'll see the home
directories on the right; when you see the right name, you're in the
right part of the registry.
hth,
Jim
- RUNAS Command (Security & Administration) by Luiz
- runas - access denied (Security & Administration) by Martin Miethe
- not getting the RunAs option (Microsoft Windows) by Spin
- not getting the RunAs option (Basics) by Spin
- Not Allowed to runas (Basics) by bxb7668

