MSI Installs Locally But Not via Managed Install
Hey Guys:
I've been working with managed installs and scripting on a K1000 the last few weeks and I've gotten several installers (15 or so) to work correctly.
There's one program I can't quite get to work though - Fonality HUD Client 3.5.
When I attempt the manual install via command line using this script - "msiexec /i "hud-3.5.0.007900.msi" /qn" - it installs correctly. However when I upload the .msi (or .zip file with the .msi file enclosed) into the K1000 and add the same script to the managed installation command line it only copies the files to the program files directory. No desktop shortcut is added and no add/remove programs entry is made as it is when you install it manually.
Interestingly it allows me to run the program if I run it from the source .exe file once it's copied onto the computer. I also see the program in the KACE software inventory list.
I'm at a loss here and any help would be appreciated.
Thanks in advance,
Luke
Answers (4)
I have found that some applications install shortcuts and Add/Remove program information for the current user only so when you install via managed install those things don't seem to appear since they exist for the system account. I would recommend using PS Tools to open a command prompt as system and run the install from there and see if you get the same results as when you use the managed install.
Comments:
-
Thanks Chuck. One question though. Is PSEXEC required on the target computer in order to run or is it a program that just calls powershell?
Luke - lukeamotion 10 years ago-
You would only use PSExec on your machine to test the install, not as part of the managed install process. - chucksteel 10 years ago
-
So if I get it to work, I add the script that works on my computer to the managed install it'll work. Got. it - lukeamotion 10 years ago
I agree with chuck, it needs a users temp area to stage or just active profile to install in. You can try running this as a kscript as a user and see what happens
I have seen this a few times, esp with vendor MSI's. The ALLUSERS property is not set properly. Open the MSI and see what is in the Property table for ALLUSERS. Then post some updates....
If the MSi contains user profile-targetted data (e.g. HKCU registry fluff) then you should configure it for self-healing.
I won't repeat the procedure here, as there will be a quadzillion entries here on AD. For a succint summing-up and guidance, seek out John McFadyen's excellent article on it.
Can you also please delete your two duplicate posts? thank you.
My script is:
c:\share\psexec>psexec.exe "\\TARGETPC -i -s "\\fileserverUNC\path\path\file.msi"
"Result "PSEXEC Could Not Start \\fileserverUNC\path\path\file.msi on TARGETPC: The system cannot find the file specified. "
If I access it through my explorer window it pops right up. Sigh. - lukeamotion 10 years ago