While work on complete and illustrated instructions on how to configure OnScript Network Edition to access remote machines is still underway, here is a short description on what is required and how to get it working.
As OnScript runs there are actually three processes involved:
OSEditor.exe - the OnScript Editor, which is the UI and always runs as the interactive user.
OSApp.exe (OnScript Application) and OSAppMgr.exe (OnScript Application Manager), collectively know as the OnScript Application Server. These two DCOM servers implement remotable actions such as script execution and file system access.
When working with scripts on the local machine these three processes will normally all be configured to run as the interactive user – this is the default configuration for DCOM servers and works just fine.
But when OnScript Network Edition is used to access a remote machine it connects to the OnScript Application Server DCOM servers of that remote machine. This will fail unless permissions and the identity of remote processes are configured correctly.
The simplest way to explain the required configuration is by using a group account whose members will have control of the OnScript Application Server and a user account that the two processes will run under (similar to a service account). For illustration purpuses let’s call them OnScriptApplicationUsers and OnScriptApplicationIdentity, respectively.
Here are the critical steps to get remote access working:
- Make sure both accounts are valid on the remote machine (the can be local or domain accounts, choose what is appropriate).
- Add any users or groups that should have access to the OnScript Application Server as members of OnScriptApplicationUsers.
- Make OnScriptApplicationIdentity a member of OnScriptApplicationUsers. This is essential because otherwise the processes will not be able to interact and some operations will fail.
- Give OnScriptApplicationIdentity any permissions your scripts require to run correctly. This is the account they will run under.
- Run DCOMCNFG and locate the two DCOM servers OnScript.AppManager and OnScript.Application. For each of them do the following:
- On the Security tab select “Customize” (on XP or 2003) or “Use custom launch permissions” (on 2000 and NT) and click Edit. Add the OnScriptApplicationUsers group and make sure it is set to “Allow launch”.
- In the Identity tab change the option from “Interactive user” to “This user” and specify the OnScriptApplicationIdentity account and password.
Now run OnScript Editor and choose File / Add computer … and specify the remote machine by NETBIOS name, DNS name or IP address and ... experiment.
If you run into problems then Event Viewer is your first aid (both machines).
XLnow - the makers of OnScript