InstallAware

Hello,

I am a new customer since a couple of weeks so I am learning by doing at the moment. I am using IA much like a deployment tool, launching both my own as well as 3rd party installers and utilities.
Version: 15 Build 11.20.12

From within a IA setup I am trying to execute another IA setup which resides on a file server:
Run Program \\myserver.xx.yyy\folder1\Unattend\FlowCad\for_Orcad16.6\FlowCad.exe /s (WAIT)

When I do this I get a prompt halting everything:
The publisher could no be verified. Are you sure you want to run this software? Run/Cancel

The file server is in the intranet zone. Run components not signed with Authenticode=enabled, Launching applications and unsafe files=enabled.
There is no warning like the above if I use start->run with the same command line on the same machine.
If I add a .bat-file to my project which executes the above command line and:
Run Program $SUPPORTFILES$\test.bat (WAIT)
I get no warning halting the setup.

Why do I get this warning when launching a setup via UNC-path directly from within IA but not otherwise?

Working with a .bat file for each command/setup I need to run is a temporary workaround but it complicates the setup and makes it much harder to maintain and "read".

EDIT:
Just found and tested "Run program as" (very quickly) with no other options except the executable and parameter "/s". This seem to work! (why?)
Also, as a side note: "Run Program" and "Run Program As" are both displayed as just "Run program" in the editor.

Will do some more testing but an explanation of my results would be interesting, what differs between Run program/Run Program As when supplied options are just the executable and its arguments?

Dear User,

I really don't know why on your OS launching a setup via UNC-path directly doesn't display the UAC warning.
I can only suppose that probably it is due by your personal system settings ... with my OS the UAC warning comes up everytime.

On Vista or higher, when setup is elevated to full admin rights, all tasks spawned by setup are also elevated to full admin rights.
This might be a problem when setup is originally invoked from a limited user account and elevated through a UAC dialog.

To skip this behaviour with "RUN PROGRAM AS" command is possible to set "Run under limited user account when UAC is enabled and setup is elevated (de-elevation)".

While setup will complete successfully, any tasks spawned by setup (such as the application being installed) will be run as administrator, instead of the original limited user. This can pose problems for users when they cannot re-run the application being installed as administrator after setup quits; thus potentially leading to misplaced application configuration files and/or user data. To prevent this problem, check this box. This setting has no effect on operating systems older than Vista, or if UAC has been disabled.

Are you running your setup package from a limited user account?
Is it your package elevated to full admin rights?

Regards

Hello,
Forgot to mention, OS is Windows 7x64 (UAC is completely turned off) and Windows XP x86. The initial setup which launches other stuff via UNC-path is deployed running under a local administrator account. When "Run program" is used instead of "Run program as" I get the "Unknown publisher"-prompt.

The expected result is not to be prompted considering the current settings of our workstations (server is in intranet zone). The warning is not related to UAC since it appears under XP as well.

Anyways, my problem is resolved since I have verified that "Run program as" works just fine, without any additional parameters other than .exe and its parameters. I was just curious to why "Run program" does not work in the same way and what differs between the two. Since they're displayed as the same command in the editor I figured they would use the same method to spawn new processes, and the difference between the two just was a matter of number of parameters one could supply.

Regards

Dear User,

For what I know, even if both commands are both displayed as "Run program" in the editor, internally the commands use a different WIN API call.
This should clarify the different behaviour you found.

Anyway, I'm happy that solved your issue.

Regards