Skip to main content

Hi all,

 

We are having an issue whereby our Office 365 updates are forcing apps to close and restart. This is happening to some VIP users and as a result they are complaining to IT about applications closing on them. Whilst this mostly recovers, the disruption whilst working is not ideal and it also doesn’t recover things like Mimecast searches (within Outlook via the addin). 

 

We would therefore like to approach this with a separate worklet or update policy to update just Office365. 

 

Does anybody have any recommendations on this one? Perhaps a Worklet whereby I can trigger a notification that the application will update in X minutes, and provide a user-friendly warning to the user (if it detects that the office apps are open). Alternatively, if we can update but not restart the app, and then apply the changes on the next restart of the apps (or device) that would be ideal. 

 

Thanks in advance! 

Hi ​@Marshyp, we have been patching this for VIP users using sperate patch only policies. We included all the apps in policy that requires app restart or need to be closed before update runs. 

Thanks, 

Think I’ve got this nailed now. Created a bespoke Worklet to detect the pending update and then remediate with a suppressed update command: 

OfficeC2RClient.exe /update user displaylevel=false forceappshutdown=false

On current testing, it seems to have done the trick nicely, but will see how wider testing goes tomorrow. 

Hi ​@Marshyp, ​@Maulik_Busa has pointed out one option for accomplishing this, a patch only with install notifications on and a deadline so the users have time to save their work.

Alternatively, you can use the Third-Party Override Worklet and follow the instructions in the readme text to add the apps to the $killIfRunningFALSE variable and schedule it so that it runs before your patching policy so that those apps don’t close automatically when patching. 

These are also good articles to reference for finding out supported applications behavior when patching and for finding the cached package name.

Hopefully that helps!

Terms & ConditionsCookie settingsAccessibility statement