Ipass Client
Hello I am trying to install the Iplass client with a transform and trying to hide the dialogue boxes with silent switches but it does not work ... could someone help me plz...
Thanks
Thanks
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Teitan
13 years ago
Posted by:
andi.sharma
13 years ago
Thank you for the response...
This is what has happened.... when trying to make a transform on the vendor supplied msi I get a error message saying ' This package does not support hidden dialogues' ... well i went ahead and made a transform anyways .... which infact does work to install the msi... Now the issue arises on making it install silently.... Even with /qb or /qn switches it does not install silently... UI intervention is prompted for the installation....
This is what has happened.... when trying to make a transform on the vendor supplied msi I get a error message saying ' This package does not support hidden dialogues' ... well i went ahead and made a transform anyways .... which infact does work to install the msi... Now the issue arises on making it install silently.... Even with /qb or /qn switches it does not install silently... UI intervention is prompted for the installation....
Posted by:
anonymous_9363
13 years ago
You can ignore that message box. It's not an error, it's for information purposes.
The dialogs you're seeing are almost certainly appearing as a result of Custom Action execution. Re-run the install, this time with a verbose log. Then, when you see the first dialog, open the log. Use a proper text editor that bypasses file locks: Notepad won't be able to open a log while MSIExec has a handle on it. The last line in the log - or one pretty close - should detail the Custom Action which just executed.
Once you know the CA's name, you can experiment with having it not execute, normally by applying an impossible-to-meet condition e.g. 0=1 on its execution.
The dialogs you're seeing are almost certainly appearing as a result of Custom Action execution. Re-run the install, this time with a verbose log. Then, when you see the first dialog, open the log. Use a proper text editor that bypasses file locks: Notepad won't be able to open a log while MSIExec has a handle on it. The last line in the log - or one pretty close - should detail the Custom Action which just executed.
Once you know the CA's name, you can experiment with having it not execute, normally by applying an impossible-to-meet condition e.g. 0=1 on its execution.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.