Windows – .vbs won’t execute anything at all

batchvbscriptwindowswindows server 2008

I created short script to run .bat file on background but when i execute .vbs file, it seems like it is not reading my script at all.
.Dos windows pops up and shutdown right away but my batch file is never executed.
(when i execute batch file directly, it works fine, so I'm assuming this script is the problem)

Dim sCurPath
sCurPath = CreateObject("Scripting.FileSystemObject").GetAbsolutePathName(".")
Set WshShell = CreateObject("WScript.Shell")
cmds=WshShell.RUN(sCurPath & "\myrun.bat", 0, True)

This code works on my desktop, windows 7 32 bit but when i try to execute this script on windows server 2008 R2, it won't do anything.
Does anyone know what I need to do to run this .vbs script on windows server?

Best Answer

Most admins disable WSH on Windows Server

Verify the entry values located below are set to 1 (enabled):

User:

HKCU\Software\Microsoft\Windows Script Host\Settings\Enabled

Machine:

HKLM\Software\Microsoft\Windows Script Host\Settings\Enabled

TechNet article

Related Solutions

Windows – Force 64bit WScript to run .vbs

The following code will check if the system is 64Bit and in this case close the script and rerun it forcing the 64Bit Host by calling it directly with the script as parameter.

If fso.FileExists("C:\Windows\SysWOW64\wscript.exe") Then
    If InStr(1, WScript.FullName, "SysWOW64", vbTextCompare) <> 0 Then ' = very basic 64bit check replace if you want a more sophisticated one
        newFullName = Replace(WScript.FullName, "SysWOW64", "Sysnative", 1, -1, vbTextCompare) ' System32 will be replaced by Sysnative. calls to sysnative bypass WoW64 emulation, cscript or wscript stays the same as they were
        newArguments = "" ' all arguments are given to the new script call
        For Each arg In WScript.Arguments
            newArguments = newArguments & arg & " "
        Next
        wso.Run newFullName & " """ & WScript.ScriptFullName & """ " & newArguments, , False
        WScript.Quit ' Close 32Bit scripting host
    End If
End If

This workaround ensures that the script is run in 64Bit no matter who calls it. If you have a situation where you can control the call (e.g. the script is only ever called via a specific link) you can probably just use the basic principle (which is the sysnative file system redirector) directly in your shortcut.

Run .vbs from Task Scheduler. VBS should execute an .exe via shell

You have the task set to run in the context of the Local System account. The System account is not a full-blown interactive user, so not everything will run in that context. You must keep the following considerations in mind when using it for tasks:

Local System presents your computer account credentials to the network (i.e. COMPUTERNAME$), so if filepath is on the a network share, the local computer account must have permissions to it specifically (or the Everyone group).
Local System does not have a user profile (technically it does but there's nothing in it). Anything that refers to a per-user registry setting or filesystem location will likely fail.
Processes running as Local System cannot interact with the user, so if your script pops a dialog, the user won't see it.

Try running your task as a bona-fide local or domain account instead of the System account. You'll of course need to embed the password into the task for that to work.

Best Answer

Related Solutions

Windows – Force 64bit WScript to run .vbs

Run .vbs from Task Scheduler. VBS should execute an .exe via shell

Related Question