Would like to understand how are you guys handling Office 365 updates monthly. We are using the ODT configuration.xml and downloading the update package from a DFS share. Our requirement is that we would like the end users to keep working on office till the time the updates are downloaded in the background and notify them before applying the update so that they can save any work and close the file to apply the update
As of now the users are notified after taking the action to close any office apps, and the download and apply is handled by the same action. Thus there is a substantial downtime when the update files are getting downloaded following by the applying of the same. We would want our users to work on office till the time the updates are getting downloaded and close only when the updates are getting applied the same way Click2Run updates work.
We were not able to find a fixlet for O365, the final execution of the deployment depends on the odt.exe. I will try the suggested option, however unsure if this would work. As I understand, following your recommendation the package will first get downloaded into the buffer directory and then based on the time set by an admin it will apply the action. However, it is only one action doing it all, how do we isolate the download and the applying task?
Let me try your recommendation and get back to you with the results.
However, it is only one action doing it all, how do we isolate the download and the applying task?
You may want to check the File Pre-Cache Wizard (under BES Support site â Wizards).
Itâs able to generate pre-cache task (this is the download part) for those fixlets you want to deploy.
So you can use this task as the âdownloadâ action.
Once the task finishes, you can deploy the original fixlets as âapplyâ.
This is just another way to solve the long download time problem.
