Hi all,

As the title says, trying to push out an in house .msi package and it doesnt work. However previously made managed installs still work.

Interestingly enough this is how it goes:

1) Make the managed install, select Override default installation, dont prepend msi.exec.exe. Full command: msiexec.exe /i "filename.msi" /qn
2) Add computer to test the install
3) Notify before and on completion for testing purposes
4) force inventory on the machine
5) Notify message comes up, continues with install, gives finished notification.
6) inventory in KACE shows the program as installed, but is missing from the machines control panel.

The kagent.log doesn't have useful information in it either, even in debug mode. You might see the msi name but it doesnt say anything about it failing or working.

Even adding a log switch to the full command doesnt put out a log file.

Anyone else experiencing this?
2 Comments   [ + ] Show Comments

Comments

  • sanity check: does the msi install correctly when you run it manually on a computer? What about when you use the "msiexec..." command locally?
  • It does. What ive tried:

    -Run msi successfully locally
    -Run the msi from command prompt with the exact same commands given to the k1000 locally with success.
    -Checked the logs msiexec puts out when installing, and there is no notable difference between the logs when run locally or from k1000.
    -Checked the Application event logs and there is the same amount of events generated when ran locally or from the k1000 managed install.}

    Id just like to re-point out that managed installs that were set up ages ago (like almost a year ago) still work, however new ones do not.
Please log in to comment

Answers

-1
uncheck delete downloaded files and run the Mi again on a machine.  Is the msi getting downloaded.  It could be installing then rolling back on you, add a logging switch to your msi call like /l*v c:\kace.inst.log
Answered 08/12/2016 by: SMal.tmcc
Red Belt

  • Ive tried it with that option checked and unchecked. I've also tried putting in the logging switch for msiexec and that also didnt output a log file.

    Gonna try some more testing.
Please log in to comment
Answer this question or Comment on this question for clarity