Closed inglenny closed 1 year ago
Does OfficeTemplates-3.0.pkg
exist on the server?
Yes it is. However the new package (MicrosoftWord-UNI-16.72.pkg) cannot be found on the server. Even though it seems like it uploads just fine.
That explains the policy failing to upload, at least. Is this affecting all new packages or just this one?
I just tested this with this package after configuring the failover URL in jamf. All other recipes using the jcds mode haven't been tested yet.
Just tested it with another Package. Also not working. Any idea what we can do?
Is that package also not actually present on the server after the recipe run?
Correct. The Autopkg logs indicate that it was uploaded correctly, but it cannot be found in Jamf Cloud, if I search for it in Settings -> Packages
Any idea what we could do?
Does it work manually adding a package via the Jamf Admin GUI on the same machine that AutoPkg is running?
Yes manually uploading the package via Jamf GUI Packages uploads the package just fine.
Not sure what to suggest. The output from curl is that the package was successfully uploaded. Does it never appear or is it just taking a long time? You could add in a Sleep processor if the latter.
I would also try to eliminate any doubt by removing the separate Office templates package from the policy and seeing if that works.
It does never appear. Even after a week. Since randomising the failover URL JCDS mode is not working anymore. However, we used JCDS only for packages which are 1GB and larger, because the upload was not working properly with standard mode. Just for the fun I tried it again with the standard upload mode and now also packages over 1 GB get uploaded just fine.
So we deactivated JCDS mode completely and have no issues anymore. No idea why it suddenly works.
Labelling as "feature of experimental jcds_mode" :-) Glad you got something working.
I updated to the latest version of jamfuploader and corrected local trust. However I'm having issues with jcds upload. API access rights are set as described with SSO read/update.
Package was removed from server as well as policy.
Here is the log of what happens:
I replaced Username, Password and URL and failover URL with XXX