Application Group reboot behaviour
Given a scenario of an application group which contains more than one application: if any application in that group requires a reboot the whole application group is terminated with an error (AppGroupHandler - InternalProcessAppRules failed with error 0x87d0032e) even though the application which demanded the reboot was installed correctly.
The expected behaviour is to perform the reboot and then continue with the next application in line in the application group after the reboot.
It would be beneficial if any reboot request in the application group process were internally remembered and only one reboot request would be sent to the user after the completetion of the whole application group.
It would be even better if any application in an application group could demand a reboot and the request would be sent to the user. After the user reboots the machine the application group should then continue with the next application in line.
For me, I think that an Application Group should allow for a setting that defers the reboot until the entire group has processed, similar to how Software Updates defer a reboot until all the updates have applied. I am on the fence if this should be the default behavior or an option. I feel that applications that need an immediate reboot are better suited for a Task Sequence than an Application Group.