Posted 12 December 2009 - 21:24
My setup needs a special "remote" mode where application files are not installed locally but kept on a file server where the application is supposed to have been installed before.
However, it must be possible to run the application on the file server, so I cannot do an administrative installation on the file server.
Does Windows Installer allow such a mode?
I thought about strictly separating the application files from non-file resources (registry, shortcuts etc.), which would also imply I cannot use built-in self-registration (because the file component does not get installed) nor InstallShield's "COM extract at build" mechanism.
As an alternative, I would set the features or components to run from source and set SourceDir to the installation directory on the file server at the beginning of the execute sequence. Would this work, or does this cause the installer to lose track of the MSI package?
What makes the issue a bit more complicated is that there are some (few) files I will have to install locally even in remote mode, e.g. some files for the Windows\System directory.
Posted 14 December 2009 - 10:00
Posted 14 December 2009 - 13:52
Posted 14 December 2009 - 16:16
Posted 14 December 2009 - 17:45
Posted 14 December 2009 - 18:13
1) Install the product on the server (not administrative)
2) Start the installation on the client (from CD or network, not from an administrative installation)
3) The client installation (InstallUISequence) checks whether "remote" mode is required (e.g. by checking whether the selected target directory is on a remote drive and then checking whether it is a valid installation)
4) If "remote" mode is required, the features are set to run from source.
Is this worth a try, or are there reasons this cannot work?
Posted 15 December 2009 - 09:52