@lukecater commented on GitHub:
Thank you! I've been using the beta, and it's performing really well during the testing phase—kudos! In my workflow, after changing a computer's name, It…
@scriptingosx commented on GitHub:
Yes, unfortunately there are technical limitations in the custom schema JSON which mean that we cannot provide the complete functionality in the custom JSON.…
@scriptingosx commented on GitHub:
I will take this as documentation request. This should be added.
@scriptingosx commented on GitHub:
fixed in the 1.1 documentation
@ecanault commented on GitHub:
Well perhaps we don't have the same experiences 😉
I think that Mac admins using Setup Manager are smart enough to not put 1 Gb of data in a configuration…
@scriptingosx commented on GitHub:
There are two reasons I am reluctant to implement this:
- creating profiles with base64 data is not trivial
- in my experience, the more data a profile…
@colorenz commented on GitHub:
Hi, you only need a storage location to upload the image. You can simply use your Jamf as a free image hoster.
You can upload them to your jamfcloud under the…
@scriptingosx commented on GitHub:
There is a known issue with Jamf Pro 11.11.x where packages that are uploaded to Jamf do not get the md5 hash computed and stored in the Jamf Pro record. That…
@scriptingosx commented on GitHub:
we are working on a solution for this, though not in the way you described
@fraserhess commented on GitHub:
This is already requested in #31 and #38
@scriptingosx commented on GitHub:
please test with 1.2beta
https://github.com/jamf/Setup-Manager/blob/beta/ConfigurationProfile.md#dark-mode