From 18d4fa6efac498ffb2e070e82d4d1958e4c6b138 Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Thu, 27 Feb 2025 11:11:19 -0800 Subject: [PATCH 1/4] Feb 2025 release notes, update to host os prereqs --- .../deployment/do/mcc-ent-prerequisites.md | 4 +- .../deployment/do/mcc-ent-release-notes.md | 45 ++++++++++++++++--- 2 files changed, 42 insertions(+), 7 deletions(-) diff --git a/windows/deployment/do/mcc-ent-prerequisites.md b/windows/deployment/do/mcc-ent-prerequisites.md index 7c95fc63fb..c9e99fa963 100644 --- a/windows/deployment/do/mcc-ent-prerequisites.md +++ b/windows/deployment/do/mcc-ent-prerequisites.md @@ -43,7 +43,7 @@ This article details the requirements and recommended specifications for using M ### Additional requirements for Windows host machines -- The Windows host machine must be using Windows 11 or Windows Server 2022 with the latest cumulative update applied. +- The Windows host machine must be using Windows 11 or Windows Server 2022 (or later) with the latest cumulative update 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. Ensure that any security settings that may restrict nested virtualization are not enabled, such as ["Trusted launch" in Azure VMs](/azure/virtual-machines/trusted-launch-portal). @@ -52,7 +52,7 @@ This article details the requirements and recommended specifications for using M ### Additional requirements for Linux host machines - The Linux host machine must be using one of the following operating systems: - - Ubuntu 22.04, 24.04 + - Ubuntu 24.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) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index 774d9cd43f..adc2e89934 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -18,11 +18,42 @@ ms.date: 10/30/2024 This article contains details about the latest releases of Connected Cache. Since Connected Cache is a preview service, some releases may contain breaking changes. -## Install script v2.0.0.2 +## February 2025 Release + +Released on **2/27/2025** + +This release contains improvements that can only be applied by redeploying your cache nodes using the updated installation script. + +### New Connected Cache container version + +- v1.2.1.2083_E + +### New Linux-hosted installation script version + +- v1.08 + +### New Windows-hosted installation script version + +- v2.0.0.3 + +### Improvements to Windows-hosted cache nodes + +- **Connected Cache WSL distribution now uses Ubuntu 24.04**: The Windows Subsystem for Linux (WSL) distribution used by Connected Cache has been updated to Ubuntu 24.04 (was 22.04). This change ensures that the WSL distribution is up-to-date with the latest security patches and features. +- **Connected Cache container now uses Ubuntu 24.04 Docker environment**: The Connected Cache container now runs using an Ubuntu 24.04 Docker environment (was 22.04). This change ensures that the container environment is up-to-date with the latest security patches and features. +- **TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation**: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation. +- **Security improvements**: Kept intentionally vague to protect previous versions of Connected Cache. + +### Improvements to Linux-hosted cache nodes + +- **Connected Cache container now uses Ubuntu 24.04 Docker environment**: The Connected Cache container now runs using an Ubuntu 24.04 Docker environment (was 22.04). This change ensures that the container environment is up-to-date with the latest security patches and features. +- **TLS-inspecting proxies no longer cause IoT Edge error during Connected Cache installation**: Fixed a bug that was causing proxy certificate path string to be improperly handled, leading to IoT Edge errors during Connected Cache installation. +- **Security improvements**: Kept intentionally vague to protect previous versions of Connected Cache. + +## Windows-hosted install script v2.0.0.2 Released on **2/7/2025** -These changes only affect the installation scripts for Connected Cache. To take advantage of these changes, you'll need to redeploy your existing cache nodes using the updated installation script. +This release only contains changes to the Windows-hosted installation scripts for Connected Cache. To take advantage of these changes, you need to redeploy your existing cache nodes using the updated installation script. ### Improvements @@ -31,11 +62,15 @@ These changes only affect the installation scripts for Connected Cache. To take - **Changes install error codes from decimal to hex code**: Install error codes for Windows-hosted cache nodes are now displayed in hex code format, improving error code readability. - **Uses configured proxy to perform install**: If a proxy was configured for the Windows-hosted cache node in Azure portal, the cache node uses the specified proxy during installation. -## Release v1.2.1.2076_E (public preview launch) +## Public Preview Release -The public preview released on **10/30/2024** +Released on **10/30/2024** -For customers that installed earlier versions of Connected Cache, this release contains breaking changes that affect both Linux and Windows host machines. See the [early preview documentation page](mcc-ent-early-preview.md) for more details. +For customers that installed earlier versions of Connected Cache, this release contains breaking changes that affect both Linux-hosted and Windows-hosted cache nodes. See the [early preview documentation page](mcc-ent-early-preview.md) for more details. + +### New Connected Cache container version + +- v1.2.1.2076_E ### Feature updates From 1873964ffaffa6e2985306cdae0054a0b8fce50e Mon Sep 17 00:00:00 2001 From: chrisjlin <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 28 Feb 2025 12:01:03 -0800 Subject: [PATCH 2/4] update to release date --- windows/deployment/do/mcc-ent-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index adc2e89934..ad4ce51e05 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -20,7 +20,7 @@ This article contains details about the latest releases of Connected Cache. Sinc ## February 2025 Release -Released on **2/27/2025** +Released on **2/28/2025** This release contains improvements that can only be applied by redeploying your cache nodes using the updated installation script. From 8f84a753a7011b27954de041ef40941041cebeac Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Fri, 28 Feb 2025 14:06:14 -0800 Subject: [PATCH 3/4] edit ubuntu ver, update metadata --- windows/deployment/do/mcc-ent-edu-overview.md | 4 ++-- windows/deployment/do/mcc-ent-prerequisites.md | 2 +- windows/deployment/do/mcc-ent-release-notes.md | 2 +- windows/deployment/do/mcc-ent-troubleshooting.md | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) 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`. From 0ff344207e78c9575f8ab54eddbd332a53f1b494 Mon Sep 17 00:00:00 2001 From: "Chris J. Lin" <36452239+chrisjlin@users.noreply.github.com> Date: Fri, 28 Feb 2025 15:04:58 -0800 Subject: [PATCH 4/4] Update mcc-ent-release-notes.md Updated release date --- windows/deployment/do/mcc-ent-release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-release-notes.md b/windows/deployment/do/mcc-ent-release-notes.md index c6f31e333e..9b566f4e6c 100644 --- a/windows/deployment/do/mcc-ent-release-notes.md +++ b/windows/deployment/do/mcc-ent-release-notes.md @@ -20,7 +20,7 @@ This article contains details about the latest releases of Connected Cache. Sinc ## February 2025 Release -Released on **2/28/2025** +Released on **3/03/2025** This release contains improvements that can only be applied by redeploying your cache nodes using the updated installation script.