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> ------------------------------- ' VBScript. RemoteTest.WSF ------------------------------- <package> <job> <script language="VBScript"> set oController = CreateObject("WSHController") set oProcess = oController.CreateScript("c:\wsh5.6\beenhere.wsf", "remmachine") oProcess.Execute While oProcess.Status <> 2 WScript.Sleep 100 WEnd WScript.Echo "Done" </script> </job> </package> ------------------------------- BeenHere.WSF ------------------------------- <package> <job> <script language="VBScript"> set fso = CreateObject("Scripting.FileSystemObject") set fout = fso.CreateTextFile("c:\beenhere.txt", true) fout.WriteLine Now fout.Close </script> </job> </package>