deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-07-10 14:43:42 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Added notes that TLS-inspecting proxies must allow calls to DO service (*.prod.do.dsp.mp.microsoft.com)

Browse Source
This commit is contained in:
chrisjlin
2025-07-07 19:53:52 -07:00
parent 67f16bdaf8
commit cc0d9a6262
3 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
windows/deployment/do/mcc-ent-deploy-to-linux.md
View File

@ -19,6 +19,8 @@ This article describes how to deploy Microsoft Connected Cache for Enterprise an
Before deploying Connected Cache 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 Connected Cache Azure resource and cache node](mcc-ent-create-resource-and-cache.md).
For Connected Cache deployment to succeed, you must allow direct calls to the Delivery Optimization service from your devices. When using a TLS-inspecting proxy, you must configure your proxy/host machine to allow calls to and from the Delivery Optimization service (*.prod.do.dsp.mp.microsoft.com).
## Steps to deploy Connected Cache cache node to Linux
# [Azure portal](#tab/portal)

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

@ -21,6 +21,8 @@ Deploying Connected Cache to a Windows host machine requires designating a [Grou
Before deploying Connected Cache 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 Connected Cache Azure resource](mcc-ent-create-resource-and-cache.md).
For Connected Cache deployment to succeed, you must allow direct calls to the Delivery Optimization service from your devices. When using a TLS-inspecting proxy, you must configure your proxy/host machine to allow calls to and from the Delivery Optimization service (*.prod.do.dsp.mp.microsoft.com).
## Steps to deploy Connected Cache node to Windows
# [Azure portal](#tab/portal)

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

@ -46,7 +46,7 @@ This release contains improvements that can only be applied by redeploying your
### 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.
- **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. Added an intermediate certificate verification step to the installation process on both Windows-hosted and Linux-hosted cache nodes. Calls to *.prod.do.dsp must be enabled for installation to succeed.
- **Security improvements**: Kept intentionally vague to protect previous versions of Connected Cache.
## Windows-hosted install script v2.0.0.2