Source : http://msdn.microsoft.com/library/default.asp?url=/library/en-us/script56/html/wstsksetupofremotewsh.asp
Setting up Remote WSH
Remote WSH, which is a new technology included in WSH 5.6, provides the ability to run a script on a remote machine or machines. With Remote WSH, the script is physically copied from the local machine to the remote machine before executing. In order to enable Remote WSH functionality, you must first set up the remote machine with the proper security settings. The steps below perform the tasks that enable Remote WSH.
Note   Both the remote and local machines must be running Windows NT 4 SP3 or greater in order to use Remote WSH.
To enable a machine to run remote scripts 

Install WSH V5.6 on the machine. If you are using Windows XP or have installed Internet Explorer 6 or greater, WSH 5.6 has already been installed. 
Note   WSH 5.6 is available for download from the Web at http://msdn.microsoft.com/scripting
Add yourself to the remote machine's Local Administrators group. 
To enable Remote WSH, use the System Policy Editor (Poledit.exe) on the server. 
Note   An administrator who wants to enable Remote WSH should add a subkey entry named Remote of type REG_SZ to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings. To enable Remote WSH, set the value of Remote to 1; to disable Remote WSH, set the value to 0. If the value of the Remote value is not set, by default Remote WSH is disabled.
Note   For more information on the System Policy Editor, see the Microsoft Windows online help system.
WSH is enabled on the machine. To test it, see Running Scripts Remotely. 
See Also
Security and Windows Script Host | Running Scripts Remotely


WSH 5.6 can run scripts that reside on remote systems. The following scripts demonstrate this capability. These scripts make the assumption that the files are located on a local machine directory called "c:\wsh5.6"; change the local path and the remote machine name as necessary.
After initially running RemoteTest.WSF on the local machine, there may be a small pause as DCOM verifies your identity. After you see the "Done" message, a file named "c:\beenhere.txt" on the remote machine indicates the time that you executed the command (from the remote computer's clock).

// JScript.
RemoteTest.WSF
------------------------------- 
<package>
<job>
<script language="JScript">
var oController = new ActiveXObject("WSHController");
var oProcess = oController.CreateScript("c:\\wsh5.6\\beenhere.wsf", "remmachine");
oProcess.Execute();
while (oProcess.Status != 2) WScript.Sleep(100);
WScript.Echo("Done"); 
</script>
</job>
</package>
------------------------------- 
BeenHere.WSF
------------------------------- 
<package>
<job>
<script language="JScript">
var fso = new ActiveXObject("Scripting.FileSystemObject");
var fout = fso.CreateTextFile("c:\\beenhere.txt", true);
fout.WriteLine(new Date);
fout.Close();
</script>
</job>
</package>