S
Spyro Polymiadis
Hi there,
I am playing around with the "Run As" option for allowing my "limited
users" access to applications that require privileges of an admin.
Instead of giving them the actual Administrator password, ive created
another admin "BF2" user so they can use those credentials.
What I am trying to do is: Restrict the local user down to a couple
applications that he can use the "run as" command on as the "BF2" user,
but I can still be able to use the run as option on all applications as
the "administrator" user (for when I need to run admin programs)
Ill give you an example...
Local User (with limited privs) called JoeBlog
Administrator User used for running programs called BF2
And local administrator is Administrator.
Ok, so JoeBlog wants to play Battlefield2 (for instance) but punkbuster
requires the program be run with admin provileges, so Ive created a BF2
user and added it to the administrator group, and they can now run
BattleField 2 as the BF2 user and all is good.
I have disabled the ability to log in (to the desktop) on the BF2 user,
but I would like to restrict the "Run As BF2 user" down to just the
Battlefield executable and nothing else. But still be able to "Run As
Administrator" on everything else (for my management).
Does anyone know of a way to lock this down? Would it be something that
needs to be set on JoeBlog's account or the BF2 account?
I can disable the Run As command all together but then I lose the option
to run Battlefield as an admin user...
Cheers
Spyro
I am playing around with the "Run As" option for allowing my "limited
users" access to applications that require privileges of an admin.
Instead of giving them the actual Administrator password, ive created
another admin "BF2" user so they can use those credentials.
What I am trying to do is: Restrict the local user down to a couple
applications that he can use the "run as" command on as the "BF2" user,
but I can still be able to use the run as option on all applications as
the "administrator" user (for when I need to run admin programs)
Ill give you an example...
Local User (with limited privs) called JoeBlog
Administrator User used for running programs called BF2
And local administrator is Administrator.
Ok, so JoeBlog wants to play Battlefield2 (for instance) but punkbuster
requires the program be run with admin provileges, so Ive created a BF2
user and added it to the administrator group, and they can now run
BattleField 2 as the BF2 user and all is good.
I have disabled the ability to log in (to the desktop) on the BF2 user,
but I would like to restrict the "Run As BF2 user" down to just the
Battlefield executable and nothing else. But still be able to "Run As
Administrator" on everything else (for my management).
Does anyone know of a way to lock this down? Would it be something that
needs to be set on JoeBlog's account or the BF2 account?
I can disable the Run As command all together but then I lose the option
to run Battlefield as an admin user...
Cheers
Spyro