Hi all,
Wondering whether this is actually possible/concievable at all, or pushing the boundaries of what is viable with MSI/Windows Installer.
We are generally using user-assigned apps deployed through Group Policy Software Installation to push MSI's - we are configuring them as 'assigned', but not 'auto-install' because it creates the rather nice 'placeholder icon' (advertisement), which the user can then fire if they want that particular app, it goes away, installs, and runs automatically.
This works fine for most apps, as they are installed locally to the workstation - and the shortcut points to the 'key file' executable as part of the package.
We have a few that have a mixture of both locally installed components, but still run primarily from a network path/exe.
Is there anyway to make a network-based file as the key file, or to configure the advertisement in some way so that it installs and run the exe from the network location?
When I change 'Advertised = Yes' in the Adminstudio Editor, it removes the Target I specify (e.g. [APPPATH]\Program.exe), and gives me the Component Warning.
Anybody had the same requirement and got a workaround - perhaps a fiddle with the Feature/Component, INSTALL/TARGETDIR or VBScript in a custom action?
Ta in advance,
Steph
