1.7.6 About the Script Launcher service

The Script Launcher service allows you to control NetExec command requests in the logon space in remote sessions. To operate a Remote Desktop Session Host server in a Remote Desktop service environment, you must log on from a remote session. However, because Script Launcher is started in the primary session on the Remote Desktop Session Host server and cannot be started in a remote session, you cannot use Script Launcher to control NetExec command requests in the logon space. However, you can control NetExec command requests in the logon space in such a system configuration by using the Script Launcher service.

The Script Launcher service causes the programs that will be started by the NetExec command with the logon space specified to be started in the logon session of the user specified for the start parameter of this service. Therefore, to use the NetExec command while the Script Launcher service is running, you must stay logged on. You can log on either from the console or from a Remote Desktop service. Normally, you do not have to stay logged on, provided that you are logged on when using the NetExec command. If you log on through the Remote Desktop service, you will stay logged on after disconnecting the session.

The Script Launcher service is registered in the Windows service with the following information:

• General

  • Service name: JP1_SCRIPT_LAUNCHER

  • Display name: JP1/Script Launcher Service

  • Description: None

  • Executable file path: installation-folder\Bin\SPTHLHSV.EXE

  • Startup type: Manual

• Logon

  Local system account

  Only the local system account can be set as the start account for the Script Launcher service.

• Recovery

  • First error: Nothing is performed.

  • Next error: Nothing is performed.

  • Subsequent errors: Nothing is performed.

  • Error count reset: 0

• Dependencies

  • System components on which the service depends: None

  • System components that depend on the service: None

When you use the Script Launcher service, Script Launcher can no longer be started. This means that automatic startup in the logon space is no longer possible. If you want automatic startup in the logon space, use Script Launcher rather than the Script Launcher service.

To use the Script Launcher service:

1. Delete the Script Launcher registration in the startup menu.

2. Use Windows Service Manager to change the properties of the Script Launcher service as shown below. Then, with the Properties dialog box open, start the Script Launcher service.

   On the General page:

   • Startup type: Automatic

   • Start parameters: Logon user name

     For the logon user name, specify the logon space account name used for executing the command requested by the NetExec command.

     Specify the logon user name in user-name, user-name@domain-name, or domain-name\user-name format.

   Do not close the Properties dialog box before the Script Launcher service has started. If you do so, the information set for the start parameters will be lost. If the information is lost, set the information on the General page again, and then start the Script Launcher service.

3. Log on with the logon user name specified for the start parameter.

   Do not log off while you are using the NetExec command. If you have logged on through the Remote Desktop service, you can terminate the Remote Desktop Services client if you stay logged on after disconnecting the session.

To change the logon space account name used for executing the commands requested by the NetExec command, stop the Script Launcher service and then start from step 2.

To specify a user other than an administrator for the logon space account name, assign the Create global objects permission in the Windows security settings in advance.

To Page Top