Like the BITS technology, Delivery Optimization also have the concept of foreground and background jobs. Microsoft has all options listed here, and in what version of Windows 10 each option is available: In general, as of now, I recommend you to be at least on Windows 10 v1709, but from a core DO point of view, you probably want to be on Windows 10 v1803. The options vary with the Windows 10 version. Now, there is a ton of different configuration options for Delivery Optimizations, controlling how the peering works, the cache size allowed, and the bandwidth control. Phil Wilcock has great post about the Express installation files scenario here: ĭelivery Optimization is a peer to peer technology, meaning as soon as one Windows 10 client in a location got the content, it can share the content with other clients. DO is also used for Software Updates when they are setup to use Express installation files. DO is used whenever Windows 10 updates any of it's built-in universal apps, or when a user installs an application from either the Microsoft Store, or the Microsoft Store for Business. Delivery Optimization Backgroundĭelivery Optimization (DO) has been around since the very first versions of Windows 10, but it has not been until recently (ConfigMgr 1802) that you find some integration between DO and ConfigMgr. ![]() Note: The setup is almost the same for non-ConfigMgr environments as well, most of the DO configuration is done via Group Policies. Here is a quick guide on setting up Delivery Optimization (DO) for a ConfigMgr environment.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |