Ability to scope smart groups based on jamf created EA for Patch Management, for example adobe-air is the EA that is created by JAMF however you can't use this attribute withing a smart or static computer group to help eventually patch the tool with a third party solution?
So my feature request would be having the ability to choose what packages/scripts I can replicate to a local distribution point from a cloud distribution point (primary).
Currently my main distribution point sits in an Amazon S3 bucket in AWS from which we upload all packages from Casper Admin to, works alright hit and miss with big files...(but that's a separate subject) and have various local distribution points (mainly mac mini servers') in many countries purely to handle the imaging of a Mac.
Now instead of replication my whole entire S3 bucket to each local distribution point where over 75% isn't going to be used for imaging as it's server from the cloud, I'd like the ability to choose only the packages that are in my configuration and copy them to the local distribution point, ultimately saving storage on the local DP's.
If you need more info give me a shout,
Thanks for the great detail in this post! I am linking it to another Feature Request that is asking for enhancements around replicated files are viewed and regarding which files are replicated. This connection will keep the votes and comments in one spot. Please keep the great ideas coming and let us know if there are any concerns about the link.
jamf binary to use both DNS name and IP address when checking in etc, let's say we're having issues with DNS on Macs or the network the binary would try to check back to the JSS using the DNS name but as a fallback a feature should be it can check back to the JSS by IP Address so there's never a break in connectivity with the Mac and the JSS.