Forum Discussion
Christopher Hadwin
Jan 12, 2018Copper Contributor
Office 365 Pro Plus - Closes All Office apps when updates are deployed
We are currently testing Office 365 Pro Plus in hopes to replace the Office 2016 MSI install. We have Office 365 Pro Plus deployed as follows :
<Configuration>
<Add OfficeClientEdition="32" Channel="Current" Version="16.0.8625.2132" OfficeMgmtCOM="True">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="OneDrive" />
</Product>
</Add>
<Display AcceptEULA="TRUE" />
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="FALSE" />
<Property Name="AUTOACTIVATE" Value="1" />
<Property Name="ForceAppShutdown" Value="FALSE" />
</Configuration>
We have updates being pushed through configuration manager. The updates get passed the machine and when they go to install the updates, it forces all office applications to close without any notification to the user. This is problematic esp since we are a SfB house. We have a SCCM DSE that i've ran this through and we've troubleshot this for a few days but we can't really find a way to either have the updates installed WITHOUT closing the apps or notify the user that the applications need to close in order to apply the update.
Has anyone see this behavior before? Any suggestions to get the outcome that we desire?
- itvinaybhattCopper Contributor
I hope this will help you, change the XML for FOREAPPSHUTDONW to below:
<Property Name="FORCEAPPSHUTDOWN" Value="FALSE"/> <!-- Setting to FALSE for user intervention --> - Andrew PriceBrass ContributorAny luck with this?
- Christopher HadwinCopper Contributor
We have a ticket open about this, our TAM is involved and our SCCM DSE is involved. If/when we find a resolution, i'll be happy to share it on here.
- JohnGruszczyk
Microsoft
Hi Christopher - interesting bug you're running into. Would it be possible for you to run a small scale (~1-5 machine) test for me? You can force call the Office update mechanism and then specify during that call to not force apps to shutdown, I wonder if that could potentially resolve the issue you're seeing. It wouldn't be a fix, but at least can give us more detail into what's happening
https://docs.microsoft.com/en-us/deployoffice/best-practices/best-practices-channel-management
See specifically the section "Use OfficeC2RClient.exe" for the variables. If you know there's an Office update available, just run it with your normal experience + forceappshutdown = false and see what happens. You can even do this on a VM or test machine that's configured the same as your normal ConfigMgr devices
- Andrew PriceBrass Contributor
Interesting, I can see you have not enabled ForceAppShutdown. As a troubleshoot step can you try hashing out that line to see if that makes any difference.
<-- <Property Name="ForceAppShutdown" Value="FALSE" /> -->
Also I can see you dont have any DisplayLevel defined so many update your AcceptEULA line to look like this.
<Display Level="Full" AcceptEULA="TRUE" />
- Christopher HadwinCopper Contributor
Thanks for the reply Andrew. I have tried it using with and without the ForceAppShutdown=true line in it. Matter of fact, we've first found this issue without that line in the config.xml file.
I will update the display level in the config.xml file and try it again. Thanks for the suggestion.