When a local admin, who is just a regular user on our network, runs our setup package from the network, the MSI property SetupExeDir always returns the unc path, not the mapped dirve path.
This applies to all the other related properties in both MSI and the script (SRCDIR, SOURCEDIR, SetupDir)
Now, when a network admin runs the setup, SetupExeDir returns the mapped drive, not the unc path.
This is a critical problem for us, as the underlying application MUST be installed to a mapped path, and we are checking during the install that the user is running the install from a mapped path.
The installer is InstallShield 2009, with a mix of InstallScript and an MSI package.
How can I force the script to check the mapped drive, without resorting to external dlls?
Any rapid help MUCH appreciated!