Forum Discussion
GlennG-TM
Jul 28, 2023Copper Contributor
Windows Server Delivery Optimization support for more products
Actually, obtaining "updates" is one of the most consuming network bandwith and a cost expensive thing often misrepresented in enterprise network architecture.
Since many years we always try to adapt or environment to put in place some mechanisms to reduce this comsuption like WSUS server, Branch Cache, proxy caching, etc. But recently Microsoft have changed some method to obtain many updates where we need to also change the "caching" method.
On Windows clients, it's somewhat not an issue. Using SCCM with Microsoft Connected Cache and Delivery Optimization (DO) it's cover almost Microsoft updates (including Windows, Edge, Office, UWP apps from Store, etc.)
On Windows Server, it's not the same thing!
Actually Windows Server doesn't offer the same DO support than Windows Client. Windows Server just receive "Edge and Windows" updates with a DO caching method.
We recently started to migrate our Office product from Office 2016 (MSI) where updates was provided by WSUS through Office 365 or Office 2021 LTSC (C2R) where updates are coming from Office CDN.
It seem Office 365 Apps Updates are not covered by Delivery Optimization on Windows Server platform like explained in the link below !!!
What is Delivery Optimization? - Windows Deployment | Microsoft Learn
We also in a migration phase for our antivirus to use Microsoft Defender. It's the same ting again. All Defender updates not seem to be using DO under Windows Server...
--------------------------
Then, my suggestion to Windows Dev Team is to innovate on that ! Please offer same Delivery Optimization for Windows Client and Windows Server.
- Deleted