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

Update mcc-ent-deploy-to-windows.md

Browse Source 
Revising note about where the provisioning package should be extracted to on the host machine
This commit is contained in:
Chris J. Lin 2024-11-21 16:13:53 -08:00 committed by GitHub
parent 849f540f37
commit c069ce9408
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -26,7 +26,11 @@ Before deploying Connected Cache to a Windows host machine, ensure that the host
# [Azure portal](#tab/portal) # [Azure portal](#tab/portal)
1. Within the Azure portal, navigate to the **Provisioning** tab of your cache node and copy the provisioning command. 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. 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. 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. 1. Create a `$User` environment variable containing the username of the account you intend to designate as the Connected Cache runtime account.