From 3a8faa199f352f3a86a0d829b8b4267cbdf2207b Mon Sep 17 00:00:00 2001
From: chrisjlin <36452239+chrisjlin@users.noreply.github.com>
Date: Thu, 24 Oct 2024 18:06:53 -0700
Subject: [PATCH] Added steps to point clients at nodes

---
 windows/deployment/do/mcc-ent-deploy-to-linux.md   | 6 ++++++
 windows/deployment/do/mcc-ent-deploy-to-windows.md | 6 ++++++
 2 files changed, 12 insertions(+)

diff --git a/windows/deployment/do/mcc-ent-deploy-to-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md
index 8385641122..d674b4e504 100644
--- a/windows/deployment/do/mcc-ent-deploy-to-linux.md
+++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md
@@ -49,6 +49,12 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
    sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="enter true if present, enter false if not" proxyurl=http://enter proxy hostname:enter port
    ```
 
+## Steps to point Windows client devices at Connnected Cache node
+
+Once you have successfully deployed Connected Cache to your Linux host machine, you will need to configure your Windows client device(s) to request Microsoft content from the Connected Cache node.
+
+You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname).
+
 ## Next step
 
 > [!div class="nextstepaction"]
diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md
index 68720ee8fa..68077a256f 100644
--- a/windows/deployment/do/mcc-ent-deploy-to-windows.md
+++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md
@@ -59,6 +59,12 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
    ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid [enter mccResourceId here] -cachenodeid [enter cacheNodeId here] -customerkey [enter customerKey here] -registrationkey [enter registration key] -cacheDrives "/var/mcc,enter drive size"  -shouldUseProxy [enter true if present, enter false if not] -proxyurl "http://[enter proxy host name]:[enter port]"  -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential
    ```
 
+## Steps to point Windows client devices at Connnected Cache node
+
+Once you have successfully deployed Connected Cache to your Windows host machine, you will need to configure your Windows client device(s) to request Microsoft content from the Connected Cache node.
+
+You can do this by setting the [DOCacheHost or DOCacheHostSource policies via Intune](./waas-delivery-optimization-reference.md#cache-server-hostname).
+
 ## Next step
 
 > [!div class="nextstepaction"]