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' (advertised shortcut), 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,
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


You will have to create a vbscript that launches the .EXE from the network, in this way you can also check if the network is accessable or not.
Install the vbscript as a file and then point the (advertised) shortcut for this script. So when the vbscript is launched windows installer will look for broken components and/or install on-demand.
Answered 08/07/2007 by: AngelD
Red Belt

Please log in to comment
Thanks AngelD.

I realised I could just have a locally-installed bat file, which in turn then called the network-based path, but actually I might do a VBScript'ed one instead.

If anyone else has alternatives, then do please post a reply - but I am thinking this is the only way to achieve it?

Answered 08/07/2007 by: stephenejones
Senior Yellow Belt

Please log in to comment
This bit of VB should suffice:

SET objFSO = CreateObject("Scripting.FileSystemObject")
SET objShell = CreateObject("WScript.Shell")

IF objFSO.FileExists("T:\Windows\SYSTEM32\MSPAINT.exe") THEN
objShell.Run """T:\Windows\SYSTEM32\MSPAINT.exe""", true
MsgBox "Network Connection is Not Available, MS Paint cannot be executed!.",,"Warning!"
Answered 08/08/2007 by: TOBES_UK
Senior Purple Belt

Please log in to comment