Jonathan Cohen
Jonathan Cohen
I can confirm the same behavior.
Care to direct me to the forum in question? Or the title of the post? Thank you,
I'm still seeing this with the current releases of Filewave and Autopkg (fresh installs with today's releases). Is there an update on the resolution?
I was working with filewave this morning to try and pattern to this issue. We discovered that using Filewave version 11.2.2 with autopkg version 1.0.1 and autopkgr version 1.4.2 on...
Confirmed - I was able to use autopkg with El Capitan (described above) to get Chrome, Evernote, and Java8 into our FW Server. I'd be happy to assist in future...
I'm no longer having issues with this - now running macOS 10.12.6, Autopkgr 1.4.2, with AutoPkg 1.0.2
This was actually user error on my part, we dump all filesets for a given application or set of applications into a fileset group now. We then associate the group...
We then use the fw_fileset_group key in our recipes to allow AutoPkg to send files directly into the correct FileSet group when a new version comes out.
I had a bone head mistake. Check your Administrator's permissions in Filewave Admin. I created a user and then didn't let that user import things to the server... the result...
These are the allowed arguments that are currently built into the importer. - fw_import_source - fw_fileset_name - fw_fileset_group - fw_destination_root - fw_app_bundle_id - fw_app_version Full details are outlined in the...