deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 02:13:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Added steps to point clients at nodes

Browse Source
This commit is contained in:
chrisjlin
2024-10-24 18:06:53 -07:00
parent 196739d6d9
commit 3a8faa199f
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
windows/deployment/do/mcc-ent-deploy-to-linux.md
View File

@ -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"]

6
windows/deployment/do/mcc-ent-deploy-to-windows.md
View File

@ -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"]