From b81e72dbd9ba4a9a40a1f97f50d24eba75123b43 Mon Sep 17 00:00:00 2001 From: Bryan Dam Date: Fri, 25 Oct 2024 11:18:53 -0400 Subject: [PATCH] Add MCC DHCP Option Added a section here, possibly incomplete by your standards, that call out that there's a DHCP option to point endpoints at the MCC server. I think that's important to call out here in the MCC docs. --- windows/deployment/do/mcc-enterprise-appendix.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/windows/deployment/do/mcc-enterprise-appendix.md b/windows/deployment/do/mcc-enterprise-appendix.md index 0a0239d6908..15640f2efd6 100644 --- a/windows/deployment/do/mcc-enterprise-appendix.md +++ b/windows/deployment/do/mcc-enterprise-appendix.md @@ -111,6 +111,10 @@ You can either set your Connected Cache IP address or FQDN using: :::image type="content" source="./images/ent-mcc-group-policy-hostname.png" alt-text="Screenshot of the Group Policy editor showing the Cache Server Hostname Group Policy setting." lightbox="./images/ent-mcc-group-policy-hostname.png"::: +#### DHCP Option 235 + +To dynamically assign one or more Connected Cache hosts you can configure a custom DHCP option 235 to specify a comma-delimited list of host FQDNs or IP addresses. You must then configure a policy to apply to PCs that configures the DOCacheHostSource policy. For for information see [Delivery Optimization reference](/windows/deployment/do/waas-delivery-optimization-reference#cache-server-hostname-source). + ## Verify content using the DO client To verify that the Delivery Optimization client can download content using Connected Cache, you can use the following steps: