RE: runas issue
- From: andy <andy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Aug 2008 23:59:00 -0700
hi,leftfoot,firstly,thx for ur timely response.
Originally,employee user was local admin account(so there were total two
local admin accounts including the built-in admin account
"Administrator"),and a few months ago,we IT personnels have to downgrade them
to Power Users per new company policy,so then only one local built-in admin
accout "Administrator" left in OS.
You mentioned that winxp has some funny "preferences" when it has two local
admin accounts,and the system may get particularly peculant after we take
away the second local admin accout from local Administrators---I am not clear
about this point,could u kindly tell me what are these funny
"preferences",and why only a couple of pcs encounter this issue,not all
pcs?----and there is no any special accounts setting in registry.Thx.
"LeftFoot" wrote:
I'm glad you resolved the issue, even if the solution wasn't particularly.
pleasing to you.
My only guess concerning the odd behavior is to wonder if the first power
user account was at one time an admin account and was changed to power user.
If so, did that leave only the built-in admin user? WinXP has these funny
"preferences" for having two admin accounts, and it seems to get particularly
petulant when it is given a second admin account and then that second admin
account is taken away.
Only other thing I can think of is that the use of the Special Accounts
setting in the registry to hide an admin account at the Welcome screen (I
don't use Welcome screen on any of our systems, but I have seen this done on
other folks' systems.) can leave you able to log on to a hidden account but
NOT able to use it or see it from many parts of the OS, like the user
accounts management applet, for instance. If it's set, I wonder if it also
precludes use of the account with the run as function? I don't know. I might
do a test on a spare system (if I can find one) today to find out.
"andy" wrote:
thx for your reply.
this pc hasn't been joined to domain yet,just in Workgroup,and the user i
need to use to run the command "runas" is local user:Administrator with its
own password.
By now,This case has been resolved ,resolution:creating another local
user(also belongs to local group:Power Uers) for employee on this pc,and then
i can run the command "runas" by lcoal user "Administrator" with password
normally on this new user's context,but i don't know why,i guess this issue
may be caused by user's profile problem.
who can kindly tell me why?
"LeftFoot" wrote:
Sorry for the late reply. Hope you've got this resolved by now. If not, is it
possible that the user name is being used in two different contexts? In other
words, local vs. domain account?
"andy" wrote:
hi,folks,recently,i met a system(winxp Pro sp2) probelm from user's
desktop:in my company,non-it employees are downgraded to Power Users,not
Administrators,so sometimes when we do troubleshooting,we need to run
applications as "administrator" by using "runas",but after I type in the
password and then system prompts that the password I entered is not
right,while I can log on to the operation system by using "administrator"
with the same password ,so i wanna know what issue causes this situation? THX.
- Follow-Ups:
- RE: runas issue
- From: LeftFoot
- RE: runas issue
- References:
- runas issue
- From: andy
- RE: runas issue
- From: LeftFoot
- RE: runas issue
- From: andy
- RE: runas issue
- From: LeftFoot
- runas issue
- Prev by Date: helper.sig folder on bootup
- Next by Date: RE: runas issue
- Previous by thread: RE: runas issue
- Next by thread: RE: runas issue
- Index(es):
Relevant Pages
|