I am running into issues installing snagit from the kbox1000.  After the install is successful when i try to run the application from start -> all programs  i get the follow error message below.  Its just a basic Msiexec install just like all the other MSI installs i push out via the kace.  I have also tried using bat files scripts etc and i cant seem to get Snagit to work.  I was wondering if anyone has come across this issue with the kace.
  JCd5cK.jpeg
Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1
Make sure your install does not delete the downloaded files. There is a check box as part of the Managed Install.  Looks like SnagIT looks for the source when it first launches. 
Answered 03/27/2015 by: rockhead44
Tenth Degree Black Belt

  • doesn't look like that option is available under User Console Library
    • I don't use the User Console Library feature so i must bow out. Good luck.
Please log in to comment
1
I had this same problem but it didn't become apparent until after many images were deployed.  Basically the other comments are correct.  Snag-it refers back to the source .MSI location (which you see in your screen capture) the first time it is run for each user profile.  If the checkbox to delete the source files is checked, you will encounter this.  

To remediate this dilemma, I simply put the source files back where the first run wizard was looking for them.  I created a File Synchronization job under Deployments.  The path is created exactly where Snagit was looking for the .msi and Snagit is happy again.  (Screen capture courtesy of Snagit)
 
Answered 03/31/2015 by: Warbrown
White Belt

  • Thank you! that solutions works perfectly!
Please log in to comment
0
The most likely scenario is that there are either registry settings or files which need to be installed to the logged-in user's profile. Because they're not present - the KBox will have installed the package using the local System account - the MSI is trying to "repair" the installation. The issue is that it cannot locate the source MSI in the location shown. I have no idea of how the KBox caches installation packages locally so can't help you on that score, I'm afraid.
Answered 03/28/2015 by: VBScab
Red Belt

Please log in to comment
0

a mix of the above...

Check the permissions of the folder where KACE caches it too, in case it does something peculiar.

Use the browse button to see if its there, probably not, or it would just repair, but it could be either not there, from the first point KACE has deleted the cache, or its there and the permissions do not allow read/Execute.

If it was just registry keys missing it would repair from the Windows\installer cache, so it must be doing a file repair. From my recollection of this wonderful app, it does look for a file, I think I work around the disappearing cache by using the duplicate file table, its easier for me to do that than try to get the deployment guys to tick the box to persist the cache, or not delete it.

Answered 03/29/2015 by: Badger
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity