Policy Install ApplicationX needs to have the old package replaced with the new one.Once the new version is approved for production, the following needs to be updated: This does not affect the other existing policies. When a package of a new version of ApplicationX is available, say version X.Z.0, a new policy ApplicationX vX.Z.0 is created by AutoPkg/JSSImporter. So that the volunteer Testers see all software (untested or in production), by default it is populated as follows:įiles & Processes: Execute Command: jamf policy -event ApplicationX-installĬomputer Groups: ApplicationX auto-updateĬomputer Groups: ApplicationX current version installedĬomputer Groups: ApplicationX test version installed They may decide to include All Computers, or a subset of their users. The contents of this smart group will be determined by our customers. This group is for computers on which ApplicationX should be made available. Smart groups Smart Group 3: “ApplicationX users” The most efficient way to manage this is with 6 policies and 5 smart groups: Then what? Well, then we can remove the testing policy until the next release is imported by AutoPkg, but we need policies that allow for self-service installation, update and removal, as well as managed installation and update.
0 Comments
Leave a Reply. |