diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml
index d486ab4862..0f9b776ed3 100644
--- a/windows/deployment/do/TOC.yml
+++ b/windows/deployment/do/TOC.yml
@@ -45,19 +45,19 @@
href: mcc-ent-create-resource-and-cache.md
- name: Configure, provision and deploy cache node
items:
- - name: Configure and provision cache node on Linux
- href: mcc-ent-configure-provision-linux.md
- - name: Configure and provision cache node on Windows
- href: mcc-ent-configure-provision-windows.md
+ - name: Deploy MCC to Linux
+ href: mcc-ent-deploy-to-linux.md
+ - name: Deploy MCC to Windows
+ href: mcc-ent-deploy-to-windows.md
- name: Using CLI to create and manage cache nodes
href: mcc-ent-manage-cache-using-CLI.md
- name: Verify cache node functionality
href: mcc-ent-verify-cache-node.md
- name: Monitor cache node
- href: mcc-ent-monitor-cache.md
+ href: mcc-ent-monitoring.md
- name: Update MCC
- href: mcc-ent-update-cache.md
- - name: Uninstalling cache node
+ href: mcc-ent-update-cache-node.md
+ - name: Uninstall cache node
href: mcc-ent-uninstall-cache-node.md
- name: Resources
items:
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..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. --mcc-resource-name
*: An existing resource group in your subscription.
@@ -190,22 +188,17 @@ 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 --auto-update-week --auto-update-ring
```
-
-
---
## Next step
-The next step is to provision the cache node on the server.
-# [Azure portal](#tab/portal)
-To provision MCC on **Windows** host machine, see [Provision Windows cache node](mcc-ent-configure-provision-windows.md)
+### [Azure portal](#tab/portal)
+To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
-Microsoft Connected Cache for Enterprise and Education
+---
+
+# 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-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
+
+## 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.
+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-ent-verify-cache-node.md)
+
+## Related content
+
+- [Deploy to a Windows host machine](mcc-ent-deploy-to-windows.md)
+- [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)
\ No newline at end of file
diff --git a/windows/deployment/do/mcc-ent-deploy-to-windows.md b/windows/deployment/do/mcc-ent-deploy-to-windows.md
new file mode 100644
index 0000000000..f5dae91aaf
--- /dev/null
+++ b/windows/deployment/do/mcc-ent-deploy-to-windows.md
@@ -0,0 +1,44 @@
+---
+title: Deploy MCCE cache software to a Windows host machine
+description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) 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 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)](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/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-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource](https://aka.ms/mccent-create-resources).
+
+## 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.
+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 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're using a Local User account as the MCCE runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
+1. Run the provisioning command on the host machine.
+
+## Next step
+
+> [!div class="nextstepaction"]
+> [Verify cache node functionality](mcc-ent-verify-cache-node.md)
+
+
+
+## Related content
+
+- [Deploy to a Linux host machine](mcc-ent-deploy-to-linux.md)
+- [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)
\ No newline at end of file
diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md
index a6b4c0afed..0060028e14 100644
--- a/windows/deployment/do/mcc-ent-edu-overview.md
+++ b/windows/deployment/do/mcc-ent-edu-overview.md
@@ -1,6 +1,6 @@
---
-title: MCC for Enterprise and Education Overview
-description: Overview, supported scenarios, and content types for Microsoft Connected Cache (MCC) for Enterprise and Education.
+title: MCCE Overview
+description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCCE).
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: conceptual
diff --git a/windows/deployment/do/mcc-ent-faq.yml b/windows/deployment/do/mcc-ent-faq.yml
index 690dd4d0c7..2d84c64a34 100644
--- a/windows/deployment/do/mcc-ent-faq.yml
+++ b/windows/deployment/do/mcc-ent-faq.yml
@@ -1,7 +1,7 @@
### YamlMime:FAQ
metadata:
- title: Microsoft Connected Cache for Enterprise Frequently Asked Questions
- description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise.
+ title: MCCE Frequently Asked Questions
+ description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCCE).
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: faq
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..1f28f0bdbf 100644
--- a/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md
+++ b/windows/deployment/do/mcc-ent-manage-cache-using-CLI.md
@@ -1,6 +1,6 @@
---
-title: MCC for Enterprise manage cache nodes using CLI
-description: Microsoft Connected Cache for Enterprise. Learn about managing cache nodes using CLI
+title: Manage MCCE cache nodes using CLI
+description: Details on how to manage Microsoft Connected Cache for Enterprise (MCCE) cache nodes via Azure CLI commands.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
@@ -20,7 +20,7 @@ ms.date: 06/03/2024
--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
Windows 11
+- ✅ Supported Linux distributions
+- ✅ Microsoft Connected Cache for Enterprise
+ms.date: 09/04/2024
+---
+
+# Monitor MCCE cache node usage
+
+Tracking the status and performance of your MCCE cache node is essential to making sure that you're getting the most out of the service.
+
+
+
+## Cache node summary
+
+The Cache Node Summary box on your Azure portal
+
+| Metric | Description |
+| --- | --- |
+| Healthy nodes | The MCCE service will periodically request heartbeat messages from your MCC node to determine if it's functioning as expected. |
+| Unhealthy nodes | If the cache node doesn't respond, it is labeled as unhealthy. |
+| Max in | The maximum egress (in Mb/sec.) that your node has pulled in at any given time. This statistic isn't dependent on the time filter near the charts. |
+| Max out | The minimum egress (in Mb/sec.) that your node has pushed out at any given time. |
+| Average in | The average ingress (in Mb/sec.) that your node has pulled in over its lifetime. This statistic isn't dependent on the time filter near the charts. |
+| Average out | The average egress (in Mb/sec.) that your node has pushed out over its lifetime. |
+| Cache efficiency | The percentage of all requests that your MCC node receives that are ultimately delivered by your MCC node. An effective node is generally expected to have an efficiency >95%. |
+
+## Charts
+
+### Filters
+
+- Will only filter the data shown in the two charts, scalable from 1 hour to 30 days
+- Can view data by individual cache nodes or the average of all your active MCC nodes.
+
+### Outbound traffic
+
+- The egress (in Mb/sec) that your MCC node is pushing out at specific time intervals
+
+### Volume by Content Type
+
+- The volume of content that your MCCE cache node is distributing, broken down by the hostname used to download said content
+
+## Additional metrics
+
+### Custom metrics
+
+- Navigate to the "Metrics" tab in the left-hand toolbar
+- Configure chart as desired using the provided metrics
+
+
\ No newline at end of file
diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md
index 1e33e85158..348b53caec 100644
--- a/windows/deployment/do/mcc-ent-prerequisites.md
+++ b/windows/deployment/do/mcc-ent-prerequisites.md
@@ -1,60 +1,71 @@
---
-title: Requirements for MCC for Enterprise and Education
-description: Overview of prerequisites and recommendations for using Microsoft Connected Cache (MCC) for Enterprise and Education.
+title: MCCE prerequisites
+description: Details 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'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).
- 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 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.
+ The Azure resources used for MCCE will be free to you during this public preview.
- **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).
+- **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.
- Disk recommendations:
- - Using an SSD is recommended as cache read speed of SSD is superior to HDD
+ - [Windows Enterprise E3 or E5](/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/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/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)
- 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.
+## Cache node host machine requirements
- 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.
+### General requirements
-## Sizing recommendations
+- Any previous installations of MCC must be [uninstalled](mcc-ent-uninstall-cache-node.md) before installing the latest version of MCC.
+- [These listed endpoints](delivery-optimization-endpoints.md) must be reachable by 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
+
+- 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/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/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](/windows/wsl/install#install-wsl-command).
+
+### 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 (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.
+- The NIC and BIOS should support SR-IOV for best performance.
+
+### Host machine sizing recommendations
| Component | Branch Office / Small Enterprise | Large Enterprise |
-| -- | --- | --- |
-| OS| Windows Server 2019*/2022 Windows 11
-- ✅ Windows 10
- ✅ Microsoft Connected Cache for Enterprise
ms.date: 06/03/2024
---
-
-
-# What is ?
-TODO: Add your heading
-
-
-
-[Introductory paragraph]
-TODO: Add your introductory paragraph
-
-
-
-
-
-## [Section 1 heading]
-TODO: add your content
-
-## [Section 2 heading]
-TODO: add your content
-
-## [Section n heading]
-TODO: add your content
-
-
+As such, we strongly recommend you [recreate your existing cache nodes in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCCE caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer. You don't need to re-create your MCC Azure resource.
## 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)
-
-
+> [View documentation for MCCE Public Preview](mcc-ent-edu-overview.md)
diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md
index 22407de869..c4b588f9ca 100644
--- a/windows/deployment/do/mcc-ent-release-notes.md
+++ b/windows/deployment/do/mcc-ent-release-notes.md
@@ -1,161 +1,40 @@
---
-title: MCC for Enterprise and Education Release Notes
-description: Release Notes for Microsoft Connected Cache (MCC) for Enterprise and Education.
+title: MCCE Release Notes
+description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE).
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: conceptual
-ms.author: nidos
-author: cmknox
-manager: aaroncz
-ms.reviewer: mstewart
-ms.collection: tier3
+ms.author: lichris
+author: chrisjlin
+manager: naengler
appliesto:
- ✅ Windows 11
-- ✅ Windows 10
+- ✅ Supported Linux distributions
- ✅ Microsoft Connected Cache for Enterprise and Education
-ms.date: 09/04/2024
+ms.date: 09/27/2024
---
-
-
-
-
-# [\ concept(s)]
-TODO: Add your heading
-
-
-
-[Introductory paragraph]
-TODO: Add your introductory paragraph
-
-
-
-## Prerequisites
-TODO: [List the prerequisites if appropriate]
-
-
-
-## [Section 1 heading]
-TODO: add your content
-
-## [Section 2 heading]
-TODO: add your content
-
-## [Section n heading]
-TODO: add your content
-
-
-
-## Next step
-
-TODO: Add your next step link(s)
-
-> [!div class="nextstepaction"]
-> [Write concepts](article-concept.md)
-
-
+- Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface
+- Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface
+- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource
+- Added Azure CLI support for programmatic creation and management of MCC Azure resources and cache nodes
+- Added support for unauthenticated proxy and cloud proxy integration
+- Added ability to set each cache node's Update Ring to govern cadence of MCCE container updates
## Related content
-TODO: Add your next step link(s)
-
-- [Write concepts](article-concept.md)
-
-
-
-
-
-
-## 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)
-
-
+- [Overview of MCCE](mcc-ent-edu-overview.md)
diff --git a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md b/windows/deployment/do/mcc-ent-support-and-troubleshooting.md
index 8b405f6c51..c7bae542e2 100644
--- a/windows/deployment/do/mcc-ent-support-and-troubleshooting.md
+++ b/windows/deployment/do/mcc-ent-support-and-troubleshooting.md
@@ -1,19 +1,17 @@
---
-title: MCC for Enterprise support and troubleshooting
-description: Microsoft Connected Cache for Enterprise. Learn about support and troubleshooting
+title: MCCE support and troubleshooting
+description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCCE).
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
+manager: naengler
+ms.author: lichris
+author: chrisjlin
appliesto:
- ✅ Windows 11
-- ✅ Windows 10
+- ✅ Supported Linux distributions
- ✅ Microsoft Connected Cache for Enterprise
-ms.date: 06/03/2024
+ms.date: 09/27/2024
---
-# " * "
-TODO: Add your heading
+# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCCE)
-TODO: Add your introductory paragraph
+This article contains instructions on how to troubleshoot different issues you may encounter while using MCCE. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache.md).
-
+MCC Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields.
-
-
-## Prerequisites
-
-TODO: List the prerequisites
-
-
-
-## "\ * \"
+## Troubleshooting cache node creation
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
-## "\ * \"
+## Troubleshooting cache node deployment
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
-## "\ * \"
+## Troubleshooting cache node monitoring
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
@@ -128,22 +95,6 @@ Optional: You have two options for manually curated links in this pattern: Next
-->
-## 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)
-
-
+## Filing a support request
+TODO: Add steps for filling out a CSS ticket.
diff --git a/windows/deployment/do/mcc-ent-uninstall-cache-node.md b/windows/deployment/do/mcc-ent-uninstall-cache-node.md
index 1aa10c6c08..70ca441c4f 100644
--- a/windows/deployment/do/mcc-ent-uninstall-cache-node.md
+++ b/windows/deployment/do/mcc-ent-uninstall-cache-node.md
@@ -1,149 +1,35 @@
---
-title: MCC for Enterprise uninstall
-description: Microsoft Connected Cache for Enterprise. Learn about uninstall
+title: Uninstall MCCE cache nodes
+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
-manager: aaroncz
-ms.author: nidos
-author: doshnid
-ms.reviewer: mstewart
-ms.collection: tier3
+ms.author: lichris
+author: chrisjlin
+manager: naengler
appliesto:
- ✅ Windows 11
-- ✅ Windows 10
-- ✅ Microsoft Connected Cache for Enterprise
-ms.date: 06/03/2024
+- ✅ Supported Linux distributions
+- ✅ Microsoft Connected Cache for Enterprise and Education
+ms.date: 09/27/2024
---
-
+## Steps to uninstall MCCE from a Linux host machine
-
-
-# " * "
-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)
-
-
+The `uninstallmcc.sh` script within the provisioning package uninstalls the MCCE caching software and all related components, including:
+- IoT Edge
+- IoT Edge Agent
+- IoT Edge Hub
+- MCC
+- Moby CLI
+- Moby engine
diff --git a/windows/deployment/do/mcc-ent-update-cache-node.md b/windows/deployment/do/mcc-ent-update-cache-node.md
new file mode 100644
index 0000000000..b49b6c76d6
--- /dev/null
+++ b/windows/deployment/do/mcc-ent-update-cache-node.md
@@ -0,0 +1,55 @@
+---
+title: Update MCCE cache nodes
+description: Details on how Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes are updated by Microsoft.
+ms.service: windows-client
+ms.subservice: itpro-updates
+ms.topic: how-to
+ms.author: andyriv
+author: chrisjlin
+manager: naengler
+appliesto:
+- ✅ Windows 11
+- ✅ Supported Linux distributions
+- ✅ Microsoft Connected Cache for Enterprise and Education
+ms.date: 09/27/2024
+---
+# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education (MCCE)
+
+Microsoft Connected Cache for Enterprise and Education (MCCE) caching software is deployed to host machines as a container. The container OS and any software component within the container will need to be updated for security vulnerabilities or quality issues, or performance improvements required to successfully operate the caching software. These Microsoft-published container updates are called "MCCE updates" in this article.
+
+Microsoft silently deploys MCCE updates to your cache nodes based on the Update Ring setting you configure for each cache node.
+
+## Update rings
+
+MCCE cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node is silently updated by Microsoft within five weeks of the update becoming available.
+
+In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest MCCE update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest MCCE update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring.
+
+### Update ring options
+
+#### Fast Ring
+All MCCE cache nodes are configured to update as part of the Fast ring by default. MCCE cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday.
+
+#### Slow Ring
+Configuring an MCCE cache node to update as part of the Slow ring provides users with the option to delay MCCE software updates until the update can be validated. There are three settings that control when MCCE updates will be applied to MCCE cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
+
+| Setting | Description |
+| --- | --- |
+| Week of the month | 1st to 4th week can be selected. There are three to four months in a year that could have a 5th week. If there's a 5th week, the update could be applied during that 5th week if the day of the week falls near the last day of the month.|
+| Day of the week | Monday through Sunday can be selected. |
+| Time of day | Time of day is based on UTC and a 24 hour clock. |
+
+## Update process
+
+When Microsoft publishes an MCCE update, the MCCE service attempts to update all MCCE cache nodes based on their Update Ring membership. If a cache node can't complete the silent MCCE update within 6 hours of starting, an error message is surfaced in the Azure portal.
+
+## Update terminology, criteria, and SLA
+
+MCCE updates will be released based on need instead of on a set cadence.
+
+| Update type | Criteria and SLA |
+| --- | --- |
+| Security | Security updates are the highest priority and will be released based on the severity rating of the vulnerability. [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 60 days of discovery. [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 120 days |
+| Quality | Quality updates fix a specific problem and addresses a noncritical, non-security-related bug. Quality updates could include performance fixes for a specific problem or changes related to cache efficiency or maximum egress for example. Quality updates will be released along with security updates or when necessary to ensure proper functioning of the Microsoft Connected Cache software. |
+
+For information on all released Microsoft Connected Cache updates see the [MCCE release notes](mcc-ent-release-notes.md).
diff --git a/windows/deployment/do/mcc-ent-verify-cache-node.md b/windows/deployment/do/mcc-ent-verify-cache-node.md
index be12905760..28bc2764ff 100644
--- a/windows/deployment/do/mcc-ent-verify-cache-node.md
+++ b/windows/deployment/do/mcc-ent-verify-cache-node.md
@@ -1,149 +1,46 @@
---
-title: MCC for Enterprise verify cache node
-description: Microsoft Connected Cache for Enterprise. Learn about verifying cache node
+title: Verify MCCE cache node functionality
+description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
+author: chrisjlin
+ms.author: lichris
+manager: naengler
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
+ms.date: 09/27/2024
appliesto:
-- ✅ Windows 11
-- ✅ Windows 10
-- ✅ Microsoft Connected Cache for Enterprise
-ms.date: 06/03/2024
+- ✅ Windows-hosted MCCE cache nodes
+- ✅ Linux-hosted MCCE cache nodes
+- ✅ Microsoft Connected Cache for Enterprise and Education
---
-
+1. To verify that the MCCE container on the host machine is running and reachable, run the following command from the host machine:
-
+ If successful, the Windows client device should begin to download a small image file from the MCCE cache node.
-# " * "
-TODO: Add your heading
+1. To check how much content an individual Windows client has pulled from an MCCE cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
-
-
-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)
-
-
+ 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
-TODO: Add your next step link(s)
-
-- [Write concepts](article-concept.md)
-
-
-
+- [Monitor cache node usage](mcc-ent-monitoring.md)
+- [Troubleshoot cache node](mcc-ent-support-and-troubleshooting.md)