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

1. Install WSH V5.6 on the machine. If you are using Windows 2001 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

2. Add yourself to the remote machine's Local Administrators group.
3. To enable Remote WSH, use Poledit.exe on the server.

   Note   An administrator who wants to enable Remote WSH must either acquire the Windows 2000 resource kit, or use http://msdn.microsoft.com/scripting to acquire the necessary windowsscript.adm file that contains the WSH settings. The windowsscript.adm file must be copied to the server that sets the gapplicabel group's policies. Although it is not necessary to copy the file to the server's \WINNT\INF directory, this is nonetheless where the default adm files are located.

   Note   For more information on Poledit.exe, see the Poledit.exe's online help system.

4. WSH should now be enabled on the machine. To test it, see Running Scripts Remotely.

See Also

Security and Windows Script Host | Running Scripts Remotely