Hello Nation. I have a couple of resources for everyone looking at Jamf Pro 10.2 and the new External Patch Source feature that will allow you to create your own patch definitions for internal apps, or apps that Jamf doesn’t provide patch definitions for:
Create a basic (starter) patch definition for an application on your Mac. Cuts down on the time needed to write definitions.
Host and managed your patch definitions and allow them to be subscribed to in Jamf Pro.
Here's the Jamf Marketplace listing: https://marketplace.jamf.com/details/patch-server-for-jamf-pro/
You can check out the documentation here: http://patchserver.readthedocs.io/
Just stumbled across this post and I'm hoping to get further clarification, this is just a way for us to make integrate additional data for use with patch reporting and patch definitions but this isn't something that actually provides the source for the updates so that we don't have to upload a new package every time a new version comes out, right?
I have setup the Kinobi patch server and current have 62 software titles setup. I also use the patch process to remove unwanted software from clients. Whenever someone installs software which matches the application bundle ID I have a policy which uninstall the software. It also helps to spot software which has been installed and renamed to look like another software program.
Within the server which I setup and track some software using EA's such as home-brew, Microsoft Teams, DisplayLink and Docker.
My current list of software titles are:
Google Web Designer
IntelliJ IDEA CE
Microsoft Remote Desktop
Visual Studio Code
VLC media player
Currently there isn't a way of sharing the these titles on the forum, maybe someone at Jamf can post them if I sent them in.