1.5.1 System configuration for executing other programs using the NetExec command

This section describes the system configuration used to execute other programs using the NetExec command. For details on the NetExec command, see 8.10.2 NetExec (call an executable file on the local PC or remote PC).

You must choose whether the NetExec command executes programs in the service space, or the logon space.

Executing programs in the service space:

Executing programs from the service makes it possible to execute programs regardless of user logon status. However, programs that require interactive manipulation involving the use of a GUI or other user interface cannot be executed.
Executing programs in the logon space:

As programs are executed in logged on user sessions, the user needs to be logged on to execute the program. This allows programs that require interactive manipulation involving the use of a GUI or other user interface to be executed.

Organization of this subsection

(1) System configuration for using the NetExec command (for executing programs in the service space)
(2) System configuration for using the NetExec command (for executing programs in the logon space)
(3) About the Script Launcher and Script Launcher service

(1) System configuration for using the NetExec command (for executing programs in the service space)

The system configuration for using the NetExec command (for executing programs in the service space) is shown in the figure below. The JP1/Script service must be running on the called computer.

Figure 1‒2: System configuration for using the NetExec command (for executing programs in the service space)

To Page Top

(2) System configuration for using the NetExec command (for executing programs in the logon space)

The system configuration for using the NetExec command (for executing programs in the logon space) is shown in the figure below. The Script Launcher or Script Launcher service must be running on the called computer. For details on the Script Launcher service, see 2.4.2 Script Launcher service settings.

Figure 1‒3: System configuration for using the NetExec command (for executing programs in the logon space)

To Page Top

(3) About the Script Launcher and Script Launcher service

The Script Launcher or Script Launcher service must be running to specify the logon space when executing the NetExec command. (The Script Launcher and Script Launcher service cannot be started at the same time.)

For details on differences in specifications for the Script Launcher and Script Launcher service, see the following table.

Table 1‒3: Differences in specifications between the Script Launcher and Script Launcher service
No.	Function	Script Launcher	Script Launcher service
1	Automatic start^#1	Y	N
2	NetExec logon space execution	Y	Y
3	NetExec logon space execution user^#2	The first user to log on	User specified by the service start parameter Or, Logged on user with high priority in the NetExec logon user settings file
4	Use on a Remote Desktop	N	Y
5	NetExec command restriction policy file^#3	N	Y

Legend:

Y: Can be used

N: Cannot be used

#1

For details on the automatic start function, see 3.1.14 Setting a script to start automatically.

#2

The user must be logged on to use the NetExec command.

#3

For details on the NetExec command restriction policy file, see 2.4.3 Setting users permitted to remotely execute the NetExec command.

As the Script Launcher cannot be started in a Remote Desktop environment, the Script Launcher cannot be used to control NetExec command requests in the logon space. As such, use the Script Launcher service when operating in a Remote Desktop environment.

The automatic start function cannot be used in the logon space when operating using the Script Launcher service. If you need to use the automatic start function in the logon space, use the Script Launcher instead of the Script Launcher service.

To Page Top