With this month’s service release for PrimalScript 2009 (build 631) we included an updated version of the RSEE (Remote Script Execution Engine) service.
The new version is now available in 32 and 64 bit and can execute PowerShell scripts remotely.
It is important to note that you cannot mix the new PrimalScript build with older RSEE service versions. The new version of the service is, however, backwards compatible with prior versions of PrimalScript. Please note that older versions of PrimalScript cannot remotely execute PowerShell even with the new service.
Why are we using this service rather than supporting PowerShell remoting? It’s pretty simple to set up PowerShell remoting in a domain environment and remotely execute scripts from the shell. In a workgroup environment, this setup is reportedly a bit more tricky and we actually have a machine or two here at SAPIEN HQ where it didn’t work at all. Since many of our customers already use RSEE to remotely execute VBScript and JScript files it was an easy decision to do this first. Needless to say, we will use and support PowerShell remoting as well as soon as we can get to it.
The user interface for RSEE also has changed a little bit. Originally RSEE was devised to execute a given script against a list of remote machines. You can load any list, check or uncheck the desired targets and fire off your script to run there. Output is sent back to Primalscript and displayed in the output window, organized by target computer.
Recognizing that quite often you also need to send a script to just one machine, the script menu now allows a choice of “Single Target” or “Multiple Targets”.
The single target dialog has a combo box with history function to make repeated use a little bit more convenient.
How do I install RSEE?
Looking in the PrimalScript installation folder you can see a “Redistributables” folder that contains the MSI files for RSEE, typically:
C:\Program Files\SAPIEN Technologies, Inc\PrimalScript 2009\Redistributables\RSEE
Use the 32 or 64 bit version on your remote machines. The MSI will list Windows Firewall exceptions automatically and start the service. You do not need to install PrimalScript itself on the remote computer. Everything is geared to make this as easy as possible to use in your environment.
What about permissions and execution policy?
Any script you submit via RSEE is transmitted encrypted via TCIP to the remote machine. The script will run under the security context of the service and is subject to all policies and restrictions of the remote machine. You can specify alternate credentials when submitting your script, which have to be valid on the remote machine and do not need to apply to your local computer. If the PowerShell execution policy on the remote computer is set to “Restricted”, RSEE will not run any PowerShell scripts. Any other execution policy setting will work.
What about firewalls?
The RSEE installer automatically enters an exception for it’s executable to the Windows Firewall settings. If you use a different firewall product, you may have to do that manually. The default tcp/ip ports used are 9987 and 9988. You can change those ports if need; please consult the PrimalScript 2009 manual for further information.
How do I get the output of the script?
The output of a remotely executed script shows up in PrimalScript’s output window just like any other script you run from within PrimalScript.
Do you have any other questions regarding RSEE? Feel free to add them here or post in our support forum at support.sapien.com