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

Merge pull request #10762 from MicrosoftDocs/main

Browse Source 
Publish main to live, 04/09/25, 3:30 PM PDT
This commit is contained in:
Ruchika Mittal
2025-04-10 04:01:14 +05:30
committed by GitHub
parent a9475793a2 f7bc770b19
commit 90c5c50a37
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -28,7 +28,7 @@ Before deploying Connected Cache to a Linux host machine, ensure that the host m
1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
>[!Note] >[!Note]
>* If you are deploying your cache node to a Linux host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add `proxyTlsCertificatePath="/path/to/pem/file"` to the provisioning command. >* If you're deploying your cache node to a host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and then add `proxytlscertificatepath="/path/to/pem/file"` to the provisioning command.
1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute. 1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
1. Run the provisioning command on the host machine. 1. Run the provisioning command on the host machine.
@ -48,7 +48,7 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
> [!Note] > [!Note]
>* If you are deploying your cache node to a host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and add `proxyTlsCertificatePath="/path/to/pem/file"` to the provisioning command. >* If you're deploying your cache node to a host machine that uses a TLS-inspecting proxy (e.g. ZScaler), ensure that you've [configured the proxy settings](mcc-ent-create-resource-and-cache.md#proxy-settings) for your cache node, then place the proxy certificate file (.pem) in the extracted provisioning package directory and then add `proxytlscertificatepath="/path/to/pem/file"` to the provisioning command.
1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute. 1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
1. Replace the values in the following provisioning command before running it on the host machine. 1. Replace the values in the following provisioning command before running it on the host machine.