Deploying LifeSize Cloud IE11 Plugin - Cannot Deploy via Kace - Works Fine via CMD
Hi guys!
Add the .msi as a dependency
I am working on pushing a "plugin" for a videoconferencing tool we use called "LifeSize Cloud". The program has a windows application, however, most users like to use the web browser version via: webapp.lifesizecloud.com
The installation for the plugin is an .MSI file. .MSI files I normally don't have any trouble with - but not today!
I am able to install this via command line:
msiexec.exe /q /i lswebrtcplugin.msi
However, when trying to deploy via Manged Install OR Script.
When deploying as a managed install, I have tried deploying with just the "/q" switch - and this did not work. I also tried again with overriding default installation>and also checking "Don't prepend msiexec.exe".. This did not work either.
I have tried deploying it via a Script. The script is as such:
Add the .msi as a dependency
on success run a BAT file
the bat file is just the code above "msiexec.exe /q /i lswebrtcplugin.msi"
This would not work either.. I tried running that as local system and as a local admin account that are on our machines, no luck.
When navigating to the C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots folder and finding the correct script that just tried to push.. I go into the folder, click on the .bat that is pushing along with it - and it is installing fine.
I am out of ideas and I was hoping someone with similar experience could lend a hand.
Thank you!
1 Comment
[ + ] Show comment
-
Make the bat/cmd file with the command line in it. Save it to the same place. Zip the files up and call .cmd file to install it. - quickwhips 6 years ago
Answers (1)
Answer Summary:
Please log in to answer
Posted by:
Nico_K
6 years ago
Top Answer
When you run it manually you are running this under your own account with the rights of your user.
As MI or script (except you check in the script the option "run as logged in user" or a special user) the user is the system service. So it does not installs in the user environment.
As MI or script (except you check in the script the option "run as logged in user" or a special user) the user is the system service. So it does not installs in the user environment.
Comments:
-
I don't know why I never try that - but this is pretty similar to the last problem I was having lol. That worked like a charm! It's pushing successful now.
I think I was worried about it not having sufficient rights when running as current user. But - as long as it's installing and no UAC prompts are showing up, I'm happy!!
Thank you! - feeldamped 6 years ago
