2.3 Environment setup in a Remote Desktop environment
To allow users other than an administrator to log in through the remote session using the remote desktop connection and use JP1/Script, specify the Windows security settings to assign the Create global objects permission to the logon users.
Note the following when using JP1/Script in a Remote Desktop environment:
-
The Script Launcher can only be started in a primary session (console session), and cannot be started in a remote session. The JP1/Script service can be started and stopped in both sessions.
-
Script files registered for automatic startup are started in the primary session irrespective of the startup type.
-
If you want to use the remote session on the client to start the executable file that will be called by the NetExec command, use the Script Launcher service. For details about the Script Launcher service, see 1.5.1 System configuration for executing other programs using the NetExec command, and 2.4.2 Script Launcher service settings.
- Note
-
JP1/Script can be used on the Windows Server Remote Desktop Services. Use RemoteApp to specify which of the JP1/Script programs installed on the Remote Desktop Session Host server will be accessible from users.
Because programs started via RemoteApp are run on a remote server, reserved variables are the same as those on the remote server. Operation commands also run on the remote server. Because the programs started on the remote server and those started on the client are displayed in the same way on the desktop, be careful not to confuse the programs.