Just a technical note of interest. If you want to change the File Association for *.vbs *.js, etc. to avert unintentional launching of "Questionable" scripts, you can do this and still utilize scripts in your local intranet with safety.
One of the command line switches for the Scripting Engine is /E:Engine where "Engine" specifies the Script engine to use. For Example the command "Wscript.exe /E:VBScript MyScript.VBS" would specify the "VBScript" engine would be used to launch the MyScript.VBS file. But, since you are specifying the "Engine" you can also name the file with "Any" legal extension that suites you, for example "MyScript.ZBS" and it will execute properly when used in the context shown above but WILL NOT execute when clicked or double clicked. Further, If you want to keep the code in your scripts from prying eyes, you can download Microsoft Script Encoder (MSE) from (Watch for LineWrap): http://msdn.microsoft.com/downloads/sample.asp?url=/msdn-files/027/001/789/m sdncompositedoc.xml&frame=true
