From d226b8e8babd0a7dd4e212a5d2c4acf5d7eadbe2 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 27 Sep 2024 13:29:12 -0700 Subject: [PATCH 01/12] lichris-docs-1 --- windows/deployment/do/TOC.yml | 12 ++- .../do/mcc-enterprise-deploy-linux.md | 38 +++++++++ .../do/mcc-enterprise-deploy-windows.md | 44 ++++++++++ .../do/mcc-enterprise-prerequisites.md | 82 +++++++++++-------- .../deployment/do/mcc-enterprise-uninstall.md | 35 ++++++++ .../do/mcc-enterprise-update-uninstall.md | 55 ------------- .../do/mcc-enterprise-verify-functionality.md | 46 +++++++++++ 7 files changed, 219 insertions(+), 93 deletions(-) create mode 100644 windows/deployment/do/mcc-enterprise-deploy-linux.md create mode 100644 windows/deployment/do/mcc-enterprise-deploy-windows.md create mode 100644 windows/deployment/do/mcc-enterprise-uninstall.md delete mode 100644 windows/deployment/do/mcc-enterprise-update-uninstall.md create mode 100644 windows/deployment/do/mcc-enterprise-verify-functionality.md diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index fe1b2a0cf3..1626b529e9 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -39,10 +39,14 @@ href: mcc-ent-edu-overview.md - name: Requirements href: mcc-enterprise-prerequisites.md - - name: Deploy Microsoft Connected Cache - href: mcc-enterprise-deploy.md - - name: Update or uninstall MCC - href: mcc-enterprise-update-uninstall.md + - name: Deploy Microsoft Connected Cache to Windows + href: mcc-enterprise-deploy-windows.md + - name: Deploy Microsoft Connected Cache to Linux + href: mcc-enterprise-deploy-linux.md + - name: Verify cache node functionality + href: mcc-enterprise-verify-functionality.md + - name: Uninstall MCC + href: mcc-enterprise-uninstall.md - name: Appendix href: mcc-enterprise-appendix.md - name: MCC for ISPs diff --git a/windows/deployment/do/mcc-enterprise-deploy-linux.md b/windows/deployment/do/mcc-enterprise-deploy-linux.md new file mode 100644 index 0000000000..a4c836b19f --- /dev/null +++ b/windows/deployment/do/mcc-enterprise-deploy-linux.md @@ -0,0 +1,38 @@ +--- +title: Deploy cache software to a Linux host machine +description: How to deploy Microsoft Connected Cache for Enterprise and Education cache software to a Linux host machine. +author: chrisjlin +ms.author: lichris +manager: naengler +ms.service: windows-client +ms.subservice: itpro-updates +ms.topic: how-to +ms.date: 09/27/2024 +appliesto: +- ✅ Supported Linux distributions +- ✅ Microsoft Connected Cache for Enterprise and Education +--- + +# Deploy your Connected Cache to a Linux host machine + +This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Linux host machine. + +Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md) and you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). + +## Steps to deploy MCCE to Linux + +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 button at the top of the Cache Node Configuration page and extract the package onto the host machine. +1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package. +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. + +## Next step + +> [!div class="nextstepaction"] +> [Verify cache node functionality](mcc-enterprise-verify-functionality.md) + +## Related content + +- [Deploy to a Windows host machine](mcc-enterprise-deploy-windows.md) +- [Uninstall MCCE](mcc-enterprise-uninstall.md) \ No newline at end of file diff --git a/windows/deployment/do/mcc-enterprise-deploy-windows.md b/windows/deployment/do/mcc-enterprise-deploy-windows.md new file mode 100644 index 0000000000..e640d0f7c3 --- /dev/null +++ b/windows/deployment/do/mcc-enterprise-deploy-windows.md @@ -0,0 +1,44 @@ +--- +title: Deploy cache software to a Windows host machine +description: How to deploy Microsoft Connected Cache for Enterprise and Education cache software to a Windows host machine. +author: chrisjlin +ms.author: lichris +manager: naengler +ms.service: windows-client +ms.subservice: itpro-updates +ms.topic: how-to +ms.date: 09/27/2024 +appliesto: +- ✅ Windows 11 +- ✅ Microsoft Connected Cache for Enterprise and Education +--- + +# Deploy your Connected Cache 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 relies on [Windows Subsystem for Linux (WSL)](https://learn.microsoft.com/en-us/windows/wsl/about) being installed under a [Group Managed Service Account (gMSA)](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or [Local User Account](https://support.microsoft.com/en-us/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) to isolate execution of the WSL-Microsoft Connected Cache distribution from the other users on the machine. This helps prevent tampering with both the WSL-MCC process and the cached content that is hosted on the disk. + +Before deploying MCCE to a Windows host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md) and you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). + +## Steps to deploy MCCE to Windows + +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 button at the top of the Cache Node Configuration page and extract the package onto the host machine. +1. Open a PowerShell windows *as administrator* on the host machine, then change directory to the extracted provisioning package. +1. Set the Execution Policy to "Unrestricted" to allow the provisoning scripts to run. +1. 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 are using a Local User account as the MCCE runtime account, you will also need to create a [PS Credential Object](https://learn.microsoft.com/en-us/dotnet/api/system.management.automation.pscredential?view=powershellsdk-7.4.0) named `$myLocalAccountCredential`. +1. Run the provisioning command on the host machine. + +## Next step + +> [!div class="nextstepaction"] +> [Verify cache node functionality](mcc-enterprise-verify-functionality.md) + + + +## Related content + +- [Deploy to a Linux host machine](mcc-enterprise-deploy-linux.md) +- [Uninstall MCCE](mcc-enterprise-uninstall.md) \ No newline at end of file diff --git a/windows/deployment/do/mcc-enterprise-prerequisites.md b/windows/deployment/do/mcc-enterprise-prerequisites.md index 1e33e85158..54e924692e 100644 --- a/windows/deployment/do/mcc-enterprise-prerequisites.md +++ b/windows/deployment/do/mcc-enterprise-prerequisites.md @@ -1,60 +1,74 @@ --- title: Requirements for MCC for Enterprise and Education -description: Overview of prerequisites and recommendations for using Microsoft Connected Cache (MCC) for Enterprise and Education. +description: Overview of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE). ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual -ms.author: carmenf -author: cmknox -manager: aaroncz -ms.reviewer: mstewart -ms.collection: tier3 +ms.author: lichris +author: chrisjlin +manager: naengler appliesto: - ✅ Windows 11 -- ✅ Windows 10 -- - ✅ Microsoft Connected Cache for Enterprise and Education -ms.date: 05/23/2024 +- ✅ Microsoft Connected Cache for Enterprise and Education +ms.date: 09/27/2024 --- -# Requirements of Microsoft Connected Cache for Enterprise and Education (early preview) +# Microsoft Connected Cache for Enterprise and Education Requirements (Public Preview) -> [!NOTE] -> As we near the release of public preview, we have paused onboarding. Please continue to submit the form to express interest so we can follow up with you once public preview of Microsoft Connected Cache for Enteprise and Education is available. To register your interest, fill out the form located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup). +This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE). -## Enterprise requirements for MCC +## Licensing requirements -1. **Azure subscription**: MCC management portal is hosted within Azure and is used to create the Connected Cache [Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management) and IoT Hub resource. Both are free services. +- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCCE) service, you will need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management). - Your Azure subscription ID is first used to provision MCC services, and enable access to the preview. The MCC server requirement for an Azure subscription costs you nothing. If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/). + If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/). + + The resources used for the public preview and in the future when this product is ready for production will be free to you, like other caching solutions. + +- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from a MCCE cache node. + + - [Windows Enterprise E3 or E5](https://learn.microsoft.com/en-us/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/en-us/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916) + - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/en-us/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans) + +## Cache node host machine requirements - The resources used for the preview and in the future when this product is ready for production will be free to you, like other caching solutions. -1. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps. - > [!NOTE] - > Azure VMs are not currently supported. If you'd like to install your cache node on VMWare, see the [Appendix](mcc-enterprise-appendix.md) for a few additional configurations. + > If you'd like to install your cache node on VMWare, see the [Appendix](mcc-enterprise-appendix.md) for a few additional configurations. - **EFLOW requires Hyper-V support** - - On Windows client, enable the Hyper-V feature. - - On Windows Server, install the Hyper-V role and create a default network switch. - - For more requirements, see [EFLOW requirements](/azure/iot-edge/iot-edge-for-linux-on-windows#prerequisites). +### General requirements - Disk recommendations: - - Using an SSD is recommended as cache read speed of SSD is superior to HDD +- Any previous installations of MCC must be [uninstalled](mcc-enterprise-update-uninstall.md) prior to installing the latest version of MCC. +- [These listed endpoints](delivery-optimization-endpoints.md) must be reachable by the host machine. +- There must be no other services / applications utilizing port 80 on the host machine (e.g. ConfigManager, Distribution Point) +- There must be at least 4 GB of free memory on the host machine. - NIC requirements: - - Multiple NICs on a single MCC instance aren't supported. - - 1 Gbps NIC is the minimum speed recommended but any NIC is supported. - - For best performance, NIC and BIOS should support SR-IOV. +### Additional requirements for Windows host machines - VM networking: - - An external virtual switch to support outbound and inbound network communication (created during the installation process) -1. **Content endpoints**: If you're using a proxy or firewall, certain endpoints must be allowed through in order for your MCC to cache and serve content. See [Delivery Optimization and Microsoft Connected Cache content type endpoints](delivery-optimization-endpoints.md) for the list of required endpoints. +- The Windows host machine must be using Windows 11 or Windows Server 2022 with the Latest Cumulative Update (LCU) applied. + - Windows 11 must have [OS Build 22631.3296](https://support.microsoft.com/en-us/topic/march-12-2024-kb5035853-os-builds-22621-3296-and-22631-3296-a69ac07f-e893-4d16-bbe1-554b7d9dd39b) or later + - Windows Server 2022 must have [OS Build 20348.2227](https://support.microsoft.com/en-us/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) or later +- The Windows host machine must support nested virtualization. +- The Windows host machine must have [WSL2 installed](https://learn.microsoft.com/en-us/windows/wsl/install#install-wsl-command). -## Sizing recommendations +### Additional requirements for Linux host machines + +- The Linux host machine must be using one of the following Operating Systems: + + - Ubuntu 20.04 + - Red Hat Enterprise Linux 8.* or 9.* + - If using RHEL, the default container engine (Podman) must be replaced with [Moby](https://github.com/moby/moby#readme) + +### Networking recommendations for host machines + +- Multiple network interface cards (NICs) on a single MCC instance aren't supported. +- 1 Gbps NIC is the minimum speed recommended but any NIC is supported. +- For best performance, NIC and BIOS should support SR-IOV. + +### Host machine sizing recommendations | Component | Branch Office / Small Enterprise | Large Enterprise | | -- | --- | --- | -| OS| Windows Server 2019*/2022
Windows 10*/11 (Pro or Enterprise) with Hyper-V Support

* Windows 10 and Windows Server 2019 build 17763 or later | Same | +| OS| Windows Server 2022
Windows 11 (Pro or Enterprise) | Same | |NIC | 1 Gbps | 5 Gbps | |Disk | SSD
1 drive
50 GB each |SSD
1 drive
200 GB each | |Memory | 4 GB | 8 GB | diff --git a/windows/deployment/do/mcc-enterprise-uninstall.md b/windows/deployment/do/mcc-enterprise-uninstall.md new file mode 100644 index 0000000000..3c67da978c --- /dev/null +++ b/windows/deployment/do/mcc-enterprise-uninstall.md @@ -0,0 +1,35 @@ +--- +title: Uninstall MCC for Enterprise and Education +description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) from a host machine. +ms.service: windows-client +ms.subservice: itpro-updates +ms.topic: how-to +ms.author: lichris +author: chrisjlin +manager: naengler +appliesto: +- ✅ Windows 11 +- ✅ Supported Linux distributions +- ✅ Microsoft Connected Cache for Enterprise and Education +ms.date: 09/27/2024 +--- + +# Uninstall MCCE caching software from a host machine + +This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) caching software from a host machine. This should be done after deleting the cache node in the Azure Portal. + +## Steps to uninstall MCCE from a Windows host machine + +1. Launch a PowerShell window *as administrator* and navigate to the MCC installation directory (C:\mcconwsl01 by default) +1. Run the `uninstallmcconwsl.ps1` script + +## Steps to uninstall MCCE from a Linux host machine + +The `uninstallmcc.sh` script within the provisioning package will uninstall the MCCE caching software and all related components, including: + +- IoT Edge +- Edge Agent +- Edge Hub +- MCC +- Moby CLI +- Moby engine \ No newline at end of file diff --git a/windows/deployment/do/mcc-enterprise-update-uninstall.md b/windows/deployment/do/mcc-enterprise-update-uninstall.md deleted file mode 100644 index 8ffa3c50c7..0000000000 --- a/windows/deployment/do/mcc-enterprise-update-uninstall.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -title: Uninstall MCC for Enterprise and Education -description: Details on how to uninstall Microsoft Connected Cache (MCC) for Enterprise and Education for your environment. -ms.service: windows-client -ms.subservice: itpro-updates -ms.topic: how-to -ms.author: carmenf -author: cmknox -manager: aaroncz -ms.reviewer: mstewart -ms.collection: - - tier3 - - must-keep -appliesto: -- ✅ Windows 11 -- ✅ Windows 10 -- ✅ Microsoft Connected Cache for Enterprise and Education -ms.date: 05/23/2024 ---- - - -# Uninstall MCC - -Contact the MCC Team before uninstalling to let us know if you're facing issues. - -This script removes the following items: - -1. EFLOW + Linux VM -1. IoT Edge -1. Edge Agent -1. Edge Hub -1. MCC -1. Moby CLI -1. Moby Engine - -To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT -Edge LTS \> Uninstall diff --git a/windows/deployment/do/mcc-enterprise-verify-functionality.md b/windows/deployment/do/mcc-enterprise-verify-functionality.md new file mode 100644 index 0000000000..25f9af10ff --- /dev/null +++ b/windows/deployment/do/mcc-enterprise-verify-functionality.md @@ -0,0 +1,46 @@ +--- +title: Verify cache node functionality +description: How to verify functionality of a Microsoft Connected Cache for Enterprise and Education cache node. +author: chrisjlin +ms.author: lichris +manager: naengler +ms.service: windows-client +ms.subservice: itpro-updates +ms.topic: how-to +ms.date: 09/27/2024 +appliesto: +- ✅ Windows-hosted MCCE cache nodes +- ✅ Linux-hosted MCCE cache nodes +- ✅ Microsoft Connected Cache for Enterprise and Education +--- + +# Verify MCCE cache node functionality + +This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCCE) cache node is functioning correctly. + +This should be done after deploying MCCE caching software to a [Windows](mcc-enterprise-deploy-windows.md) or [Linux](mcc-enterprise-deploy-linux.md) host machine. + +## Steps to verify functionality of MCCE cache node + +1. To verify that the MCCE container on the host machine is running and reachable, run the following command from the host machine: + + ```powershell + wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com + ``` + + If successful, there should be an HTTP response with StatusCode 200. + +1. To verify that the MCCE cache node can be reached by Windows clients in your network, visit the following address from a web browser on a Windows client device: + + `http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com` + + If successful, the Windows client device should begin to download a small image file from the MCCE cache node. + +1. To check how much content an individual Windows client has pulled from a MCCE cache node, open the [Delivery Optimization activity monitor](https://learn.microsoft.com/en-us/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. + + You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server". + +## Related content + +- [Monitor cache node usage](mcc-enterprise-monitoring.md) +- [Troubleshoot cache node](mcc-enterprise-support-troubleshoot.md) \ No newline at end of file From c5c1082cca1468627e80021d00dd8a5f6559433c Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 27 Sep 2024 13:51:56 -0700 Subject: [PATCH 02/12] Acrolinx improvements --- .../deployment/do/mcc-enterprise-deploy-linux.md | 4 ++-- .../do/mcc-enterprise-deploy-windows.md | 10 +++++----- .../do/mcc-enterprise-prerequisites.md | 16 ++++++++-------- .../deployment/do/mcc-enterprise-uninstall.md | 10 +++++----- .../do/mcc-enterprise-verify-functionality.md | 6 +++--- 5 files changed, 23 insertions(+), 23 deletions(-) diff --git a/windows/deployment/do/mcc-enterprise-deploy-linux.md b/windows/deployment/do/mcc-enterprise-deploy-linux.md index a4c836b19f..c15dd8a281 100644 --- a/windows/deployment/do/mcc-enterprise-deploy-linux.md +++ b/windows/deployment/do/mcc-enterprise-deploy-linux.md @@ -17,11 +17,11 @@ appliesto: This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Linux host machine. -Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md) and you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). +Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). ## Steps to deploy MCCE to Linux -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 button at the top of the Cache Node Configuration page and extract the package onto the host machine. 1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package. 1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute. diff --git a/windows/deployment/do/mcc-enterprise-deploy-windows.md b/windows/deployment/do/mcc-enterprise-deploy-windows.md index e640d0f7c3..e75da9ca97 100644 --- a/windows/deployment/do/mcc-enterprise-deploy-windows.md +++ b/windows/deployment/do/mcc-enterprise-deploy-windows.md @@ -17,18 +17,18 @@ appliesto: 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 relies on [Windows Subsystem for Linux (WSL)](https://learn.microsoft.com/en-us/windows/wsl/about) being installed under a [Group Managed Service Account (gMSA)](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or [Local User Account](https://support.microsoft.com/en-us/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) to isolate execution of the WSL-Microsoft Connected Cache distribution from the other users on the machine. This helps prevent tampering with both the WSL-MCC process and the cached content that is hosted on the disk. +Deploying MCCE to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/en-us/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) 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](mcc-enterprise-prerequisites.md) and you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). +Before deploying MCCE to a Windows host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). ## Steps to deploy MCCE to Windows -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 button at the top of the Cache Node Configuration page and extract the package onto the host machine. 1. Open a PowerShell windows *as administrator* on the host machine, then change directory to the extracted provisioning package. -1. Set the Execution Policy to "Unrestricted" to allow the provisoning 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 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 are using a Local User account as the MCCE runtime account, you will also need to create a [PS Credential Object](https://learn.microsoft.com/en-us/dotnet/api/system.management.automation.pscredential?view=powershellsdk-7.4.0) named `$myLocalAccountCredential`. + - If you're using a Local User account as the MCCE runtime account, you'll also need to create a [PSCredential Object](https://learn.microsoft.com/en-us/dotnet/api/system.management.automation.pscredential?view=powershellsdk-7.4.0) named `$myLocalAccountCredential`. 1. Run the provisioning command on the host machine. ## Next step diff --git a/windows/deployment/do/mcc-enterprise-prerequisites.md b/windows/deployment/do/mcc-enterprise-prerequisites.md index 54e924692e..a53dc8e4a8 100644 --- a/windows/deployment/do/mcc-enterprise-prerequisites.md +++ b/windows/deployment/do/mcc-enterprise-prerequisites.md @@ -19,13 +19,13 @@ This article details the requirements and recommendations for using Microsoft Co ## Licensing requirements -- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCCE) service, you will need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management). +- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCCE) service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management). If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/). - The resources used for the public preview and in the future when this product is ready for production will be free to you, like other caching solutions. + The Azure resources used for MCCE will be free to you during this public preview. -- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from a MCCE cache node. +- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from an MCCE cache node. - [Windows Enterprise E3 or E5](https://learn.microsoft.com/en-us/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/en-us/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916) - Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/en-us/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans) @@ -37,10 +37,10 @@ This article details the requirements and recommendations for using Microsoft Co ### General requirements -- Any previous installations of MCC must be [uninstalled](mcc-enterprise-update-uninstall.md) prior to installing the latest version of MCC. +- Any previous installations of MCC must be [uninstalled](mcc-enterprise-update-uninstall.md) before installing the latest version of MCC. - [These listed endpoints](delivery-optimization-endpoints.md) must be reachable by the host machine. -- There must be no other services / applications utilizing port 80 on the host machine (e.g. ConfigManager, Distribution Point) -- There must be at least 4 GB of free memory on the host machine. +- The host machine must have no other services / applications utilizing port 80 (for example, ConfigManager or Distribution Point). +- The host machine must have at least 4 GB of free memory. ### Additional requirements for Windows host machines @@ -55,14 +55,14 @@ This article details the requirements and recommendations for using Microsoft Co - The Linux host machine must be using one of the following Operating Systems: - Ubuntu 20.04 - - Red Hat Enterprise Linux 8.* or 9.* + - Red Hat Enterprise Linux (RHEL) 8.* or 9.* - If using RHEL, the default container engine (Podman) must be replaced with [Moby](https://github.com/moby/moby#readme) ### Networking recommendations for host machines - Multiple network interface cards (NICs) on a single MCC instance aren't supported. - 1 Gbps NIC is the minimum speed recommended but any NIC is supported. -- For best performance, NIC and BIOS should support SR-IOV. +- The NIC and BIOS should support SR-IOV for best performance. ### Host machine sizing recommendations diff --git a/windows/deployment/do/mcc-enterprise-uninstall.md b/windows/deployment/do/mcc-enterprise-uninstall.md index 3c67da978c..69eb8b733b 100644 --- a/windows/deployment/do/mcc-enterprise-uninstall.md +++ b/windows/deployment/do/mcc-enterprise-uninstall.md @@ -16,7 +16,7 @@ ms.date: 09/27/2024 # Uninstall MCCE caching software from a host machine -This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) caching software from a host machine. This should be done after deleting the cache node in the Azure Portal. +This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal. ## Steps to uninstall MCCE from a Windows host machine @@ -25,11 +25,11 @@ This article describes how to uninstall Microsoft Connected Cache for Enterprise ## Steps to uninstall MCCE from a Linux host machine -The `uninstallmcc.sh` script within the provisioning package will uninstall the MCCE caching software and all related components, including: +The `uninstallmcc.sh` script within the provisioning package uninstalls the MCCE caching software and all related components, including: - IoT Edge -- Edge Agent -- Edge Hub +- IoT Edge Agent +- IoT Edge Hub - MCC - Moby CLI -- Moby engine \ No newline at end of file +- Moby engine diff --git a/windows/deployment/do/mcc-enterprise-verify-functionality.md b/windows/deployment/do/mcc-enterprise-verify-functionality.md index 25f9af10ff..d782443c2e 100644 --- a/windows/deployment/do/mcc-enterprise-verify-functionality.md +++ b/windows/deployment/do/mcc-enterprise-verify-functionality.md @@ -18,7 +18,7 @@ appliesto: This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCCE) cache node is functioning correctly. -This should be done after deploying MCCE caching software to a [Windows](mcc-enterprise-deploy-windows.md) or [Linux](mcc-enterprise-deploy-linux.md) host machine. +These steps should be taken after deploying MCCE caching software to a [Windows](mcc-enterprise-deploy-windows.md) or [Linux](mcc-enterprise-deploy-linux.md) host machine. ## Steps to verify functionality of MCCE cache node @@ -30,13 +30,13 @@ This should be done after deploying MCCE caching software to a [Windows](mcc-ent If successful, there should be an HTTP response with StatusCode 200. -1. To verify that the MCCE cache node can be reached by Windows clients in your network, visit the following address from a web browser on a Windows client device: +1. To verify that Windows clients in your network can reach the MCCE cache node, visit the following address from a web browser on a Windows client device: `http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com` If successful, the Windows client device should begin to download a small image file from the MCCE cache node. -1. To check how much content an individual Windows client has pulled from a MCCE cache node, open the [Delivery Optimization activity monitor](https://learn.microsoft.com/en-us/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. +1. To check how much content an individual Windows client has pulled from an MCCE cache node, open the [Delivery Optimization activity monitor](https://learn.microsoft.com/en-us/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device. You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server". From 6747a66585f23213a39eaf18b3e53461997a7723 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 27 Sep 2024 15:36:51 -0700 Subject: [PATCH 03/12] additional edits, acrolinx --- .../do/mcc-ent-configure-provision-linux.md | 149 ------------------ .../do/mcc-ent-configure-provision-windows.md | 149 ------------------ .../do/mcc-ent-create-resource-and-cache.md | 8 +- ...oy-linux.md => mcc-ent-deploy-to-linux.md} | 4 +- ...indows.md => mcc-ent-deploy-to-windows.md} | 4 +- .../do/mcc-ent-manage-cache-using-CLI.md | 98 ++++++------ 6 files changed, 56 insertions(+), 356 deletions(-) delete mode 100644 windows/deployment/do/mcc-ent-configure-provision-linux.md delete mode 100644 windows/deployment/do/mcc-ent-configure-provision-windows.md rename windows/deployment/do/{mcc-ent-deploy-linux.md => mcc-ent-deploy-to-linux.md} (92%) rename windows/deployment/do/{mcc-ent-deploy-windows.md => mcc-ent-deploy-to-windows.md} (95%) diff --git a/windows/deployment/do/mcc-ent-configure-provision-linux.md b/windows/deployment/do/mcc-ent-configure-provision-linux.md deleted file mode 100644 index 3c39a7af8f..0000000000 --- a/windows/deployment/do/mcc-ent-configure-provision-linux.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -title: MCC for Enterprise provision Linux cache node -description: Microsoft Connected Cache for Enterprise. Learn about how to provision Linux cache node. -ms.service: windows-client -ms.subservice: itpro-updates -ms.topic: how-to -manager: aaroncz -ms.author: nidos -author: doshnid -ms.reviewer: mstewart -ms.collection: tier3 -appliesto: -- ✅ Windows 11 -- ✅ Windows 10 -- ✅ Microsoft Connected Cache for Enterprise -ms.date: 06/03/2024 ---- - - - - - -# " * " -TODO: Add your heading - - - -TODO: Add your introductory paragraph - - - - - -## Prerequisites - -TODO: List the prerequisites - - - -## "\ * \" -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps -1. Step 1 -1. Step 2 -1. Step 3 - -## "\ * \" -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps -1. Step 1 -1. Step 2 -1. Step 3 - -## "\ * \" -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps -1. Step 1 -1. Step 2 -1. Step 3 - - - -## Next step - -TODO: Add your next step link(s) - -> [!div class="nextstepaction"] -> [Write concepts](article-concept.md) - - - -## Related content - -TODO: Add your next step link(s) - -- [Write concepts](article-concept.md) - - - diff --git a/windows/deployment/do/mcc-ent-configure-provision-windows.md b/windows/deployment/do/mcc-ent-configure-provision-windows.md deleted file mode 100644 index d2ea4921a2..0000000000 --- a/windows/deployment/do/mcc-ent-configure-provision-windows.md +++ /dev/null @@ -1,149 +0,0 @@ ---- -title: MCC for Enterprise provision Windows cache node -description: Microsoft Connected Cache for Enterprise. Learn about how to provision Windows cache node. -ms.service: windows-client -ms.subservice: itpro-updates -ms.topic: how-to -manager: aaroncz -ms.author: nidos -author: doshnid -ms.reviewer: mstewart -ms.collection: tier3 -appliesto: -- ✅ Windows 11 -- ✅ Windows 10 -- ✅ Microsoft Connected Cache for Enterprise -ms.date: 06/03/2024 ---- - - - - - -# " * " -TODO: Add your heading - - - -TODO: Add your introductory paragraph - - - - - -## Prerequisites - -TODO: List the prerequisites - - - -## "\ * \" -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps -1. Step 1 -1. Step 2 -1. Step 3 - -## "\ * \" -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps -1. Step 1 -1. Step 2 -1. Step 3 - -## "\ * \" -TODO: Add introduction sentence(s) -[Include a sentence or two to explain only what is needed to complete the procedure.] -TODO: Add ordered list of procedure steps -1. Step 1 -1. Step 2 -1. Step 3 - - - -## Next step - -TODO: Add your next step link(s) - -> [!div class="nextstepaction"] -> [Write concepts](article-concept.md) - - - -## Related content - -TODO: Add your next step link(s) - -- [Write concepts](article-concept.md) - - - diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md index d067f2c8dd..b1dcf2cc2c 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md @@ -195,17 +195,17 @@ az mcc ent node update --cache-node-name --mcc-resource-name -To provision MCC on **Linux** host machine, see [Provision Linux cache node](mcc-ent-configure-provision-linux.md) +To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md) # [Azure CLI](#tab/cli/) -To provision cache node using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md) +To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md) ---
diff --git a/windows/deployment/do/mcc-ent-deploy-linux.md b/windows/deployment/do/mcc-ent-deploy-to-linux.md similarity index 92% rename from windows/deployment/do/mcc-ent-deploy-linux.md rename to windows/deployment/do/mcc-ent-deploy-to-linux.md index c15dd8a281..55acd126ef 100644 --- a/windows/deployment/do/mcc-ent-deploy-linux.md +++ b/windows/deployment/do/mcc-ent-deploy-to-linux.md @@ -13,13 +13,13 @@ appliesto: - ✅ Microsoft Connected Cache for Enterprise and Education --- -# Deploy your Connected Cache to a Linux host machine +# Deploy MCCE cache node to a Linux host machine This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) caching software to a Linux host machine. Before deploying MCCE to a Linux host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). -## Steps to deploy MCCE to Linux +## Steps to deploy MCCE cache node to Linux 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 button at the top of the Cache Node Configuration page and extract the package onto the host machine. diff --git a/windows/deployment/do/mcc-ent-deploy-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md similarity index 95% rename from windows/deployment/do/mcc-ent-deploy-windows.md rename to windows/deployment/do/mcc-ent-deploy-to-windows.md index e75da9ca97..942744942e 100644 --- a/windows/deployment/do/mcc-ent-deploy-windows.md +++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md @@ -13,7 +13,7 @@ appliesto: - ✅ Microsoft Connected Cache for Enterprise and Education --- -# Deploy your Connected Cache to a Windows host machine +# 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. @@ -21,7 +21,7 @@ Deploying MCCE to a Windows host machine requires designating a [Group Managed S Before deploying MCCE to a Windows host machine, ensure that the host machine meets all [requirements](mcc-enterprise-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources). -## Steps to deploy MCCE to Windows +## 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. 1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine. diff --git a/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md b/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md index 2d913cc50e..783ed6f8e5 100644 --- a/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md +++ b/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md @@ -20,7 +20,7 @@ ms.date: 06/03/2024
-This article outlines how to create, configure and provision your Microsoft Connected Cache for Enterprise cache nodes using Azure CLI. +This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCCE) cache nodes using Azure CLI. ## Prerequisites: @@ -34,20 +34,20 @@ This article outlines how to create, configure and provision your Microsoft Conn The first step is to create a resource group if you don't already have one. An Azure resource group is a logical container into which Azure resources are deployed and managed. -To create a resource group, use [az group create](/cli/azure/group#az-group-create). +To create a resource group, use `az group create`. You can find more details on this CLI command [here](/cli/azure/group#az-group-create).
```azurecli-interactive az group create --name myrg --location westus ``` -Once the resource group is created, you will need to create a Microsoft Connected Cache for Enterprise resource. +Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource. -### 2. Create a MCC resource -A MCC resource is a resource under which cache nodes can be created. +### 2. Create an MCCE Azure resource +An MCCE Azure resource is a top-level Azure resource under which cache nodes can be created. -To create a mcc resource, use az mcc ent resource create +To create an MCCE Azure resource, use `az mcc ent resource create` ```azurecli-interactive az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg @@ -64,7 +64,7 @@ The next step is to create a cache node under this resource. ### 3. Create a cache node -To create a cache node, use az mcc ent node create +To create a cache node, use `az mcc ent node create` ```azurecli-interactive az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg --host-os linux @@ -78,8 +78,9 @@ az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccre
### 4. Confirm cache node creation -Before you can start configuring your cache node, you need to confirm that cache node creation has been successful. -To confirm cache node creation, use az mcc ent node show +Before you can start configuring your cache node, you need to confirm that the cache node was successfully created. + +To confirm cache node creation, use `az mcc ent node show`
@@ -93,11 +94,11 @@ az mcc ent node show --cache-node-name mycachenode --mcc-resource-name mymccreso
-Once the cache node has been created successfully, you can now configure the cache node. +Once successful cache node creation is confirmed, you can proceed to configure the cache node. ### 5. Configure cache node -To configure your cache node, use az mcc ent node update +To configure your cache node, use `az mcc ent node update` The below example configures a Linux cache node with proxy enabled: @@ -125,68 +126,59 @@ az mcc ent node update --cache-node-name --mcc-resource-name ### 6. Get provisioning details for the cache node -Now that you have configured the cache node, the next step is to provision the cache node on the server. To provision the cache node, you will need to create a provisioning script with relevant information. -To get the relevant information for provisioning script, use az mcc ent node get-provisioning-details +After successfully configuring the cache node, the next step is to deploy the cache node to a host machine. To deploy the cache node, you'll need to create a provisioning script with relevant information. + +To get the relevant information for provisioning script, use `az mcc ent node get-provisioning-details` ```azurecli-interactive az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg ``` -In the output, please save the values for cacheNodeId, customerKey, mccResourceId, registrationKey. These values are needed to create the provisioning script. +Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script. -### 7. Provisioning cache node +### 7. Deploy cache node
-#### Provisioning cache node on Linux host OS: -Before you provision your cache node on Linux machine, please make sure you have completed the requisites listed here: Host machine requirements +#### Deploy cache node to Linux host machine +Before you deploy your cache node to a Linux host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md) -Use the link below to download and unzip the provisioning package on the server and run the below script to provision your cache node. +Use the following link to download and extract the Linux-compatible MCCE provisioning package onto the host machine. -[Download MCC package for Linux host OS](https://aka.ms/MCC-Ent-InstallScript-Linux) +[Download MCCE provisioning package for Linux host machine](https://aka.ms/MCC-Ent-InstallScript-Linux)
>[!IMPORTANT] ->Note: before you execute the script, please make sure you change access permissions by running the command below
->```azurepowershell-interactive ->sudo chmod +x provisionmcc.sh ->``` +>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below. +```azurepowershell-interactive +sudo chmod +x provisionmcc.sh +``` -
+Replace the values in the following provisioning command before running it.
->[!NOTE] ->Please replace the sample values in the script below with the values that you saved in the step 5 and 6. - -
- ->[!IMPORTANT] ->'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet. - -
- -Provisioning script:
-`powershell-interactive +```azurepowershell-interactive sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid=" enter cacheNodeId here " customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="true" proxyurl=http://enter proxy hostname:enter port -` +```
-#### Provisioning cache node on Windows host OS: - -Before you provision your cache node on Windows, make sure you have completed the requisites listed here: [Host machine requirements](mcc-ent-prerequisites.md) - -Please download and unzip the provisioning package on the server and run the below script to provision your cache node. -Note: Please replace the sample values with the values that you saved in the above steps. - >[!IMPORTANT] >'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet. +#### Deploy cache node to Windows host machine + +Before you deploy your cache node to a Windows host machine, make sure you have met the prerequisites listed here: [Host machine requirements](mcc-ent-prerequisites.md) + +Use the following link to download and extract the Windows-compatible MCCE provisioning package onto the host machine. +[Download MCCE provisioning package for Windows host machine](https://aka.ms/MCC-Ent-InstallScript-WSL)
-[Download MCC package for Windows host OS](https://aka.ms/MCC-Ent-InstallScript-WSL) -
+>[!IMPORTANT] +>Before you execute the provisioning command, make sure you change directory to the extracted provisioning package and set the script execution permissions by running the command below. +```azurepowershell-interactive +Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process +``` - -If you are using a **gmsa** account:
+If you're using a **Group Managed Service Account**, replace the values in the following provisioning command before running it.
```powershell-interactive ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User @@ -194,7 +186,10 @@ If you are using a **gmsa** account:

-If you are using **local user account** or **domain user account**:
+>[!IMPORTANT] +>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet. + +If you're using **Local User account** or **Domain User account**, replace the values in the following provisioning command before running it.
```powershell-interactive ./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid enter mccResourceId here -cachenodeid enter cacheNodeId here -customerkey enter customerKey here -registrationkey enter registration key -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy $true -proxyurl " http://enter proxy host name:enter port" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential @@ -202,10 +197,13 @@ If you are using **local user account** or **domain user account**:

+>[!IMPORTANT] +>'shoulduseproxy' parameter is required, whether or not your network uses proxy to access internet. + ## Next step -To verify cache node functionality, visit, [Verify cache node functionality](mcc-ent-verify-cache-node.md) +To verify cache node functionality, see [Verify cache node functionality](mcc-ent-verify-cache-node.md)
From 34f7ff91815559117452338fe0d98d2cccbdb160 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Mon, 30 Sep 2024 11:03:42 -0700 Subject: [PATCH 04/12] additional changes --- .../do/mcc-ent-create-resource-and-cache.md | 79 ++++------ .../deployment/do/mcc-ent-deploy-to-linux.md | 10 +- .../do/mcc-ent-deploy-to-windows.md | 10 +- windows/deployment/do/mcc-ent-edu-overview.md | 4 +- windows/deployment/do/mcc-ent-faq.yml | 4 +- .../do/mcc-ent-manage-cache-using-CLI.md | 4 +- .../deployment/do/mcc-ent-monitor-cache.md | 149 ------------------ windows/deployment/do/mcc-ent-monitoring.md | 61 +++++++ .../deployment/do/mcc-ent-prerequisites.md | 6 +- .../deployment/do/mcc-ent-private-preview.md | 4 +- .../deployment/do/mcc-ent-release-notes.md | 4 +- .../do/mcc-ent-support-and-troubleshooting.md | 12 +- .../do/mcc-ent-uninstall-cache-node.md | 2 +- .../do/mcc-ent-update-cache-node.md | 72 ++++----- .../do/mcc-ent-verify-cache-node.md | 8 +- 15 files changed, 164 insertions(+), 265 deletions(-) delete mode 100644 windows/deployment/do/mcc-ent-monitor-cache.md create mode 100644 windows/deployment/do/mcc-ent-monitoring.md diff --git a/windows/deployment/do/mcc-ent-create-resource-and-cache.md b/windows/deployment/do/mcc-ent-create-resource-and-cache.md index b1dcf2cc2c..fd199751a9 100644 --- a/windows/deployment/do/mcc-ent-create-resource-and-cache.md +++ b/windows/deployment/do/mcc-ent-create-resource-and-cache.md @@ -1,31 +1,29 @@ --- -title: MCC for Enterprise provision create cache node -description: Microsoft Connected Cache for Enterprise. Learn about how to create cache node. +title: Create and configure MCCE cache nodes +description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to -manager: aaroncz +manager: naengler ms.author: nidos author: doshnid -ms.reviewer: mstewart -ms.collection: tier3 appliesto: - ✅ Windows 11 -- ✅ Windows 10 +- ✅ Supported Linux distributions - ✅ Microsoft Connected Cache for Enterprise ms.date: 06/03/2024 --- -# Create MCC resource and cache nodes +# Create MCCE Azure resource and cache nodes -This article outlines how to create and configure your Microsoft Connected Cache for Enterprise cache nodes. The creation and configuration of your cache node takes place in Azure portal. The deployment of your cache node requires downloading an installer script that will need to be run on your cache server. +This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes. The creation and configuration of your cache node takes place in Azure. The deployment of your cache node requires downloading and running an OS-specific provisioning package on your host machine. ## Prerequisites -1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a completely free-of-charge service hosted in Azure. You'll need to have a Pay-As-You-Go subscription in order to onboard to our service. To create a subscription, go to [Pay-As-You-Go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/). +1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/). 2. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps. -For more information on sizing and OS requirements, please visit [Host OS Requirement](mcc-ent-prerequisites.md) +For more information on sizing and OS requirements, see [the prerequisites for using MCCE](mcc-ent-prerequisites.md). -## Create MCC resource +## Create MCCE Azure resource # [Azure portal](#tab/portal) @@ -34,13 +32,13 @@ For more information on sizing and OS requirements, please visit [Host OS Requir :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png"::: --> -1. Select Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Also, enter a name for the resource and click Review + Create. +1. Select the Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Then enter a name for the resource and select Review + Create. 1. After a few moments, you'll see a "Validation successful" message, indicating you can move onto the next step and select Create. -1. The creation of the resource may take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes. +1. The creation of the resource might take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes. # [Azure CLI](#tab/cli) @@ -61,7 +59,7 @@ For more information on sizing and OS requirements, please visit [Host OS Requir * Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one. -#### Create MCC resource +#### Create MCCE Azure resource Replace the following placeholders with your own information: * *\*: An existing resource group in your subscription. * *\*: A name for your Microsoft Connected Cache for Enterprise resource. @@ -73,26 +71,26 @@ az mcc ent resource create --mcc-resource-name --resource-group --- -## Create cache node +## Create MCCE cache node # [Azure portal](#tab/portal) 1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created. - 1. Under Cache Node Management, click on Cache Nodes and then on + Create Cache Node. + 1. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node. - 1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and click create. Please note, cache node names have to be unique under the Microsoft Connected Cache resource. + 1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and select create. Note, cache node names have to be unique under the Microsoft Connected Cache resource. - The creation of cache node may take a few minutes. Please click Refresh to see your recently created cache node. + The creation of cache node might take a few minutes. Select Refresh to see your recently created cache node. Once the status changes to **Not Configured**, you can now configure your cache node. # [Azure CLI](#tab/cli) -Use the command below to create a new cache node if you don't already have one. +Use the following command to create a new cache node if you don't already have one. Replace the following placeholders with your own information: * *\*: An existing resource group in your subscription. @@ -123,22 +121,22 @@ az mcc ent node create --cache-node-name --mcc-resource-name *: An existing resource group in your subscription. * *\*: A name for your Microsoft Connected Cache for Enterprise resource. * *\*: The Azure region where your Microsoft Connected Cache will be located. -* *\*: The cache drive path. You can add upto 9 cache drives. +* *\*: The cache drive path. You can add upto nine cache drives. * *\*: The size of cache drive. Must be at least 50 Gb. * *\*: If proxy needs to be enabled or not.
Accepted values: enabled, disabled @@ -162,7 +160,7 @@ az mcc ent node update --cache-node-name --mcc-resource-name
-Use the command below to configure cache node for **Windows** host OS +Use the following command to configure cache node for deployment to a **Windows** host machine. Replace the following placeholders with your own information: * *\*: An existing resource group in your subscription. @@ -190,21 +188,16 @@ az mcc ent node update --cache-node-name --mcc-resource-name }]" --proxy --proxy-host <"proxy host name"> --proxy-port --auto-update-day --auto-update-time