Silent switch issue
Hello All,
I have a small issue in one of my package. we have a launch condition in our template(wsi) to validate the lab pc or a normal pc. we have a appsearch for the registry key HKEY_LOCAL_MACHINE\SOFTWARE\BlaBla\GroupPolicies\1\IsWkstLaboratory with the value 1 and a launch condition for it.
if we install any application with the switch QR it is fine(which is our standard) but if we deviate from it say if we use QB it does not recognise the launch condition and proceeds with the install. i am not understanding what might be the reason. would anyone of us help me in this?
Many Thanks.
I have a small issue in one of my package. we have a launch condition in our template(wsi) to validate the lab pc or a normal pc. we have a appsearch for the registry key HKEY_LOCAL_MACHINE\SOFTWARE\BlaBla\GroupPolicies\1\IsWkstLaboratory with the value 1 and a launch condition for it.
if we install any application with the switch QR it is fine(which is our standard) but if we deviate from it say if we use QB it does not recognise the launch condition and proceeds with the install. i am not understanding what might be the reason. would anyone of us help me in this?
Many Thanks.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
rakesh.kumar
13 years ago
Check wheter Appsearch and LaunchCondition are sequenced in InstallExecuteSequence table and AppSearch is sequenced before LaunchCondition action
Posted by:
anonymous_9363
13 years ago
If the sequence was out, or the action wasn't present, it would work in neither mode, since both modes run the Execute sequence, which is why I don't think the OP is quite right about which scenarios cause the problem. The only difference between QR and QB is that, if the user cancels a QR install, a modal dialog is displayed at the end, whereas the installation just ends if QB was specified. Both scenarios runs the ExecuteImmediate sequence and so should be identical.
What I *think* the OP is seeing is what happens when a non-silent install is run, i.e. with no Qx argument. If that's the case, then yes, I'd say that either AppSearch or LaunchCondition is missing, or the order of execution is wrong, in whichever mode - UserInterface or ExecuteImmediate, is causing the problem.
What I *think* the OP is seeing is what happens when a non-silent install is run, i.e. with no Qx argument. If that's the case, then yes, I'd say that either AppSearch or LaunchCondition is missing, or the order of execution is wrong, in whichever mode - UserInterface or ExecuteImmediate, is causing the problem.
Posted by:
anitha_accen
13 years ago
Hi Rakesh,
Yes appsearch and launch condition is sequenced in the installexecutesequence table and appsearch is ahead of launch condition.
Thanks.
Yes appsearch and launch condition is sequenced in the installexecutesequence table and appsearch is ahead of launch condition.
Thanks.
Posted by:
pjgeutjens
13 years ago
Ani,
I'd suggest running a /QB and /QR installation with extensive logging and putting the 2 logs side by side. Try to compare the installation flows in both cases, concentrating on the AppSearch and LaunchConditions Actions. also look to make sure the actions aren't conditioned (you never know)...
rgds,
PJ
I'd suggest running a /QB and /QR installation with extensive logging and putting the 2 logs side by side. Try to compare the installation flows in both cases, concentrating on the AppSearch and LaunchConditions Actions. also look to make sure the actions aren't conditioned (you never know)...
rgds,
PJ
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.