deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-14 01:53:21 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
windows-itpro-docs/windows/deployment/do/mcc-ent-deploy-to-windows.md
chrisjlin 38df7f3984 fixes broken links
2024-09-30 11:53:05 -07:00

3.0 KiB
Raw Blame History

title, description, author, ms.author, manager, ms.service, ms.subservice, ms.topic, ms.date, appliesto
title description author ms.author manager ms.service ms.subservice ms.topic ms.date appliesto
Deploy MCCE cache software to a Windows host machine Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) cache software to a Windows host machine. chrisjlin lichris naengler windows-client itpro-updates how-to 09/27/2024
✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>

Deploy MCCE cache node to a Windows host machine

This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Windows host machine.

Deploying MCCE to a Windows host machine requires designating a Group Managed Service Account (gMSA) or a Local User Account as the MCCE runtime account. This prevents tampering with the MCC container and the cached content on the host machine.

Before deploying MCCE to a Windows host machine, ensure that the host machine meets all requirements, and that you have created and configured your MCC Azure resource.

Steps to deploy MCCE cache node to Windows

  1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
  2. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.
  3. Open a PowerShell windows as administrator on the host machine, then change directory to the extracted provisioning package.
  4. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run.
  5. Create a $User environment variable containing the username of the account you intend to designate as the MCC runtime account. For gMSAs, the value should be formatted as "Domain\Username$". For Local User accounts, $User should be formatted as "LocalMachineName\Username".
    • If you're using a Local User account as the MCCE runtime account, you'll also need to create a PSCredential Object named $myLocalAccountCredential.
  6. Run the provisioning command on the host machine.

Next step

[!div class="nextstepaction"] Verify cache node functionality

Related content