Forum Discussion
Does the Office 2019 share for local deployment grow each month and can it be tidied up?
Hi,
I couldn't find a specific Office 2019 community so I'm asking the question here. We are deploying office 2019 from a local share set-up by the Office deployment tool rather than clients going directly to the CDN. We want to keep this share updated with the latest setup files and monthly updates.
I have noticed that the share was initially around 2Gb then grew by 2GB the next month as it keeps a versioned folder for each update, e.g. 16.0.10340.20017 folder for the January 2019 updates then a 16.0.10341.20017 folder for the February updates.
Will this share continue to grow by 2GB each month when a new set of setup files is released? And why are the older versions kept? Are these needed to update \ service clients on that version? Can these older version folders be cleaned up?
Thanks,
Nigel
Thanks. We raised a call with Microsoft support and the ODT downloads a new version folder each month, e.g. Office\Data\16.0.10342.20010. It doesn't clean up previous version folders and each one is the latest copy of Office 2019 and around 2GB. We setup a scheduled task to run ODT to download the latest on the Wednesday after patch Tuesday and also delete old version folders (as you can safely do this). But we keep last month's version so this could be used for roll-back if the latest version breaks some functionality.
Nigel
2 Replies
Since you control the deployment process and the configuration files, you can delete any version not explicitly referenced in the config files. They might be needed for some users using the repair functionality, but you can always redownload them if you get too much of these.
Thanks. We raised a call with Microsoft support and the ODT downloads a new version folder each month, e.g. Office\Data\16.0.10342.20010. It doesn't clean up previous version folders and each one is the latest copy of Office 2019 and around 2GB. We setup a scheduled task to run ODT to download the latest on the Wednesday after patch Tuesday and also delete old version folders (as you can safely do this). But we keep last month's version so this could be used for roll-back if the latest version breaks some functionality.
Nigel
