Configuring Delivery Optimization
Last updated
Last updated
Since Windows 10, Microsoft has included Delivery Optimization (DO) as a built-in component in Windows. DO is used for downloading content in which it can be downloaded from a peer or a caching server. Microsoft has provided administrators several ways to manage DO configuration on clients, which includes Group Policy (Active Directory / Intune) and Client Settings in Configuration Manager. When using StifleR to manage content downloads, it is important that existing configuration settings do not conflict with StifleR's configuration.
StifleR configures DO using Templates. Templates are applied to Network Groups and Network Groups can include one or more subnets. Think of these as peering groups. DO also uses the concept of peering groups which are referenced as DO Groups. Using Templates, StifleR can define DO Groups based on Network Groups which includes specific settings. For more information on which DO settings can be managed by StifleR, see this table.
Microsoft provides administrators the ability to manage Delivery Optimization settings using Group Policy via Active Directory or Intune. Using AD or Intune policies to manage DO can conflict with StifleR's ability to manage DO settings on the StifleR client. It is generally recommended to review the policies and remove any which may conflict with StifleR. For more information on which DO settings can be managed by StifleR, see this table.
StifleR is designed to manage Delivery Optimization peering groups based on how networks are defined in StifleR. When implementing StifleR in a Configuration Manager environment, it is important to disable the Client Setting: Delivery Optimization: Use Configuration Manager Boundary Groups for Delivery Optimization Group ID.
