Ability to control Application Deployment Policy failed update response

Avatar
Randall Kender

Currently when a host pool has an application that needs and update as part of an Application Deployment Policy, if the update fails for any reason the action to uninstall is attempted following a re-install. There is no option to change this logic.

This can be disruptive in my cases where repeated installs may consume a license, or mess with agent functionality in various systems (duplicate objects). This can also be a problem if the policy is allowed to run while a user is logged into the machine, as it would be more desirable to have an out-of-date application rather than triggering an uninstall that may then fail the re-install, since that would mean the users would lose all access to the application.

Please create an option to allow control of the behavior so that we can specify if the uninstall is triggered, or if a warning/error is thrown and no further action is taken. Ideally this could be specified in the deployment policy, but even an option under Advanced App Service Environmental Variables would be ok.

0

Comments (2 comments)

Sort by
0
Avatar
Toby Skerritt
(Edited )

Hi Randall Kender , thanks for this suggestion. Your issue with app uninstalls is noted, i will raise it with the dev team.

It doesn't fix the issue, but we do offer the option to restrict scenarios where apps would be modified via the ‘desired host state’ control. This wont remediate failed installs, but it will prevent changes happening while users are logged on. You may be aware of this option already, but if not, I hope its useful.

0
Avatar
Randall Kender

Thank you for the reply. Yes, I am aware of this setting, but the issue is that we allow week-long sessions (and for some no forced log off), so only doing updates when users are logged off becomes problematic. We like to use the maintenance window and do them nightly.

Please sign in to leave a comment.