+ cscript isn’t defined as the default scripting engine
+ it requires an admin to change the default scripting engine because it can’t be set at the user context level
Why aren’t servers cscript by default??? This is a quick and easy change when building servers… Either
1. Run cscript //h:cscript
or
2. Change the value default value of HKCR\vbsfile\shell to “Open2”
or
3. Just use Perl 🙂
Yeah… Add that to the list of gripes…
+ No perl installed…
😉
Who needs perl on a windows server. IronPython and Powershell rule have access to any job needed in a Windows Environment. Lets move into the 21st Century.
No IronPython, in fact I have never seen IronPython on any of my customer’s servers. PowerShell I have seen, but only on test servers. This customer I don’t even think has it on test servers though. Even if it were on there, I would prefer perl.
Perl has no place in Windows management and you will soon learn its life span is done. You will have no choice but to learn Powershell, be irrelevant, or retire.
LOL
Brandon said:
“Perl has no place in Windows management and you will soon learn its life span is done.”
So, what do you propose for cross-platform scripting? Linux sure ain’t going away, and it doesn’t really exist in the *nix world, notwithstanding pash/mono/moonlight…
You can set cscript as the default by shift-right-clicking on a .vbs, open with, and browse for cscript.exe, and check always open with. OR
Change Application to cscript.exe in
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.vbs
Very cool Scott, that does work… It performs the override in HKCU so I can do it. Awesome. Here is a generic command that should work for folks to do that
reg add hkcu\software\microsoft\windows\currentversion\explorer\fileexts\.vbs /v Application /d cscript.exe
and to remove
reg delete hkcu\software\microsoft\windows\currentversion\explorer\fileexts\.vbs /v Application /f