MSI will not install per machine
I need to deploy Trimble Point Creator to some employees. It ships with an .EXE so I created an MSI using Repackager in AdminStudio. I seem to have the licensing and installation set when I am installing the MSI while logged in as myself, however, when I login as another user on the VM after the install, it acts as if it has not installed everything and attempts to find the MSI file to finish installation. Inside of the MSI the ALLUSERS property is set to 1 and the MSI script itself is as follows...
msiexec /i "MSI name.msi" ALLUSERS=1 /qn
Does anyone have any ideas as to why this won't install on a per machine basis?
-Adam
-
When you say "attempts to find the MSI", do you mean it fails? If so, I suspect the MSI was deployed to a location to which only you (or admins) have access. Re-deploy but use a "public" location. That way, when the self-heal (what's happening isn't strictly speaking a repair) kicks in, the Wi engine will be able to locate the MSI and finish the installation to completion. - anonymous_9363 11 years ago
Answers (2)
That is a very normal behaviour.. your msi can contain "per user" information which will be "repaired" when a new user tries to start the application.
this should be a one time occurence.
if you believe that this should not happen, please check the eventviewer to find out why the repair is triggered.
It could be that your package contains some information that shouldn't be there , causing this repair.
Jeroen
It fails to find the files stored on the network location. Unfortunately the way we organize things, normal end users to not have rights to access the folders that contain the files. Once an install is deemed to be in working condition we use SCCM and install apps as an Admin from distribution points. We can usually get around this by persisting the content in the client cache but we try to avoid this whenever possible so it doesn't become full. I was able to obtain an MSI shell that calls the .EXE and the HASP installed stored within it. This works so it looks like the issue has been resolved. Thank you for the response.