Remote WSH
Remote WSH allows a local Windows script to be executed on another computer through the `WshController` and `WshRemote` objects.
since 0.9.8.11
Purpose
Show registry keys (1)
HKLM\SOFTWARE\Microsoft\Windows Script Host\Settings\Remote
Remote WSH allows a local Windows script to be executed on another computer through the WshController and WshRemote objects. It uses DCOM to transfer and control the script, which is then run by Windows Script Host on the target computer.
The catalog entry is intended to prevent this remote execution at the computer level. However, the available Microsoft documentation does not establish that the specific combination of the REG_DWORD type and a value of 0 has this effect.
Notes
Security
Successfully disabling Remote WSH removes one DCOM-based path for remote script execution. Microsoft documents that Remote WSH already requires the initiating user to be a member of the target computer's local Administrators group.
This setting does not disable local Windows Script Host execution or other remote-management mechanisms such as Windows PowerShell remoting, WMI, Remote Desktop, or unrelated DCOM applications.
Possible side effects
If Remote WSH is effectively disabled, legacy management or automation solutions that use WshController or WshRemote to start scripts on this computer can no longer perform those operations.
Notes
The available Microsoft documentation describes Remote as a string entry and specifies the value 1 for enabling Remote WSH. It does not confirm REG_DWORD as a supported type or document the intended behavior of REG_DWORD 0 at the specified HKLM path. It therefore cannot be stated reliably that the DWORD value written by Setup Foundry disables Remote WSH.
Remote WSH is a legacy technology introduced with Windows Script Host 5.6. The detailed Microsoft source for this functionality is consequently historical documentation.
Microsoft documentation
Microsoft Learn: Windows Script Host 5.6 Boasts Windows XP Integration, Security, New Object Model