I'm using Configuration Manager CB1511 to deploy Office 2016 to machines that already have either Office 2010 or 2013 installed.
The deployment is set to run whether or not a user is logged on.
If the deployment runs when a user is logged on and happens to have for example an open word document in the old office version, the deployment simply force-quits the open word application, not giving the user a chance to save their file, this is obviously not a good thing.
Is there any way around this? For example to have it prompt the user to save the document? Or perhaps not uninstall the old office version until next reboot?
I know I could set the application to only install when there is no logged on users, or during a maintenance window. For various reasons this would probably not work well in our current environment.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
I'm using Configuration Manager CB1511 to deploy Office 2016 to machines that already have either Office 2010 or 2013 installed.
The deployment is set to run whether or not a user is logged on.
If the deployment runs when a user is logged on and happens to have for example an open word document in the old office version, the deployment simply force-quits the open word application, not giving the user a chance to save their file, this is obviously not a good thing.
Is there any way around this? For example to have it prompt the user to save the document? Or perhaps not uninstall the old office version until next reboot?
I know I could set the application to only install when there is no logged on users, or during a maintenance window. For various reasons this would probably not work well in our current environment.
Share this post
Link to post
Share on other sites