5 replies to this topic

[cross]

I need to create a CA that runs a vbscript.  I have to pass parameters to the Vbscript, therefore I cannot just have a CA that calls this script.  I want to try and stream this script into the SUPPORTDIR and call launchappandwait, passing in the parameters. This doesn't work.  Can anyone explain SUPPORTDIR to me. There doesn't seems to be much documentation.

[Leigh Ravenhall]

Instead of passing parameters, is it possible to call your VBScript, then at the start of the script retrieve the values of some properties that you wanted to pass in.

All it takes is:
VBVar = Session.Property(PropertyName)

[cross]

I'm trying this however Session.Property is causing an error when the script is run.  

[Leigh Ravenhall]

What error is it returning?

Can you post the code that it is failing on?

[SteveP]

You may want to try calling your custom action as a Type 34 (base type ... add in the flag values for deferred action, etc.).  Use the location of WScript.exe as the Source (generally, you can use [SystemFolder] in NT and 2000 ... not sure for Win 9x).  Then, in the Target field, use WScript.exe //B <path and location to your VBS script> <Arg1> <Arg2> ... etc.

Then, in the first part of your script, use something like this:

Dim oArgs
Set oArgs = WScript.Arguments

With the way I wrote the command line, <Arg1> would be oArgs(0), etc.

This is a ton easier than trying to get property values from within the script, and you can use property values in the command line.  The limitation would be that the command line is limited to 255 characters, and you have to double quote entries that contain white space.

Hope that helps.