Hello!
following scenario:
You have an application created in PMP, lets say it's the common Microsoft App "Powertoys".
You allow your IT Admins to add groups to this App via INTUNE.
Your IT Admins add some groups as REQUIRED for Install.
There is a new version for that app that is automatically added via Publisher.
You have configured the app so it copies all the assignments to the new app version.
Now in Intune, there will be a new app package and it will also likely contain the REQUIRED assignments.
-> What will happen now? The clients will instantly receive the new app version because it is now assigned as REQUIRED just like the previous app version.
Our question is, how can we prevent this? We don't want all the clients to instantly receive the new update because that's the task of the "Update for" packages, that will also automatically be created.
The update package is configured with deferal times, similar to a ring deployment concept. This is done by adding availability times in the config in PMP.
When PMP automatically creates a new app package and copies all the required assignments from the old version, this behavior destroys the update concept of the app and rather than a ring deployment, we suddenly have a big bang update.
Is there any way to tackle this?
Regards, Dominic
following scenario:
You have an application created in PMP, lets say it's the common Microsoft App "Powertoys".
You allow your IT Admins to add groups to this App via INTUNE.
Your IT Admins add some groups as REQUIRED for Install.
There is a new version for that app that is automatically added via Publisher.
You have configured the app so it copies all the assignments to the new app version.
Now in Intune, there will be a new app package and it will also likely contain the REQUIRED assignments.
-> What will happen now? The clients will instantly receive the new app version because it is now assigned as REQUIRED just like the previous app version.
Our question is, how can we prevent this? We don't want all the clients to instantly receive the new update because that's the task of the "Update for" packages, that will also automatically be created.
The update package is configured with deferal times, similar to a ring deployment concept. This is done by adding availability times in the config in PMP.
When PMP automatically creates a new app package and copies all the required assignments from the old version, this behavior destroys the update concept of the app and rather than a ring deployment, we suddenly have a big bang update.
Is there any way to tackle this?
Regards, Dominic