Managed Software package

[Stephen Jaeger]

In building a Manged Software Delivery, I have noticed  under "Additional delivery options" Automatically upgrade software that has been superseded by this software" is greyed out and do not know why. Also using the same software package in a policy,  "Supercede Settings">Automatically upgrade software that has been superseded by this software is also greyed out.

------------------------------
Stephen Jaeger
------------------------------

[Arthur Prosso]

Hello Stephen!

Up to 8.6 RU3 "Automatically upgrade" option is NOT greyed out (both in the wizard and in an existing policy UI) only if there is a superseded component defined (pre-defined) for a component being included into the MD policy.  Just in case - supersedence associations  may be defined in the "Associations" tab in the "Software Release Edit "dialog - see below.

This behaviour will change in 8.7 and it will be possible to configure the product so that the supersedence options will always be checkable  regardless of the existing supersedence associations.
Regards,
Artur



------------------------------
Software Engineer 5
Broadcom Inc.
------------------------------

[Tal Fisher]

Hello Author when can we expect 8.7? I need the "Do not install if" box enabled. We deploy some executable apps that auto-update. We don't want Altiris to downgrade the application after we complete an Altiris agent upgrade.

[Mike Grueber]

ITMS 8.7 is planned for the first quarter of calendar year 2023.

[Arthur Prosso]

Hi Tal !
Mike has replied about release dates.
Just in case here is more clarification regarding the checkbox:
"Do not install..." will be checkable in your current ITMS release once you define the "is superseded" association MANUALLY ( see my 1st post) .

If there is no such an association then even if the check box were checkable that would not help.
The functionality does not work "out of box" on the client side, because in general case it is impossible to tell which component supersedes which - only manual definition on the server side will work.  Same situation will be in 8.7 further on. 
In 8.7 we will be fixing only the UI and "auto update" of policies for components that have undergone supersedence chain CHANGES on the background  (need to add/remove superseding components checks into the policy execution flow in the related policies).


Regards
Artur




------------------------------
Software Engineer 5
Broadcom Inc.
------------------------------

[Tal Fisher]

Yes, I read your past post.  I was under the impression that all I had to do was check that box and the policy would know exactly what to do. "only manual definition on the server side will work" makes sense as I tried the "supersede" method yesterday in my DEV environment.
 So it makes sense to me to keep the boxes grayed out. That way there is no misinterpretation and false expectation on how the "Additional delivery option works". 
By the way,  The ITMS 8.6 RU3 upgrade was the easiest and most effective upgrade I have seen in the last 8 years. Kudo to your team! Go team Broadcom!!! Any plans for an ITMS Sessions and Tech EXPO or Seminar?