You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/plan-design/hierarchy/client-peer-cache.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Peer cache doesn't replace the use of other solutions like Windows BranchCache o
43
43
44
44
## Operations
45
45
46
-
To enable peer cache, deploy the [client settings](#bkmk_settings) to a collection. Then members of that collection act as a peer cache source for other clients in the same boundary group.
46
+
To enable peer cache, deploy the [client settings](#client-settings) to a collection. Then members of that collection act as a peer cache source for other clients in the same boundary group.
47
47
48
48
- A client that operates as a peer content source submits a list of available cached content to its management point using state messages. A peer content source client also sends a state message to the management point when it removes content from its local cache.
0 commit comments