deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-14 22:37:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Correcting syntax for pem file parameters

Browse Source
This commit is contained in:
chrisjlin 2024-11-21 17:07:23 -08:00
parent 37751bd7af
commit ecdd05bca3
2 changed files with 4 additions and 4 deletions
Show Stats 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 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 certificate]` to the provisioning command. >* 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.
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 certificate]` to the provisioning command. >* 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.
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.

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

@ -34,7 +34,7 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host
1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Open a PowerShell 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 `-proxyTlsCertificatePemFileName [path to certificate]` to the provisioning command. >* 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 `-proxyTlsCertificatePemFileName "path/to/pem/file"` to the provisioning command.
1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run. 1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run.
1. Create a `$User` PowerShell variable containing the username of the account you intend to designate as the Connected Cache runtime account. 1. Create a `$User` PowerShell variable containing the username of the account you intend to designate as the Connected Cache runtime account.
@ -67,7 +67,7 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Open a PowerShell 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 certificate]` to the provisioning command. >* 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.
1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run. 1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run.
1. Create a `$User` PowerShell variable containing the username of the account you intend to designate as the Connected Cache runtime account. 1. Create a `$User` PowerShell variable containing the username of the account you intend to designate as the Connected Cache runtime account.