Yes, the title is unclear, but I didn't know how to phrase it briefly.
I was wondering if it was possible to apply packages with a "from near to far" priority order without the far-flung configuration overwriting the near-flung configuration?
Since this is still not clear, let me explain:
I have a package deployed across an entire OU, but I have one (or more) machines that are exceptions. Don't look at me sideways; we all have exceptions
. So I stupidly thought I'd just put the conflicting package on the machine. That was indeed stupid because it doesn't work. So here I am, asking if we could implement a "nearest to furthest" priority system for package application.
A concrete example:
I am installing Acrobat Reader across an entire OU, but some machines have a package of an older version of Acrobat Pro (which therefore does not depend on the same installer).
In my case, I could therefore put Acrobat Reader in conflict with my Acrobat Pro package without this generating errors or repeated uninstallation/reinstallation.
My current solution is to modify the Acrobat Reader package and put the exceptions there, which is ugly and not very sustainable...
Code: Select all
if already_installed == True:
if installed_version =="{AC76BA86-1033-FFFF-7760-0E0F06755100}":
print("Acrobat 2015")
elif installed_version == '{AC76BA86-1033-FFFF-7760-0E1401753200}':
print("Acrobat 2017")
elif installed_version =='{AC76BA86-1033-FFFF-7760-0E1401753200}':
print("Acrobat 2020")
elif installed_version == '{AC76BA86-1033-FF00-7760-BC15014EA700}':
print("Reader DC ou Acrobat DC")
return "OK"
else:
return "WARNING"
Thank you for your feedback
Good day
