Jamf Sync app

Wgphoto
New Contributor III

Hey, guys. Started testing Jamf Sync app, since Admin is going away (gone?). I was checking out the documentation and the latest bug fixes list that the upload timeout was changed to an hour to accommodate large uploads, but does not solve issue with files larger than 5GB on a JCDS2 distribution point. This concerns me as my most frequent uploads are Adobe apps and they typically are larger than 5GB. I have not had much success with the web upload of these installers in the past, which is why I continued to use Admin. I am attempting an upload now using Jamf Sync, but I suspect it may just fail as package is larger than 5GB. Progress bar isn't doing much either. What have your experiences been?

Bug fixes

Changed the timeout for uploads to an hour to solve an issue with large uploads. This does not solve the issue with files > 5 GB that are uploaded to a JCDS2 DP.

Screenshot 2024-05-14 at 10.38.00 AM.png

 

7 REPLIES 7

dlondon
Valued Contributor

Hi @Wgphoto - Did you record the error?  I'm having problems with Creative Cloud apps too from the Jamf Cloud server to our local DP.

My error looks like this:
ERROR: Failed to copy CCLab2024JunSubstance3DPainterIntel_en_GB_MAC.pkg to <share name here>: dataRequestFailed(statusCode: 400, message: Optional("{\n \"httpStatus\" : 400,\n \"errors\" : [ {\n \"code\" : \"DUPLICATE_FIELD\",\n \"description\" : \"duplicate name\",\n \"id\" : null,\n \"field\" : \"packageName\"\n } ]\n}"))
24/06/19 11:08:21-ERROR: Failed to transmit data for https://<server name here>/api/v1/packages. Status code: 400

This may have been due to an issue, where only 100 packages (and you have more) were pulled into Jamf Sync, that was fixed. It can if occur multiple package records that contain the same file name but different display names. This can be done using the classic API, web console and Jamf Pro API prevent this.

Might give the following script a run. It loads your list of packages from Jamf Pro and looks for duplicate listings.

 

 

#!/bin/bash

function getToken() {
	authToken=$(curl -su ${user}:${pass} -X POST -H "Accept: application/json" ${URL}/api/v1/auth/token
)

	#	echo "authToken: $authToken" >$(tty)
	local theToken=$(/usr/bin/plutil -extract token raw -o - - <<< "$authToken")
	echo $theToken
}

echo "Enter the URL for your Jamf Pro server (https://your.jamfPro.server):"
read URL

tokenURL="$URL/uapi/auth/tokens"

echo "Enter Jamf Admin name for ${URL} [admin]:"
read user

if [ -z $user ];then
	user="jssadmin"
fi

echo "Enter password for $user:"
stty -echo
read pass
stty echo

token=$(getToken)
if [ $token == "" ];then
	echo "exiting"
	exit 1
fi

packages=$(curl -s -X GET -H "authorization: Bearer $token" -H "Content-type: application/json" -d "$newPackage" "$URL/api/v1/packages")

#echo $packages
$(/usr/bin/osascript -l JavaScript << EoS

	var duplicates      = 0;
	var duplicatesArray = [];
	var unique    	    = [];
	packagesArray  		= $packages.results;

	var packageCountDict = {};

	for(var key in packagesArray) {

		let filename = packagesArray[key].fileName;
		let displayName = packagesArray[key].packageName

		if (filename in packageCountDict) {
			packageCountDict[filename].push(displayName);
		} else {
			packageCountDict[filename] = [displayName];
		}

		if (unique.includes(filename)) {
			duplicates += 1;
		} else {
			unique.push(packagesArray[key].fileName);
		}
	}

	console.log('\n----- Summary -----');
	if (duplicates == 0) {
		console.log('no duplicate package records found');
	} else {
		for(var whichFile in packageCountDict) {
			//console.log(whichFile + " count: " + packageCountDict[whichFile].length);
			if (packageCountDict[whichFile].length > 1) {
				console.log(whichFile + " has " + packageCountDict[whichFile].length + " package objects.");
				for (var displayName in packageCountDict[whichFile]) {
					console.log("    " + packageCountDict[whichFile][displayName]);
				}
			}
		}
	}
	console.log('\n');
EoS
)

 

 

 

 

calfriday
New Contributor II

Sadly - this is still an issue. Ever since Jamf Admin has been shutdown, I have major problems uploading anything. File sizes greater than 5GB always fail on Jamf Sync.
Trying to upload direct to jamfcloud via the browser is arguably worse because the session will likely expire before and you will have no confirmation of whether or not your file uploaded correctly. 

Even once packages appear to be uploaded, it takes forever for them to be available. You have no way to verify if your packages have fully uploaded because you can't try to redownload them until they become available which can take hours.
Jamf admin was so much easier because you could upload multiple files at a time, it was fast, and packages were available quickly. This feels like a step back in functionality 

daniel-packager
New Contributor

Same here i get the same error message too

CasperSally5432
New Contributor III

chiming in to say we're also having issues with 5GB+ apps.

jimkirk
New Contributor II

Just chiming in to say discontinuing Jamf Admin without a suitable replacement has been frustrating.

leslie
Contributor II
Contributor II

Hopefully by now you've found the issue uploading large files (>5GB) has been resolved.