Hi,

I have a very specific validation to do on the workstation by VBS before going through the whole MSI copy files and registry. I am using Wise 6.x

I Want the VBS to check many things and if the workstation qualifies, it will set a specific registry key, then using the normal MSI conditions features, I want the MSI to copy some specific file depending on the value that is set earlier by the VBS.

I am setting the registry search using System Search under Target Search in Wise to set a property for the registry am looking. I also try to run the VBS on top on the list, hoping it will run before the registry key is search but with no luck.

Is there a way to first run a VBS, then tell wise to look at a registry key after and take actions according to the value of the registry?

Many thanks for your inputs.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
you don't say what your vbs is supposed to do but see if there's a way to do it with windows installer, vbs scripts can get kinda kludgy. If you need to run a script before system search it's called appsearch, in installexecutesequence table. Usually one of the first things to run. so if appsearch is sequence 400 you'd put your script at 395, let's say. in Wise it's pretty easy to do in the scripting tab which orders the actions but doesn't display sequence numbers.

BTW, you may want to change your handle :-)
good luck!
Answered 12/21/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
The script validates many many corporate stuff and sets a reg to a specific value if wks qualifies, sort of a flag that I want to verify later in normal MSI features actions. The script works and do his job just fine.

In Execute sequence, the VBS is at the top, before AppSearch. The problem is the registry is checked probably before the VBS is called in the sequence. The VBS is currently at sequence 59 so. I would really need the Features/Conditions to be checked after the VBS.

I dont want to use this script to determines if the MSI should run like run conditions or such, the MSI has to do many things but I want it to do more if the workstation is in a specific state.

I hope it is possible. Thanks

P.S.: English is my second language so I dont understand the change handle question :)
Answered 12/21/2010 by: PackagerWannaBe
Orange Senior Belt

Please log in to comment
0
Ok, I have read the following post:

http://itninja.com/question/sysprep-is-removing-dns-config65&mpage=1&key=vbs%2Cproperty쭙

I am figuring it out the best way to achieve what I need and found out the Session.Property I can use in my VBS but I am having a hard time.

For testing and understanding purposes i simply create a test VBS that sets the property using the following: Session.Property("TESTSETPROP") = 1

My property TESTSETPROP is already set to 0 in the table. The Custom action type VBS from embedded code is set very high in the sequence before CostFinalize

The "script" is failing...

What am I missing please?
Answered 12/22/2010 by: PackagerWannaBe
Orange Senior Belt

Please log in to comment
0
I try again with a brand new project and all is working as expected. My current test wsi project was probably corrupted due to all try and fails.

Thks
Answered 12/22/2010 by: PackagerWannaBe
Orange Senior Belt

Please log in to comment
0
Set up WPS to create back-up files. That way, you can easily go back to a working version, even if it was 2, 3, 4 or whatever iterations before.
Answered 12/23/2010 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity