From c069ce9408a584269f8724a76a53f3225035277a Mon Sep 17 00:00:00 2001 From: "Chris J. Lin" <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 21 Nov 2024 16:13:53 -0800 Subject: [PATCH] Update mcc-ent-deploy-to-windows.md Revising note about where the provisioning package should be extracted to on the host machine --- windows/deployment/do/mcc-ent-deploy-to-windows.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md index be4f2d9a64..e1ff1c2af4 100644 --- a/windows/deployment/do/mcc-ent-deploy-to-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -26,7 +26,11 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host # [Azure portal](#tab/portal) 1. Within the Azure portal, navigate to the **Provisioning** tab of your cache node and copy the provisioning command. -1. Download the provisioning package using the option at the top of the Cache Node Configuration page and extract the package onto the host machine. **Note**: The installer should be in a folder that isn't synced to OneDrive, as this will interfere with the installation process. +1. Download the provisioning package using the option at the top of the Cache Node Configuration page and extract the archive onto the host machine. + + >[!Note] + >* The provisioning package should be extracted to a directory that isn't synced to OneDrive, as the sychronization process will interfere with the installation. It is recommended to extract the provisioning package to the root directory of the host machine (e.g. C:\mccInstaller) + 1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Set the Execution Policy to *Unrestricted* to allow the provisioning scripts to run. 1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account.