Posted on 07-23-2020 12:19 PM
We have cloud Jamf Pro and both an on prem DP and a cloud one. Most packages need to be available to users on or off campus, but there are a few which are used only in the campus computer labs and which are too big for the cloud DP to accept. In order to not attempt to sync those ginormous packages every time, I've got the cloud DP set to sync specific files instead of the full contents of the master, and the biggies are unchecked.
The big downside to this is that each time I add a new package that DOES need to be in the cloud, I have to remember to go into the settings and add a checkmark for it. Assuming there is no way to change the default for new packages to "yes" from "no", is there any other clever scheme I could use to ease the administrative overhead?
Posted on 07-17-2024 05:41 PM
I know this is an old post, but we previously did the same things when jamf-sync wasn't avaliable.
Now we set JamfCloud DP to be the master DP, and upload our extra large/unsupported package sizes to our on-prem DP. We set in the policy to force the use of our on-prem DP. (Our on-prem DP is internet avaliable via HTTPS).
The only downside I've noticed is when viewing packages in Settings => Packages in Jamf Cloud webUI, the packages uploaded to on-prem show ! warning next to them. This presumably is because jamf pro/cloud cant find the packages in the jamf cloud DP. Again not a big issue as we only use our on-prem DP for these extra large packages.