We want to run the vbscript through BigFix

1

Hi All,

I am struggling to deploy the vbscript through BigFix which is keep in the folder. The folder consist of supporting file and vbscript.

However we are getting exit code 0 but I think vbscript is not getting called.

When we run the script manually working fine ie through admin command prompt. Below is the bigfix script and output

prefetch 30f4b3968b2f809452f2adccadabb04d996ece78 sha1:30f4b3968b2f809452f2adccadabb04d996ece78 size:536561 http://XXXXXXXXXXXx:52311/Uploads/30f4b3968b2f809452f2adccadabb04d996ece78/RizenNetworkTool.tmp sha256:89f9b0c5e4284af1eedb578d81b43080183e0692e8fccaf6d4e7577e10678ecc
extract 30f4b3968b2f809452f2adccadabb04d996ece78 “C:\Rizen Network Tool”

wait cscript.exe “C:\Rizen Network Tool\Push.vbe”

prefetch 30f4b3968b2f809452f2adccadabb04d996ece78 sha1:30f4b3968b2f809452f2adccadabb04d996ece78 size:536561 http://YXXXXXXXXXXXX:52311/Uploads/30f4b3968b2f809452f2adccadabb04d996ece78/RizenNetworkTool.tmp sha256:89f9b0c5e4284af1eedb578d81b43080183e0692e8fccaf6d4e7577e10678ecc
extract 30f4b3968b2f809452f2adccadabb04d996ece78 “C:\Rizen Network Tool”

wait cmd.exe /c cscript.exe “C:\Rizen Network Tool\Push.vbe”

action uses wow64 redirection false
wait cmd.exe /c cscript.exe “C:\Rizen Network Tool\Push.vbe”

action uses wow64 redirection false
wait cscript.exe “C:\Rizen Network Tool\Push.vbe”

action uses wow64 redirection false
wait “{pathname of system folder}\cscript.exe” “{((pathname of client folder of current site} & “C:\Rizen Network Tool\Push.vbe”)}”

I tried all above mention script.

All come with exit code 0

…

Any help or suggestion on this.

2

Firstly, .vbe is encoded vbscript, so are you sure about what it does?

In addition to the usual security concerns of running encoded scripts, does this need to be run in a user context? Bigfix actions run under the SYSTEM context by default.

If running as the current user is needed see Tip - Action Override User settings for advice.

It is a long, long time since I have done anything with VBScript, but the following should be a good template

action uses wow64 redirection false

override wait
hidden=true
wait "{pathname of file "cscript.exe" of native system folder}" //B //NoLogo "C:\Rizen Network Tool\Push.vbe"
3

Exit 0 typically means the command complete with no errors, so in the case of calling a script, it would indicate the script executed and did not trap an error. It could be that the script is running but is expecting a user context as @trn mentions so it not running as expected…to know that though you’d need to know the script is doing but as its VBS encoded, you’d have to decode it in order to see what its doing.

Are you running directly form the fixlet? Have you tried using the debugger and see if it behaves any differently (the debugger runs as the user where as the fixlet runs as SYSTEM). I tip I used for calling other scripts is to invoke the command in the debugger using CMD.exe /k which keep the CMD window open allow you to see any messages the are echoed back to the CMD process.

image
image832×359 17.5 KB