A
Alan van der Vyver
Hi!
I think I am missing something very basic and expected to be able to
find the information I am looking for easily, but in fact, have not been
able to.
I want our staff to have standard user accounts, because I want them to
be aware of potentially malicious activities they did not initiate and I
want them to pause and consider the consequences when they do initiate
actions that are considered potentially destabilizing. This can be
achieved by supplying an administrator user name and password. However,
I do not want to prevent people from performing these actions and having
an administrator do it for them is totally impractical.
It would seem the obvious solution is to provide an additional
administrative account on the machine that can be used to authorize
these activities, but as soon as people are aware of that account they
will just log on with it. Then the UAC dialogs lose any "security" value
and just become an annoyance, because most people will always just click
"OK" without even reading them.
What I am looking for is an account that can be used for privelege
escalation, but cannot be used to log on locally. I tried removing the
"Log on locally" permission from an administrative account, but then it
can not be used for privilege escalation either.
How is one supposed to accomplish this scenario? Is it actually possible
to create an account that can be used for privilege escalation, but not
for local log on?
regards,
Alan.
I think I am missing something very basic and expected to be able to
find the information I am looking for easily, but in fact, have not been
able to.
I want our staff to have standard user accounts, because I want them to
be aware of potentially malicious activities they did not initiate and I
want them to pause and consider the consequences when they do initiate
actions that are considered potentially destabilizing. This can be
achieved by supplying an administrator user name and password. However,
I do not want to prevent people from performing these actions and having
an administrator do it for them is totally impractical.
It would seem the obvious solution is to provide an additional
administrative account on the machine that can be used to authorize
these activities, but as soon as people are aware of that account they
will just log on with it. Then the UAC dialogs lose any "security" value
and just become an annoyance, because most people will always just click
"OK" without even reading them.
What I am looking for is an account that can be used for privelege
escalation, but cannot be used to log on locally. I tried removing the
"Log on locally" permission from an administrative account, but then it
can not be used for privilege escalation either.
How is one supposed to accomplish this scenario? Is it actually possible
to create an account that can be used for privilege escalation, but not
for local log on?
regards,
Alan.