/build/static/layout/Breadcrumb_cap_w.png

Trouble Deploying .msi Through kace

I used App-deploy to Repackage our companies VPN Client installer into an msi. When I go to test and Distribute to my test machine is where I run into my problem.

In kace it is showing that the VPN client has been installed, But on the machine itself, the program still doesn't appear.

Any help? And anything I can provide to help ?
Asked 10 years ago 2813 views
3 Comments   [ + ] Show comments
  • Does the msi work when manually installed on the machine?
    Does the msi have any special parameters you are using? (silent install, etc...)
    I'm assuming you're using Managed Install.
    Look in the Program Data\Dell\KACE\User\KAgent.log file right after the program runs to see if there are any errors.
    Also the KACE system can distribute EXE files as well, so you might want to do that if the original is an exe. - h2opolo25 10 years ago
  • One thing I have noticed in deploying apps with MSIs is that KACE will say it is successful even if it didn't get installed. I am assuming this is because the success of the script is based on whether or not the action of launching the MSI on the machine was fired off, rather than whether or not the software was installed. h2opolo25 has a great point though - always test what you want your script to do first, i.e. manually try to install it; I usually try to run it from the CMD prompt after verifying the msi installer works by double clicking on it as well. - jfrank 10 years ago
  • What VPN client is it? - k1000-chan 10 years ago

Answers (2)

Posted by: Badger 10 years ago
Red Belt
0

ooh yeh, I agree with EdT there....

There is a very very very very good chance that there is a supported 'silent install' from the vendor.
The very nature of the VPN app, is that it will be doing some very low level stuff that does not fit nicely into the MSI standard actions.

Focus on a silent install of the vendor media

Posted by: EdT 10 years ago
Red Belt
0
I suspect your repackage of the vendor install is at fault. A VPN client needs to load into the network stack which either requires a reboot to complete, or at the very least will stop the network running and then restart it. If all you have done is to capture the changes to files and registry, chances are that you now have no mechanism to insert the VPN client into the network stack. You don't mention whether you have rebooted the system after install, but it is perfectly possible for the MSI to return either 0 or 3010 to show success as it will have completed the installation successfully, but your MSI is fundamentally broken so it does not actually install all the bits that are needed. Equally, if you have forgotten to set ALLUSERS to 1 in the property table, a KACE installation will fail to install any shortcuts as they will go to the profile of the service account being used for the install, which of course does not exist, as service accounts do not have a user profile. If you enable verbose logging, the logfile should give you more information. Just review what the user profile folders resolve to in the directory table list-out.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ