2.4 Environment setup in a Remote Desktop service environment
You can use JP1/Script on the Windows Server 2008 R2 Remote Desktop service, Windows Server 2012 Remote Desktop service, or Windows Server 2012 R2 Remote Desktop service. To allow users other than an administrator to log in through the remote session and use JP1/Script, specify the Windows security settings to assign the Create global objects permission to the login users. Note the following when using JP1/Script in a Remote Desktop service environment:
-
Script Launcher can be started in the primary session on the Remote Desktop Session Host server, and cannot be started in the remote session on the client. The JP1/Script service can be started and stopped in both sessions.
-
Script files registered for automatic startup are started in the primary session on the Remote Desktop Session Host server 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.7.6 About the Script Launcher service.
- Important note
-
Do not use the Beep command in the remote session on the client. If you do so, an error occurs. For example, 0005 (Access was denied. Recheck file attributes or security) is output.
- Note
-
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.