Skip to main content
Jamf Nation, hosted by Jamf, is a knowledgeable community of Apple-focused admins and Jamf users. Join us in person at the ninth annual Jamf Nation User Conference (JNUC) this November for three days of learning, laughter and IT love.

Replace in All Configurations Should Also Mean in Policies too

I update a package in Casper Admin, I "replace in all configurations", and then I usually delete off the old one \- which deletes it from self-service and any attached policies which I then have to reattach the new one I made.

It would be nice if replacement were global.

This behavior has been around for a while, but I am using 8.52

Comment
Order by:

Posted: by CasperSally

agree... and autorun data as well.

Like

Posted: by mm2270

As long as its an option, i.e, a checkbox you tick when using the 'Replace in All' function, then I would agree. There may be circumstances where you may not want it to replace the package in your policies as well.

Like

Posted: by HSICT

I actually assumed this was already part of the configuration. I noticed that the Apps I was pushing in Self-Service where still listed in policies \- but not working. To my horror I found the "Package" was empty in these because we had updated the version in Admin and retired the old version. Would definitely be great as an option.

Like

Posted: by jwojda

+1

Like

Posted: by bpavlov

This would certainly be nice behavior to have.

Like

Posted: by taugust04

What I would like:

In Casper Admin, right click on the "old" package. Below the option of "Replace in all configurations", I'd like a new option "Replace in policies...". From there, a window pops up with a list of each policy the old package is used in. At the top of the pop-up window is a pull-down menu where you select the "new" package. A check box is next to each policy, and I can replace the old package with the new package in any policy by selecting the check box. A second check box should be displayed to allow for duplicating the policy with the new package rather than doing a straight up repair, if the policy has been selected for a package replacement.

~Ted

Like

Posted: by Look

Absolutely!
It needs to be a seperate function but it would be great to have all Self Service policies updated automatically!

Like

Posted: by fedagain

100% Fully agree!! I was just talking about this!!!! This is a VERY needed feature! Thank you!!

Like

Posted: by BVikse

If we could get an implementation of the OP @mcrispin said that would be great, @taugust04 has the best idea though. That would save me a lot of time.

Like

Posted: by MikeF

Like

Posted: by RobertHammen

I've wanted this functionality for years. Would help automate some of the patch management mayhem, as well as keeping the JSS cleaner by allowing you to instantly delete older versions of apps without having to do the "find every policy that uses them and edit it to add the new package/delete the old one/remember to go delete the old package from the JSS" routine I've done literally thousands of times.

Like

Posted: by macbrun

Bump. Yes, yes, a thousand times yes! This is a feature that would save so much time!

Like

Posted: by blackholemac

With the death of nuke and pave imaging, this feature request is even more urgent.

I am right now trying to build my new provisioning scheme does away with Jamf Imaging entirely for the modern era.

It is going well but will likely become quite tedious as I need to swap out packages for substitute packages. Using the replace in all configurations was handy then. Now if I want to substitute a package, I will have to look everywhere that package is and modify each policy that uses it. Please vote this feature request up!

Like

Posted: by pkn

I assumed that replace in all configurations also meant policies too. This feature would be great to have.

Like

Posted: by bearzooka

Almost one year after the last one… BUMP!

Like

Posted: by bearzooka

Well, since I am doing this kind of tasks on a weekly basis, I did the nerdy thing and created PackageChanger

It can replace a package, on every policy it appears, for another package. Both need to be already uploaded to the JSS and it doesn't work on Patch Policies, unfortunately.

Like

Posted: by Initialised

It might seem odd if you've always kept version info in the file name but in most cases I get around this by removing version information from the file name using Metadata and Inventory to keep track of version numbers.

So when I update an App all I need to do is drag it into Jamf Admin and all policies related to this app automatically update.

Like

Jamf would like to hear your feedback around Restrictions payload (computers and devices)