deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-16 02:43:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

fixed acrolinx

Browse Source
This commit is contained in:
chrisjlin
2024-09-30 16:59:39 -07:00
parent 38df7f3984
commit 7afd1e791f
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
windows/deployment/do/mcc-ent-private-preview.md
View File

@ -1,12 +1,12 @@
---
title: MCCE early preview
description: Details on Microsoft Connected Cache for Enterprise (MCCE) early preview.
title: MCCE Private Preview
description: Details on Microsoft Connected Cache for Enterprise (MCCE) Private Preview
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: conceptual
manager: naengler
ms.author: nidos
author: doshnid
ms.author: lichris
author: chrisjlin
appliesto:
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>
ms.date: 06/03/2024
@ -14,11 +14,11 @@ ms.date: 06/03/2024
# Microsoft Connected Cache for Enterprise and Education (MCCE) Private Preview
If you participated in the MCCE Private Preview, thank you for your collaboration and feedback.
If you participated in the MCCE early preview, thank you for your collaboration and feedback.
If you would like to continue using MCCE, you will need to upgrade your cache nodes to the Public Preview release. Existing Private Preview cache nodes will continue to function but can no longer be managed or monitored remotely via the MCCE Azure service.
To continue using MCCE, we strongly recommend that you upgrade your existing cache nodes to the Public Preview release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the MCCE Azure service.
As such, we strongly recommend you [recreate your Private Preview 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 do not need to re-create your MCC Azure resource.
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