Same here, both via web and jamf admin. Packages stay on "Availability pending". Were on cloud, Jamf 10.13.

Im having similar issues where it'll upload and fail at 99 per cent

same issue. we just migrated to Jamf Cloud last week and at first, replication seemed to be ok. I added 2 packages and tried to replicate again and got an error. Now when adding packages through Jamf Admin, it gets to the end and then says it failed to upload due to some connectivity issue. I uploaded a Mojave package yesterday through Jamf Pro on the web and it still today shows availability pending. Not off to a good start here...

Same issue here, have logged a request.

Found the same as other Jamf Admins, after several attempts the packages uploaded! This was using Admin and Web.

Some articles indicated AWS server(s) may have a possible bottleneck or the way the system manages the file(s) during the upload.

Have you tried to upload .pkg file through JSS, Settings > Computer Management > Packages > New

I have a related issue when I come to replicate from Jamf Pro up to Jamf Cloud.

It will quite often upload PKGs that have already been successfully uploaded to the cloud, sometime about 3 or 4, so can take quite a while. The PKGs are already available in Jamf Cloud and are being utilised by policies, so I know it has already worked previously.

It is not a massive problem, but it is frustrating if i have to wait for them to replicate again (sometimes again and again).

I have had this across different versions of Jamf Cloud /Jamf Pro

I did the same thing as @tanton and mine uploaded finally. I don't know whats been going on with the reliability of Jamf but it can be frustrating. I was given a work around script that uses the API but haven't had any success with it. Has anyone tried this script?

#!/bin/sh

####################################################################################################

#

# THIS SCRIPT IS NOT AN OFFICIAL PRODUCT OF JAMF SOFTWARE

# AS SUCH IT IS PROVIDED WITHOUT WARRANTY OR SUPPORT

#

# BY USING THIS SCRIPT, YOU AGREE THAT JAMF SOFTWARE

# IS UNDER NO OBLIGATION TO SUPPORT, DEBUG, OR OTHERWISE

# MAINTAIN THIS SCRIPT

#

####################################################################################################

#

# DESCRIPTION

# This script will create a package record inside of Jamf Pro. Can be used when a large package

# such as a 20GB+ Adobe file cannot be uploaded to JCDS. Manually upload the file to a local SMB / HTTPS

# share, then use this script to create it's record inside of Jamf Pro.

####################################################################################################

#

# DEFINE VARIABLES & READ IN PARAMETERS

#

####################################################################################################



read -p "Jamf Pro URL: " server

read -p "Jamf Pro Username: " username

read -s -p "Jamf Pro Password: " password

echo ""

read "Package Name (including file extension)": packageName               #Name of the package (including file extension)

####################################################################################################

#

# SCRIPT CONTENTS - DO NOT MODIFY BELOW THIS LINE

#

####################################################################################################

# Courtesy of github dot com slash zdorow

echo "Testing connection to Jamf Pro..."

test=$(curl --fail -ksu "$username":"$password" "$server"/JSSResource/users -X GET)

status=$?

if [ $status -eq 6 ]; then

    echo ""

    echo "The Jamf Pro URL is incorrect. Please edit the URL and try again."

    echo "If the error persists please check permissions and internet connection"

    echo ""

    exit 99

elif [ $status -eq 22 ]; then

    echo ""

    echo "Username and/or password is incorrect. Please edit and try again."

    echo "If the error persists please check permissions and internet connection"

    echo ""

    exit 99

elif [ $status -eq 0 ]; then

    echo ""

    echo "Connection test successful! "

    echo ""

else

    echo ""

    echo "Something went really wrong,"

    echo "Lets try this again."

    exit 99

fi

####################################################################################################

#

# MAIN PROCESS

#

####################################################################################################



curl -kvu ${username}:${password} -H "Content-Type: text/xml" ${server}/JSSResource/packages/id/-1 -d "<package><name>${packageName}</name><filename>${packageName}</filename></package>" -X POST



exit 0

I was having the same issues with uploading the various Mojave packages. Anything over 5GB would fial. I ended up using a Windows 10 Based PC with chrome browser to upload the files to our Jamf cloud instance and it worked perfect.

is it the macOS Mojave installer? If so, install that via VPP purchase and use Mojave Caching server to resolve bandwidth concerns. What packages are you trying to install?

@rfadul I tried both in Safari and Chrome to upload the pkg and Chrome just sits there while in Safari I get the message "Package failed to upload" in red right below the "Choose file" button. This is a .PKG that I generated via the Adobe CC Packager. The corresponded "uninstaller.pkg" uploads without issue. This is the first time I've ever experienced this issue.

PS For lack of anything else to try, I re-ran the cloud packager and therefore created a new .pkg. This uploaded without issue. So, no idea if the problem was on Adobe's end or when JAMF Admin zipped the .pkg together! sigh Well, whatever, it's working now.

No Support for me as well I am struggling to deploy pro plus

Hi everyone, I was experiencing this today and it turned out to be a licensing issue. We had purchased more licenses and forgot to update our Activation Code in the JSS. Immediately after updating the Activation Code, I was able to upload packages again.

@smpersists2020 are you talking about the licenses for the software that you are uploading or the licenses for Jamf Pro?

We might be having different issues. I learned that JAMF Admin has some problems and messes up the database on JAMFCloud. I had to rename the file I wanted to upload to something different and then re-upload it. It worked after that. I'm on Catalina right now.

I seem to be seeing the same problem over the last couple of weeks. I upload packages, they seem to be stable. I deploy the policy and see it fail, then call it manually and get an error that says the package is not available. After I look at the packages I'm finding most of them are now stating "Upload Failed"

I’ve seen this issue before. I did the following to fix.

• delete errored pkg from jamfcloud entirely


• rename pkg for uploading using no spaces, such macOSCatalina.pkg and re upload using web GUI (pref from a device that is hard wired in as it seems to have a higher success rate)

After I did this it worked.

From jamf support engineer: “Spaces in file names, mainly packages and script just a bad time with Jamf Pro. Naming files with camelCase, named-with-dashes or named_with_underscores are just better.”

Hope this helps!

I have been able to get around the problem by deleting my package all together and recreating a new one. Unfortunately you then have to re-add the package to any policies using that package.
I have also seen trying again later to work as well.
Frustrating issue.

+1 to @zachary.fisher 's workaround.

I've been having problems uploading the newest Microsoft Office v16.38 pkg this whole week via the web gui and jamf admin. After deleting all pending pkgs, renaming the local pkg with no spaces and no underscores, I was finally able to successfully upload the 1.64GB Office pkg.

I just finished testing a deployment of this new pkg to my own Mac with great success.
Hopefully this can help others get around this annoying issue while Jamf gets around to fixing it properly.

I had the same issue today with the original "Microsoft AutoUpdate 4.29.pkg"; I uploaded it several times and it always failed, but other PKGs could be uploaded without trouble.
The solution was to zip the PKG file, then uploading worked smoothly.

Having the same issue today. I've tried multiple solutions but I think there is a corrupted package list in the JCDS. I am not sure how to resolve this.

I am also having this issue today, seems like somethings broken at Jamf? But status.jamf.com says everything is green..

I heard from a Jamf support response that this is related to PI-006574 which is not currently listed on the PI board.

@molops: [PI-006574] Fixed an issue that sometimes caused large packages to fail to upload to the JCDS.

It's not an issue with large packages - it's an issue with EVERY package!

So I also talked to the Jamf Support today and they asked me to simply in Jamf Cloud GUI go to:
Management Settings > System Settings > Activation Code > Edit
and then re-paste the activation code and Save (this resets something, don't know what).

Then uploading packages worked again!