The private App Installers beta group was seperate to the standard Jamf Pro beta forum and the guide was published in the seperate forum. We are still making further changes to App Installers and hope to be able to open the feature up in a public beta in the near future.
Hey Justin, appreciate the update! Really looking forward to the future of patching with Jamf Pro. Question about the public beta of "App Installers", will it be coupled with a future Jamf Pro beta release or be its own separate beta release?
Hey Justin, I installed 10.37 in my on-prem dev environment and everything seems to be working with the enabled Cloud Services Connection. However, I am getting mixed signals about this being available for on-prem customers once it leaves the "preview" phase. Do you know if this will be available to on-prem environments? If not, I think we need to get a feature request going as this would be extremely useful (I'm sure) to us who have on-prem environments.
@joelsenders App Installers is for Jamf Cloud subscription customers. Whilst today App Installer will work with a non Jamf Cloud instance, it is not supported. There will be some changes in a future iteration of App Installers that will rely on infrastructure that is only available in Jamf Cloud. Once that change is made, the feature will cease to work in an on prem environment.
I don't understand why this isn't being implemented into the Patch Management section where we can control who gets what version of the app (Early Adopters vs All). With this new App Installers, you have a choice of all clients or all servers. This should have been combined in one location,
Hi @andrewsp. @joelsenders is correct. App Installers uses MDM instead of the Jamf Binary so the underlying behaviour is constrained by what we are able to do with MDM commands. There are a number of other significant architecture differences with App Installers, the packages not being hosted on a customer distribution point as one example, that prevent us from just combining the two feature areas into one. There will be more control over the deployment behaviour in a future release of App Installers.
I agree, need release branching and control like basic dev, testing & production to stage and control releases.
@JustinC is there a concept of rollback with the app installer implementation? What if you dev did testing and it worked as expected but when put into production something "issue" or breaking a app workflow was discovered can you easily rollback to a working version of the application?
Does the current process do any QA on the installer does it install or security or virus QA process on the developer installers? I have seen many developer installers that incorrectly set permissions or do many bad installation processes. For example, AutoPKG, uses virus total to do VirusTotal. VirusTotalAnalyzer is an AutoPkg processor to query downloaded files from the VirusTotal database. Since Jamf ones Jamf Protect, maybe it can be updated and implemented to do a security audit of App Installers before they are released in production?
@thebrucecarter unfortunately there was an incompatibility between what I will call 'traditional code' and the 'new code' that App Installers uses which meant that at this time we were unable to use traditional static scoping mechanisms. We hope to address this in a future release of App installers.
Curious whether this was brought up in the BETA program at all?
FWIW I have raised https://ideas.jamf.com/ideas/JN-I-25934 bit disappointed that this feature does not follow the scoping format of the rest of the UI, especially in terms of static groups (we use these as rollout/testing groups) but hoping this could be implemented in the near future.
Are app Installers Only Available to Jamf Cloud Customers?
So, the App Installer implementation is stated only available to Jamf cloud subscription, but initially might work with on-premise subscriptions? Is there a technical reason why it will be only available to Jamf cloud customers? If there is a political or financial reason, seems like you could consider other options to allow the on-premise customers the ability to use it until their organization can consider moving to a Jamf Cloud implementation due to multiple reasons like issues with upload stability or automation with the installer package with Jamf Cloud, or security.
I have created a feature request, please vote it up if you need or would like it available to on-premise Jamf instances.
Since App Installers will not work for on-prem, couldn't you give everyone the ability to download the packages you build on what I assume is a CDN you manage. We would at least not need to go out and get the packages for the software to use them in Patch Management, like we currently do. I have a feature request open for this.