deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

edit ubuntu ver, update metadata

Browse Source
This commit is contained in:
Meghan Stewart 2025-02-28 14:06:14 -08:00
parent ca43764e1b
commit 8f84a753a7
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
windows/deployment/do/mcc-ent-edu-overview.md
View File

@ -13,7 +13,7 @@ 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: 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.

2
windows/deployment/do/mcc-ent-prerequisites.md
View File

@ -10,7 +10,7 @@ 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/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
ms.date: 10/30/2024
ms.date: 02/28/2025
---
# Microsoft Connected Cache for Enterprise and Education Requirements

2
windows/deployment/do/mcc-ent-release-notes.md
View File

@ -11,7 +11,7 @@ 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: 10/30/2024
ms.date: 02/28/2025
---
# Release Notes for Microsoft Connected Cache for Enterprise and Education

4
windows/deployment/do/mcc-ent-troubleshooting.md
View File

@ -11,7 +11,7 @@ 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</a>
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`.