diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md
index 4aefa039d1..c730c9e094 100644
--- a/windows/deployment/do/mcc-ent-edu-overview.md
+++ b/windows/deployment/do/mcc-ent-edu-overview.md
@@ -13,7 +13,7 @@ appliesto:
- ✅ Windows 11
- ✅ Windows 10
- ✅ Microsoft Connected Cache for Enterprise and Education
-ms.date: 10/30/2024
+ms.date: 02/28/2025
---
# Microsoft Connected Cache for Enterprise and Education Overview
@@ -57,7 +57,7 @@ Customers may have office spaces, data centers, or Azure deployments that meet s
- Have Azure VMs and/or Azure Virtual Desktop deployed
- Have limited internet bandwidth (T1 or T3 lines)
-To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04.
+To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 (or later) or Ubuntu 24.04.
See [Connected Cache node host machine requirements](mcc-ent-prerequisites.md) for recommended host machine specifications in each configuration.
diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md
index c9e99fa963..d40301587e 100644
--- a/windows/deployment/do/mcc-ent-prerequisites.md
+++ b/windows/deployment/do/mcc-ent-prerequisites.md
@@ -10,7 +10,7 @@ manager: naengler
appliesto:
- ✅ Windows 11
- ✅ Microsoft Connected Cache for Enterprise and Education
-ms.date: 10/30/2024
+ms.date: 02/28/2025
---
# Microsoft Connected Cache for Enterprise and Education Requirements
diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md
index ad4ce51e05..c6f31e333e 100644
--- a/windows/deployment/do/mcc-ent-release-notes.md
+++ b/windows/deployment/do/mcc-ent-release-notes.md
@@ -11,7 +11,7 @@ appliesto:
- ✅ Windows 11
- ✅ Supported Linux distributions
- ✅ Microsoft Connected Cache for Enterprise and Education
-ms.date: 10/30/2024
+ms.date: 02/28/2025
---
# Release Notes for Microsoft Connected Cache for Enterprise and Education
diff --git a/windows/deployment/do/mcc-ent-troubleshooting.md b/windows/deployment/do/mcc-ent-troubleshooting.md
index fd4a693300..60f3a726f3 100644
--- a/windows/deployment/do/mcc-ent-troubleshooting.md
+++ b/windows/deployment/do/mcc-ent-troubleshooting.md
@@ -11,7 +11,7 @@ appliesto:
- ✅ Windows 11
- ✅ Supported Linux distributions
- ✅ Microsoft Connected Cache for Enterprise
-ms.date: 01/15/2025
+ms.date: 02/28/2025
---
@@ -97,7 +97,7 @@ If the Connected Cache installation is failing due to WSL-related issues, try ru
Once the Connected Cache software has been successfully deployed to the Windows host machine, you can check if the cache node is running properly by doing the following on the Windows host machine:
1. Launch a PowerShell process as the account specified as the runtime account during the Connected Cache install
-1. Run `wsl -d Ubuntu-22.04-Mcc-Base` to access the Linux distribution that hosts the Connected Cache container
+1. Run `wsl -d Ubuntu-24.04-Mcc-Base` to access the Linux distribution that hosts the Connected Cache container
1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime
If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs -- -f`.