Delivery Optimization configuration

Timeline

From the capture of 18 Oct 23:34 UTC

14 undated sections
7 with conditions

Settings and overrides named on this page

Registry values, policies and cmdlets the source mentions, with the dated steps that name them. Read the source for the values to set.

DelayBackgroundDownloadFromHttp
DelayCacheServerFallbackBackground
DelayCacheServerFallbackForeground
DelayForegroundDownloadFromHttp
MaxCacheAge
MinFileSizeToCache

Requirements, exceptions and scope

1. Prerequisites to allow Delivery Optimization communicationRequirement1 condition1 passage
Delivery Optimization (DO) is used to download Microsoft content from different sources (HTTP source, peers, and/or dedicated cache solution). It requires communication between the DO…
ProxyRequirement1 passage
PortsRequirement2 conditions2 passages
2. Evaluate Delivery Optimization policiesRecommendation1 passage
Wide area network (WAN)ExceptionScope1 passage
GroupIDSource default behaviorScopeRecommendation1 passage
Restrict peer selectionRequirement2 conditions1 passage
2b. Organization sizeRecommendation1 passage
Minimum file size to cacheException1 condition1 passage
Disk sizeRequirement1 passage
2d. Improve P2P efficiencyException1 passage
Bandwidth throttling optionsExceptionRecommendation1 condition2 passages
3. Using Connected CacheScopeRecommendation2 conditions2 passages
DelayCacheServerFallbackBackgroundDelayCacheServerFallbackForeground
Summary of basic configuration recommendationsRecommendation6 passages
MinFileSizeToCacheMaxCacheAgeDelayBackgroundDownloadFromHttpDelayForegroundDownloadFromHttpDelayCacheServerFallbackBackgroundDelayCacheServerFallbackForeground

Extracted automatically from Microsoft's wording. Confirm dates, conditions and whether they apply to you in the source before acting; a month or quarter is a window, not a day.

Observed history and review priority

Captured 18 Oct 23:34 UTC; extracted 18 Oct 23:34 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c.

Review priority. Extracted assertions require review · Applicability or exceptions require review

0 date changes and 0 condition changes across 0 compared revisions. Suggested check interval: 24 hours.

Earlier unavailable versions and edits between checks are unknown. A missing statement requires review; it does not mean the policy was cancelled. Recovered historical statements are not original revision snapshots.

Retained observations · 2

Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.

18 Oct 23:34 UTC · 24 candidates
6 Oct 16:41 UTC · 22 candidates