S
satv73
Hi,
I wanted to analyze what kind of privelege is need to launch a
specific process on a remote machine which is under the same [using
WMI].
I created a test user and granted all WMI/DCOM side accesses. Now I am
able to perform all the standard WMI calls like remote process lookup
et.c using the test user. But when I tried to launch the specific
process using "Win32_Process" create with the test user, it gives error
[=2]. I kept on adding previleges one by one from the Local security
policy on the client machine for the test user and at some point, I
ended up giving more than what Administrator has [like Part of
operating system], still the same error was occuring. But it works, if
I simply add the test user under "Administrators" group.
This made me to think whether if somewhere, the WMI Win32_Process
security is explictly looking for whether the test user is a part of
"Administrators" group, then this previlege experiment will not help.
Anybody can comment on this?
Thanks in advance
Sathish
I wanted to analyze what kind of privelege is need to launch a
specific process on a remote machine which is under the same [using
WMI].
I created a test user and granted all WMI/DCOM side accesses. Now I am
able to perform all the standard WMI calls like remote process lookup
et.c using the test user. But when I tried to launch the specific
process using "Win32_Process" create with the test user, it gives error
[=2]. I kept on adding previleges one by one from the Local security
policy on the client machine for the test user and at some point, I
ended up giving more than what Administrator has [like Part of
operating system], still the same error was occuring. But it works, if
I simply add the test user under "Administrators" group.
This made me to think whether if somewhere, the WMI Win32_Process
security is explictly looking for whether the test user is a part of
"Administrators" group, then this previlege experiment will not help.
Anybody can comment on this?
Thanks in advance
Sathish