@cnoboa The URL is: https://jamf-patch.jamfcloud.com/v1/software Port 443 Sorry for not posting that sooner, part of my goals this first quarter are to have more of the Patch Back End Operations transparent. We have a KB that we started and I will be adding to in the near future. KB: https://www.jamf.com/jamf-nation/articles/424/software-definition-files-in-the-jss
@m.entholzner Morning, it looks as though you are correct the build script missed the JRE update, I will have that updated and pushed out this evening. We have a more manual back up plan to catch these updates, which it did but a day later. We are adding a lot more automation in this first qtr of this year to continuously improve on the Target Response Time and get this down and out to you as quickly as possible, hopefully same day! This hiccup will really help us write something to catch things like this in the future. Thanks for your patience.
You should also rename it. There is nothing in what this does that deals with patching. It would have been better if you named it "Version Tracking", at least then it would be what it does.
OK, "Version Tracking for the few things WE wish to track" it the best name. Track the OS at least, I care more about the OS then any Adobe product.
My patch reporting list has not been updated since december.
Is there maybe a file that has been corrupted that I can delete to solve this? I can access the https://jamf-patch.jamfcloud.com/v1/software from the jamf server (mac os x 10.12.6 / JAMF 9.99.0)