Software Deployment Question

Want to use K1000 File Synchronization to copy a .jar file to the Public Desktop

11/28/2017 1313 views
I've used Kace 1000 before to copy setting files, shortcuts and so on. I'm trying to find a way to copy a 7MB .jar file to the Public Desktop on computers running Windows 7 x64 Professional. I know with shortcuts the best practice is to add the shortcut to a folder and zip it up. Then have it set to target C:\Users\Public\Desktop using persist. While I could most likely get to work via a script, I want to do it the File Synchronization way because half the computers I need to target are laptops and not powered on most of the time. With File Synchronization I could target using labels and then leave it set and eventually it will. My issue is that while ini, json and internet shortcuts work fine, I can't get it to copy this sort of file this way. Any suggestions? What are the limitations of File Synchronization when using Kace 1000?  I realize that File Synchronization isn't exactly the same as coping something but it seems to work that way. I have tried having the file contained inside a zipped in a folder and with just the .jar file itself.
1 Comment   [ + ] Show comment


  • So I have gotten a .bat to copy to the public folder but I can't seem to get it to copy to the user's folders so matter what flavor of wildcard I use: %allusersprofiles%, %userprofiles%, etc, etc. Anyone have any advice on this?

All Answers


As far as I'm aware, file sync is basically a file-copy for Enterprise/Education level deployment, but I have only used it to deploy&lock settings for browsers. I am not entirely sure what the Persist function does either; whether unchecking it will stop the sync if the computer already has the file it needed.

How long have you waited for the File Sync to happen? I can never get it to happen immediately on a test computer, if I even see it happen.

Answered 01/28/2019 by: zweeks
White Belt


Hey There, File Sync does exactly what you are trying to accomplish. In your case as it is a single file you don't need to zip it, just copy the *.jar file up. Firstly go into soft, create a new software item, call it jar Update and then associate that file to it, ensuring that in the supported O/S section that the windows systems are available to distribute to. Then , under distribution, select Choose action, New, Give it a name, select the path to the public desktop and if you are adding an additional folder at that point click on create path, select the credential you wish to use that has access to write (local Admin), select persist so that it will remain. beneath that select Manage Associated labels and if you have a smart label created for "Windows 7 x64 Professional" then target those machines and then whatever schedule you want it to run on. That simple.... Whenever you want to replace the .jar with a new version just go back into software and replace the associated file with the new one and if it isn't running on a schedule then click on select and resend file to update. The most important part here is the Supported O/S version part of the software config item and ensure that the O/S versions you wish to target are listed and select under supported O/S. Good Luck. Dave

Answered 01/28/2019 by: Ozhunna
Yellow Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


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