mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 10:53:43 +00:00
lichris-docs-1
This commit is contained in:
chrisjlin
@ -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
|
||||
|
||||
38
windows/deployment/do/mcc-enterprise-deploy-linux.md
Normal file
38
windows/deployment/do/mcc-enterprise-deploy-linux.md
Normal file
@ -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
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
# 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)
|
||||
44
windows/deployment/do/mcc-enterprise-deploy-windows.md
Normal file
44
windows/deployment/do/mcc-enterprise-deploy-windows.md
Normal file
@ -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:
|
||||
- ✅ <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 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)
|
||||
|
||||
<!-- OR -->
|
||||
|
||||
## Related content
|
||||
|
||||
- [Deploy to a Linux host machine](mcc-enterprise-deploy-linux.md)
|
||||
- [Uninstall MCCE](mcc-enterprise-uninstall.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:
|
||||
- ✅ <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/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- - ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 05/23/2024
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
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 <br> Windows 10*/11 (Pro or Enterprise) with Hyper-V Support <br><br>* Windows 10 and Windows Server 2019 build 17763 or later | Same |
|
||||
| OS| Windows Server 2022 <br> Windows 11 (Pro or Enterprise) | Same |
|
||||
|NIC | 1 Gbps | 5 Gbps |
|
||||
|Disk | SSD <br>1 drive <br>50 GB each |SSD <br>1 drive <br>200 GB each |
|
||||
|Memory | 4 GB | 8 GB |
|
||||
|
||||
35
windows/deployment/do/mcc-enterprise-uninstall.md
Normal file
35
windows/deployment/do/mcc-enterprise-uninstall.md
Normal file
@ -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:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
|
||||
- ✅ Supported Linux distributions
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
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
|
||||
@ -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:
|
||||
- ✅ <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/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 05/23/2024
|
||||
---
|
||||
|
||||
<!-- Customers will no longer update the private preview and instead install public preview
|
||||
# Update or uninstall Microsoft Connected Cache for Enterprise and Education
|
||||
|
||||
Throughout the preview phase, we'll send you security and feature updates for MCC. Follow these steps to perform the update.
|
||||
|
||||
## Update MCC
|
||||
|
||||
Run the following command with the **arguments** we provided in the email to update your MCC:
|
||||
|
||||
```powershell
|
||||
# .\updatemcc.ps1 version="**\<VERSION\>**" tenantid="**\<TENANTID\>**" customerid="**\<CUSTOMERID\>**" cachenodeid="**\<CACHENODEID\>**" customerkey="**\<CUSTOMERKEY\>**"
|
||||
```
|
||||
|
||||
For example:
|
||||
|
||||
```powershell
|
||||
# .\updatemcc.ps1 version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.659" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99a"
|
||||
```
|
||||
-->
|
||||
# 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
|
||||
46
windows/deployment/do/mcc-enterprise-verify-functionality.md
Normal file
46
windows/deployment/do/mcc-enterprise-verify-functionality.md
Normal file
@ -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
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
# 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)
|
||||
Reference in New Issue
Block a user