Forum Discussion
UpdatePath Office 365
- Aug 06, 2019
gustavo _ Yamamoto Couple of additional thoughts... If the machines are relatively recent Windows 10 versions you can look at new technologies built into Windows like Delivery Optimization. In this way, the computers would be all be configured the same in terms of Office but you would group the Windows 10 machines so they would share content "peer-to-peer". So maybe one machine downloads from CDN by subnet and others share that kind of thing.
If you don't think that's an option, you could DFS-N\DFS-R to have a common namespace like \\Office365\SAC and the clients would then be referred to a local file server to obtain content. This would greatly simplify effort in not having to maintain 70 different GPO's by site. (If I recall these configurations were stored in AD in terms of sites)
Dear friend, I read your two posts informing about office 365 update, but couldn't find my specific case there, I will use a GPO (ADMX) to control the updates of my company, but I have 70 branches scattered here in Brazil, and I would like that when the computers are in the branches, I change the registry keys to look for branch servers updates.
gustavo _ Yamamoto Couple of additional thoughts... If the machines are relatively recent Windows 10 versions you can look at new technologies built into Windows like Delivery Optimization. In this way, the computers would be all be configured the same in terms of Office but you would group the Windows 10 machines so they would share content "peer-to-peer". So maybe one machine downloads from CDN by subnet and others share that kind of thing.
If you don't think that's an option, you could DFS-N\DFS-R to have a common namespace like \\Office365\SAC and the clients would then be referred to a local file server to obtain content. This would greatly simplify effort in not having to maintain 70 different GPO's by site. (If I recall these configurations were stored in AD in terms of sites)