Upgrade software through existing pology?

If you go to Settings > Computer Management > Packages and select the package, you can edit it by removing the existing file and dragging and dropping the new package in its place. This will automatically update any associated policies. After that, go to the policy, open the Logs tab, and click ‘Flush All’ to trigger a redeployment.

You can test this before Flushing All by flushing the policy only on your test device.

Inheriting a management instance is always an interesting time!

First, I’m assuming that your title is a typo (I think that Pology is a typo for policy but found that indeed, Pology is a set of Python command line tools… so I’ll let you correct me if Ithat’s the case). In any event, we need to understand the intention policy, the specific scope and any needs the package being deployed might have. 

Whatever the overall scope is, it looks like a simple install of a package without waiting, fanfare, or questions. I’ve seen this plenty of times with required software on new machines. The question is, do you want it to use the updated package moving forward for computers that haven’t yet run the policy, or do you ALSO want to upgrade everyone that has already has it installed? If it’s the former, then yea, just loading up the .pkg will install that one moving forward. If it’s the latter then you’ve got a few more questions. 

Otherwise you need to know if the software .pkg is ready to go right from download. Sometimes software installers need to be customized for various reasons. I don’t see any scripts mentioned in this policy, so whatever the .pkg is, it’s handling everything it seems to need on its own. 

If you could give a little more detail on the intention of the policy, it would help me be more specific. 

I updated the package, made sure it was showing in the policy. Did the flush logs and will see what the software inventory shows in a few days.

Thanks!

Personally, I would leave your current policy. Duplicate it. 

Once the policy is duplicated, change the scope to only test computers and change the desired package and any other payloads. I’d also download your new package and run it through this app. Once testing goes well, move forward with your scope.

Repeat for new updates.

You may need logs later, or a history of bread crumbs. So I wouldn’t recycle 1 policy over and over. Can always clean up later.