Crossposted using Lemmit.
Original post from /r/jamf by /u/D3xbot on 2023-06-20 20:45:08+00:00.
My organization has several campuses and needs a few applications which are not friendly to Jamf Cloud/JCDS. Because of that, we use a hybrid of on-prem file share DPs on each campus and Jamf Cloud where all packages are on our file share DPs and most (but not all) packages are replicated to JCDS.
I’ve got our network segments set up so that when a Mac checks in on our network, it goes to that campus’s network segment and gets set to use that campus’s on-prem file share DP and fall back to JCDS. If a Mac checks in from off-network, it goes on the external network segment and gets set to use JCDS first.
Lately, I’ve noticed an uptick in “failed” package installations. Looking into the failures, I found something interesting. Most of them failed to download from the local DP for one reason or another, failed over to JCDS, then successfully installed the package from Jamf Cloud:
Executing $PolicyName
Mounting $On-PremDPforCampus
cp: /Volumes/path/to.pkg: No such file or directory
Error: The package ($PackageName.pkg) could not be found.
Retrying using distribution point Cloud Distribution Point…
Downloading $PackageName.pkg…
Downloading https://use1-jcds.services.jamfcloud.com[…]$PackageName.pkg…
Verifying package integrity…
Installing $PackageName.pkg…
Successfully installed $PackageName.pkg.
Unmounting file server…
Has anyone else experienced this type of error? If so, have you solved it or do you just deal with it by scoping packages to smartgroups based on “Has Application $AppName”