The WshRemote object allows you to remotely administer computer systems on a computer network. It represents an instance of a WSH script, that is, a script file with one of the following extensions: .wsh, .wsf, .js, .vbs, .jse, .vbe, and so on. An instance of a running script is a process. You can run the process either on the local machine or on a remote machine. If you do not provide a network path, it will run locally. When a WSHRemote object is created (by using the CreateScript() method), the script is copied to the target computer system. Once there, the script does not begin executing immediately; it begins executing only when the WSHRemote method Execute is invoked. Through the WshRemote object interface, your script can manipulate other programs or scripts. Additionally, external applications can also manipulate remote scripts. The WshRemote object works asynchronously over DCOM.

Note

In WSH version 5.6.6626, which ships with Internet Explorer 6 and Windows XP, a remote script is copied to memory in the remote machine and run from there. In later versions of WSH, such as the one provided by Windows Server 2003, a remote script is copied to the temporary directory of the account that accesses the remote machine. The script is run with the security settings for the remote machine and the temporary directory.

The following example demonstrates how the WshRemote object is used to start a remote script.

Code

Visual Basic Script	Copy Code
Dim Controller, RemoteScript Set Controller = WScript.CreateObject("WSHController") Set RemoteScript = Controller.CreateScript("test.js", "remoteserver") RemoteScript.Execute Do While RemoteScript.Status <> 2 WScript.Sleep 100 Loop

JScript	Copy Code
var Controller = WScript.CreateObject("WSHController"); var RemoteScript = Controller.CreateScript("test.js", "remoteserver"); RemoteScript.Execute(); while (RemoteScript.Status != 2) { WScript.Sleep(100); }

Error Property | Status Property

Execute Method | Terminate Method

End Event | Error Event | Start Event

Reference