/build/static/layout/Breadcrumb_cap_w.png

Hide Command prompt window

I am running a vbscript through msi using the Action: Execute commandline from path.where property is set as [WindowsFolder]system32\cscript.exe and vbs file in commandline.(that vbfile is present in the machine where package is goin to install).But problem is with silent installation.On installing package ,the cmd window will pop up and go.Can any one suggest a method to hide this cmd window popping up during package installtion?

0 Comments   [ + ] Show comments

Answers (8)

Posted by: anonymous_9363 13 years ago
Red Belt
0
Use 'START /B CSCRIPT [blah, blah, blah...]'.

Make sure that your script has thorough logging since, with no command window, it will be impossible to track failures.
Posted by: mekaywe 13 years ago
Brown Belt
0
did you try with wscript.exe ?
Posted by: Anjana 13 years ago
Senior Yellow Belt
0
Thanks for the reply.
Let me try with Start /B...
But I am not allowed to use wscript in this case.
Posted by: Anjana 13 years ago
Senior Yellow Belt
0
But Start /B is giving error in MSI. :-(
Posted by: anonymous_9363 13 years ago
Red Belt
0
We can see "the error" from here, of course...
Posted by: spartacus 13 years ago
Black Belt
0
ORIGINAL: Anjana

I am running a vbscript through msi using the Action: Execute commandline from path.where property is set as [WindowsFolder]system32\cscript.exe and vbs file in commandline.(that vbfile is present in the machine where package is goin to install).But problem is with silent installation.On installing package ,the cmd window will pop up and go.Can any one suggest a method to hide this cmd window popping up during package installtion?


If the VBS file is consistent across all machines to which you plan to deploy the package, why not import the contents of the script and construct a Type 6 or type 38 custom action ? That way you eliminate the need for cscript.exe and the command window. There are a few caveats to this depending on the contents of your script, for example any code which uses the WScript object (e.g. wscript.sleep) will not work in a custom action.

Alternatively You might want to try out the method using wixca.dll, which I posted here

Spartacus
Posted by: mazessj 13 years ago
Blue Belt
0
I suggest revising the script to work in WScript instead of CScript, since CScript is specifically intended to run in a console window (hence its name).
Posted by: angrymidget 10 years ago
White Belt
0

When editing a script, you can click the "View raw XML editor" link under the Scheduling section. If you change the type=policy field to type=hidden, the entire script will run in silent mode.

<config name="Blah Blah script that does whatever" type="hidden" id="106" version="1393522756" description="Whatever this script does.">

If you need to export the script as a resource to another Org on the KACE appliance, you will have to change it back from hidden to policy as it will not show up in the list of available resources.

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ