Problem with Run Command Task

[KAMIRAN Support 0]

Hi dears ,

We have problem with Run Command task and we can not even run calc.exe.

we use this  :

COMMAND LINE TO RUN  : calc.exe

WORKING DIRECTORY  : c:\windows\system32

But nothing will run on client !

Also I create a simple batch file c:\1.bat and try to run it on my clients but it can not be run by "Run Command "

why ?

I must add this : just the command "Shutdown -r" work find with run command task.

Edited April 30, 2017 by KAMIRAN Support

[bbahes 29]

Have you tried to type entire path to calc.exe in "COMMAND LINE TO RUN:" ?

[MartinK 383]

Problem is that executed command is executed with "Local System" permissions. That is reason why applications like calc.exe are not visible for standard users with desktop environment. It is possible that application is actually running, but is is not accessible by user.

Techcnically content of "Run Command" task is placed into temporary bat file and executed - have tou used "call c:\1.bat" syntax to execute your bat file using this task?

When writing custom commands, you have to be aware of Local System user environment, which is different from standard user/administrator account. Environment variables may differ, user-specific section of windows registry is different. Also filesystem and network permissions may be different, especially when accessing user files. As already mentioned, system user has no access to desktop environment, which may causes failure of application startup.

[bbahes 29]

14 minutes ago, MartinK said:

Problem is that executed command is executed with "Local System" permissions. That is reason why applications like calc.exe are not visible for standard users with desktop environment. It is possible that application is actually running, but is is not accessible by user.

Techcnically content of "Run Command" task is placed into temporary bat file and executed - have tou used "call c:\1.bat" syntax to execute your bat file using this task?

When writing custom commands, you have to be aware of Local System user environment, which is different from standard user/administrator account. Environment variables may differ, user-specific section of windows registry is different. Also filesystem and network permissions may be different, especially when accessing user files. As already mentioned, system user has no access to desktop environment, which may causes failure of application startup.

Do you plan to develop option like "Run As" to specify user under which commands can be executed?

[KAMIRAN Support 0]

10 hours ago, MartinK said:

Problem is that executed command is executed with "Local System" permissions. That is reason why applications like calc.exe are not visible for standard users with desktop environment. It is possible that application is actually running, but is is not accessible by user.

Techcnically content of "Run Command" task is placed into temporary bat file and executed - have tou used "call c:\1.bat" syntax to execute your bat file using this task?

When writing custom commands, you have to be aware of Local System user environment, which is different from standard user/administrator account. Environment variables may differ, user-specific section of windows registry is different. Also filesystem and network permissions may be different, especially when accessing user files. As already mentioned, system user has no access to desktop environment, which may causes failure of application startup.

Yes you are right , I check the prepossesses and it seems that as you said all commands are run by a temp batch file under Local System Account, So we can not see the interface of applications.

is there any way to run the command as a user or administrator ?

[jimwillsher 65]

you could try making your "command to run" something like

runas /user:ABC  "calc.exe"

However it still won't pop up on the user's screen because the command will be running in session 0 (system) whereas the logged-in user will be a different non-zero session number.

 

Jim

[KAMIRAN Support 0]

2 minutes ago, jimwillsher said:

you could try making your "command to run" something like

runas /user:ABC  "calc.exe"

However it still won't pop up on the user's screen because the command will be running in session 0 (system) whereas the logged-in user will be a different non-zero session number.

 

Jim

You are right , Run as command can not be used because it will run in session 0.

[jimwillsher 65]

May I ask what it is you are trying to achieve?

[KAMIRAN Support 0]

3 minutes ago, jimwillsher said:

May I ask what it is you are trying to achieve?

One of our customers want to install some certificates in all clients or install some programs or update patches and we are trying to do this.

They want to solve for example certificates problems in all of 1000 clients , Example : hxxp://support.eset.com/kb6208/

We are testing trying to do this with CMD.

 

[jimwillsher 65]

If you've got 1000 clients then I am guessing they are in a domain, in which case Group Policy or SCCM is probably a better solution.

[KAMIRAN Support 0]

6 minutes ago, jimwillsher said:

If you've got 1000 clients then I am guessing they are in a domain, in which case Group Policy or SCCM is probably a better solution.

Yes but they want to use ESET Agent to install their certificates and we run it with power shell and certutil , And it works find in local system now .