mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-16 19:03:46 +00:00
changes to other pages and content in overview page
This commit is contained in:
Nidhi Doshi
@ -20,53 +20,70 @@ ms.date: 05/09/2023
|
||||
|
||||
> [!IMPORTANT]
|
||||
> - Microsoft Connected Cache is currently a preview feature. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
|
||||
> - As we near the release of public preview, we have paused onboarding. Please continue to submit the form to express interest so we can follow up with you once public preview of Microsoft Connected Cache for Enteprise and Education is available. To register your interest, fill out the form located at [https://aka.ms/MSConnectedCacheSignup](https://aka.ms/MSConnectedCacheSignup).
|
||||
|
||||
Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be deployed to as many Windows servers, bare-metal servers, or VMs as needed, and is managed from a cloud portal. Cache nodes are created in the cloud portal and are configured by applying the client policy using management tools such as Intune.
|
||||
Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. MCC can be managed from an Azure portal or through Azure CLI and can be deployed to as many Windows devices, Linux devices, or VMs as needed. Managed Windows devices can be configured to download cloud content from a Connected Cache server by applying the client policy using management tools such as Intune.<br>
|
||||
|
||||
Microsoft Connected Cache (MCC) for Enterprise and Education (early preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](/mem/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
|
||||
Microsoft Connected Cache (MCC) for Enterprise and Education (preview) is a standalone cache for customers moving towards modern management and away from Configuration Manager distribution points. For information about Microsoft Connected Cache in Configuration Manager (generally available, starting Configuration Manager version 2111), see [Microsoft Connected Cache in Configuration Manager](configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
|
||||
|
||||
## Supported scenarios
|
||||
Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux] (windows/wsl/about) and either a [Group Managed Service Account](windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts), local user account, or domain user account are required to run WSL. WSL needs to run in a user context and any user, even if the currently logged-in user, could be used to run WSL and Microsoft Connected Cache.<br>
|
||||
|
||||
Connected Cache (early preview) supports the following scenarios:
|
||||
### Supported scenarios and deployments
|
||||
|
||||
- Pre-provisioning of devices using Windows Autopilot
|
||||
- Cloud-only devices, such as Intune-enrolled devices
|
||||
Microsoft Connected Cache for Enterprise and Education (preview) is intended to support the following content delivery scenarios:<br>
|
||||
* Pre-provisioning of devices using Windows Autopilot<br>
|
||||
* Co-managed clients that get monthly update and Win32 apps from Microsoft Intune. For more information, see Support for Intune Win32 apps.<br>
|
||||
* Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly update and Win32 apps from Microsoft Intune. For more information, see Support for cloud-managed devices.<br>
|
||||
|
||||
## Supported content types
|
||||
Microsoft Connected Cache is built for flexible deployments to support a number of enterprise configurations:
|
||||
|
||||
##### Branch office
|
||||
Customers may have globally dispersed offices that meet the following parameters:
|
||||
* 10 – 50 Windows Clients
|
||||
* No dedicated server hardware
|
||||
* Internet bandwidth is great to limited (satellite internet)
|
||||
* Possibly intermittent connectivity
|
||||
<br>
|
||||
To support the branch the branch office scenario, customers can deploy to a Windows 11 client (see Host machine requirements) device.
|
||||
|
||||
##### Large Enterprise
|
||||
Customers may have office spaces, data centers, or Azure deployments that meet the following parameters:
|
||||
* 100's or 1,000's of Windows devices (client or server).
|
||||
* Existing hardware – Decommissioned DP, file server, cloud print server
|
||||
* Azure VMs and Azure Virtual Desktop
|
||||
* Internet bandwidth is great to limited (T1)
|
||||
|
||||
|
||||
### Supported content types
|
||||
When clients download cloud-managed content, they use Delivery Optimization from the cache server installed on a Windows server or VM. Cloud-managed content includes the following types:
|
||||
* Windows updates: Windows feature and quality updates
|
||||
* Office Click-to-Run apps: Microsoft 365 Apps and updates
|
||||
* Client apps: Intune, store apps, and updates
|
||||
* Endpoint protection: Windows Defender definition updates
|
||||
|
||||
- Windows updates: Windows feature and quality updates
|
||||
- Office Click-to-Run apps: Microsoft 365 Apps and updates
|
||||
- Client apps: Intune, store apps, and updates
|
||||
- Endpoint protection: Windows Defender definition updates
|
||||
For the full list of content endpoints that Microsoft Connected Cache for Enterprise and Education supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).<br>
|
||||
|
||||
For the full list of content endpoints that Microsoft Connected Cache for Enterprise and Education supports, see [Microsoft Connected Cache content and services endpoints](delivery-optimization-endpoints.md).
|
||||
### Hardware or VM Requirements
|
||||
See [Host machine requirements](mcc-ent-prerequisites.md) for complete details.
|
||||
|
||||
|Deployment Scenarios| Download Speed Range | Download Speeds and Content Volume Delivered in 8 Hours | VM/Hardware Recommendation |
|
||||
|---|---|---|---|
|
||||
|Branch Office|< 1 Gbps Peak| 500 Mbps - 1,800 GB </br></br> 250 Mbps - 900 GB </br></br> 100 Mbps - 360 GB </br></br> 50 Mbps - 180 GB| 4 Cores </br></br> Up to 8 GB Memory with 4 GB of Free </br></br> 100 GB free disk space|
|
||||
|Small to Medium Enterprises/Autopilot Provisioning Center - 50 - 500 devices in a single location|1 - 5 Gbps| 5 Gbps - 18,000 GB </br></br>3 Gbps - 10,800 GB </br></br>1 Gbps - 3,600 GB| 8 Cores </br></br> Up to 16 GB Memory with 4 GB of Free </br></br> 500 GB free disk space|
|
||||
|Medium to Large Enterprises/Autopilot Provisioning Center - 500 - 5,000 devices|5 - 101 Gbps Peak| 9 Gbps - 32,400 GB </br></br> 5 Gbps - 18,000 GB </br></br>3 Gbps - 10,800 GB| 16 Cores</br></br> 32 GB Memory with 4 GB of Free </br></br> 2 200-500 GB SSDs|
|
||||
|
||||
<br>
|
||||
|
||||
## How it works
|
||||
|
||||
MCC is a hybrid (mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module and Docker compatible Linux container deployed to your Windows devices. The Delivery Optimization team chose IoT Edge for Linux on Windows (EFLOW) as a secure, reliable container management infrastructure. EFLOW is a Linux virtual machine, based on Microsoft's first party CBL-Mariner operating system. It's built with the IoT Edge runtime and validated as a tier 1 supported environment for IoT Edge workloads. MCC is a Linux IoT Edge module running on the Windows Host OS.
|
||||
|
||||
1. The Azure Management Portal is used to create MCC nodes.
|
||||
1. The MCC container is deployed and provisioned to the server using the installer provided in the portal.
|
||||
1. Client policy is set in your management solution to point to the IP address or FQDN of the cache server.
|
||||
1. Microsoft end-user devices make range requests for content from the MCC node.
|
||||
1. The MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
|
||||
1. Subsequent requests from end-user devices for content will now come from cache.
|
||||
1. If the MCC node is unavailable, the client pulls content from CDN to ensure uninterrupted service for your subscribers.
|
||||
1. The Azure management portal for Microsoft Connected Cache or CLI are used to create cache nodes, configure deployments, including unauthenticated proxy settings.
|
||||
1. Prepare Windows or Linux devices. If deploying to Windows devices, prepare accounts - gMSA, local user account, domain account. Deploy to Windows or Linux devices using scripts.
|
||||
1. The Microsoft Connected Cache container is deployed to the device using Azure IoT Edge container management services and the cache server begins reporting status and metrics to Delivery Optimization services.
|
||||
1. The DOCacheHost setting is configured using Intune or other MDM, DHCP custom option, or registry key.
|
||||
1. Devices request content from the cache server, the cache server forwards the requests to the CDN and fills the cache, the cache server delivers the content requested to the devices, and uses Peer to Peer (depending on DO Download mode settings) for all DO content.
|
||||
1. Devices can fallback to CDN if cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN )settings to prefer the local cache server.
|
||||
Customers can view data regarding Microsoft Connected Cache downloads on management portal and Windows Update for Business reports
|
||||
|
||||
The following diagram displays an overview of how MCC functions:
|
||||
|
||||
<!--
|
||||
:::image type="content" source="./images/waas-mcc-diag-overview.png" alt-text="Diagram displaying the components of MCC." lightbox="./images/waas-mcc-diag-overview.png":::
|
||||
|
||||
## IoT Edge
|
||||
|
||||
Even though your MCC scenario isn't related to IoT, Azure IoT Edge is used as a more generic Linux container deployment and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs several functions important to manage MCC on your edge device:
|
||||
|
||||
1. Installs and updates MCC on your edge device.
|
||||
1. Maintains Azure IoT Edge security standards on your edge device.
|
||||
1. Ensures that MCC is always running.
|
||||
1. Reports MCC health and usage to the cloud for remote monitoring.
|
||||
|
||||
For more information on Azure IoT Edge, see the Azure IoT Edge [documentation](/azure/iot-edge/about-iot-edge).
|
||||
-->
|
||||
|
||||
@ -25,7 +25,13 @@ This article outlines how to create, configure, and deploy Microsoft Connected C
|
||||
|
||||
## Prerequisites:
|
||||
1. **Install Azure CLI**: [How to install the Azure CLI](/cli/azure/install-azure-cli)
|
||||
1. **Install MCC extension**: [Install the MCC extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
|
||||
1. **Install MCC extension**: Install MCC extension via the command below
|
||||
|
||||
```azurecli-interactive
|
||||
az extension add --name mcc
|
||||
```
|
||||
|
||||
To learn more about installting extensions, visit [Install the MCC extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
|
||||
|
||||
<br>
|
||||
<br>
|
||||
@ -67,7 +73,7 @@ The next step is to create a cache node under this resource.
|
||||
To create a cache node, use `az mcc ent node create`
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg --host-os linux
|
||||
az mcc ent node create --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg --host-os <linux or windows>
|
||||
```
|
||||
|
||||
<br>
|
||||
|
||||
@ -1,149 +0,0 @@
|
||||
---
|
||||
title: MCC for Enterprise monitor cache nodes
|
||||
description: Microsoft Connected Cache for Enterprise. Learn about how to monitor cache node.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
manager: aaroncz
|
||||
ms.author: nidos
|
||||
author: doshnid
|
||||
ms.reviewer: mstewart
|
||||
ms.collection: tier3
|
||||
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</a>
|
||||
ms.date: 09/04/2024
|
||||
---
|
||||
|
||||
<!--
|
||||
Remove all the comments in this template before you sign-off or merge to the main branch.
|
||||
|
||||
This template provides the basic structure of a How-to article pattern. See the
|
||||
[instructions - How-to](../level4/article-how-to-guide.md) in the pattern library.
|
||||
|
||||
You can provide feedback about this template at: https://aka.ms/patterns-feedback
|
||||
|
||||
How-to is a procedure-based article pattern that show the user how to complete a task in their own environment. A task is a work activity that has a definite beginning and ending, is observable, consist of two or more definite steps, and leads to a product, service, or decision.
|
||||
|
||||
-->
|
||||
|
||||
<!-- 1. H1 -----------------------------------------------------------------------------
|
||||
|
||||
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
|
||||
|
||||
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
|
||||
|
||||
* Include only a single H1 in the article.
|
||||
* Don't start with a gerund.
|
||||
* Don't include "Tutorial" in the H1.
|
||||
|
||||
-->
|
||||
|
||||
# "<verb> * <noun>"
|
||||
TODO: Add your heading
|
||||
|
||||
<!-- 2. Introductory paragraph ----------------------------------------------------------
|
||||
|
||||
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
|
||||
|
||||
Readers should have a clear idea of what they will do in this article after reading the introduction.
|
||||
|
||||
* Introduction immediately follows the H1 text.
|
||||
* Introduction section should be between 1-3 paragraphs.
|
||||
* Don't use a bulleted list of article H2 sections.
|
||||
|
||||
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
|
||||
|
||||
-->
|
||||
|
||||
TODO: Add your introductory paragraph
|
||||
|
||||
<!---Avoid notes, tips, and important boxes. Readers tend to skip over them. Better to put that info directly into the article text.
|
||||
|
||||
-->
|
||||
|
||||
<!-- 3. Prerequisites --------------------------------------------------------------------
|
||||
|
||||
Required: Make Prerequisites the first H2 after the H1.
|
||||
|
||||
* Provide a bulleted list of items that the user needs.
|
||||
* Omit any preliminary text to the list.
|
||||
* If there aren't any prerequisites, list "None" in plain text, not as a bulleted item.
|
||||
|
||||
-->
|
||||
|
||||
## Prerequisites
|
||||
|
||||
TODO: List the prerequisites
|
||||
|
||||
<!-- 4. Task H2s ------------------------------------------------------------------------------
|
||||
|
||||
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
|
||||
|
||||
For portal-based procedures, minimize bullets and numbering.
|
||||
|
||||
* Each H2 should be a major step in the task.
|
||||
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
|
||||
* Don't start with a gerund.
|
||||
* Don't number the H2s.
|
||||
* Begin each H2 with a brief explanation for context.
|
||||
* Provide a ordered list of procedural steps.
|
||||
* Provide a code block, diagram, or screenshot if appropriate
|
||||
* An image, code block, or other graphical element comes after numbered step it illustrates.
|
||||
* If necessary, optional groups of steps can be added into a section.
|
||||
* If necessary, alternative groups of steps can be added into a section.
|
||||
|
||||
-->
|
||||
|
||||
## "\<verb\> * \<noun\>"
|
||||
TODO: Add introduction sentence(s)
|
||||
[Include a sentence or two to explain only what is needed to complete the procedure.]
|
||||
TODO: Add ordered list of procedure steps
|
||||
1. Step 1
|
||||
1. Step 2
|
||||
1. Step 3
|
||||
|
||||
## "\<verb\> * \<noun\>"
|
||||
TODO: Add introduction sentence(s)
|
||||
[Include a sentence or two to explain only what is needed to complete the procedure.]
|
||||
TODO: Add ordered list of procedure steps
|
||||
1. Step 1
|
||||
1. Step 2
|
||||
1. Step 3
|
||||
|
||||
## "\<verb\> * \<noun\>"
|
||||
TODO: Add introduction sentence(s)
|
||||
[Include a sentence or two to explain only what is needed to complete the procedure.]
|
||||
TODO: Add ordered list of procedure steps
|
||||
1. Step 1
|
||||
1. Step 2
|
||||
1. Step 3
|
||||
|
||||
<!-- 5. Next step/Related content------------------------------------------------------------------------
|
||||
|
||||
Optional: You have two options for manually curated links in this pattern: Next step and Related content. You don't have to use either, but don't use both.
|
||||
- For Next step, provide one link to the next step in a sequence. Use the blue box format
|
||||
- For Related content provide 1-3 links. Include some context so the customer can determine why they would click the link. Add a context sentence for the following links.
|
||||
|
||||
-->
|
||||
|
||||
## Next step
|
||||
|
||||
TODO: Add your next step link(s)
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Write concepts](article-concept.md)
|
||||
|
||||
<!-- OR -->
|
||||
|
||||
## Related content
|
||||
|
||||
TODO: Add your next step link(s)
|
||||
|
||||
- [Write concepts](article-concept.md)
|
||||
|
||||
<!--
|
||||
Remove all the comments in this template before you sign-off or merge to the main branch.
|
||||
-->
|
||||
|
||||
@ -14,9 +14,9 @@ appliesto:
|
||||
ms.date: 09/04/2024
|
||||
---
|
||||
|
||||
# Monitor MCCE cache node usage
|
||||
# Monitor MCC cache node usage
|
||||
|
||||
Tracking the status and performance of your MCCE cache node is essential to making sure that you're getting the most out of the service.
|
||||
Tracking the status and performance of your MCC cache node is essential to making sure that you're getting the most out of the service.
|
||||
|
||||
<!-- Add standard metrics
|
||||
|
||||
@ -28,7 +28,7 @@ The Cache Node Summary box on your Azure portal
|
||||
|
||||
| Metric | Description |
|
||||
| --- | --- |
|
||||
| Healthy nodes | The MCCE service will periodically request heartbeat messages from your MCC node to determine if it's functioning as expected. |
|
||||
| Healthy nodes | The MCC service will periodically request heartbeat messages from your MCC node to determine if it's functioning as expected. |
|
||||
| Unhealthy nodes | If the cache node doesn't respond, it is labeled as unhealthy. |
|
||||
| Max in | The maximum egress (in Mb/sec.) that your node has pulled in at any given time. This statistic isn't dependent on the time filter near the charts. |
|
||||
| Max out | The minimum egress (in Mb/sec.) that your node has pushed out at any given time. |
|
||||
@ -49,7 +49,7 @@ The Cache Node Summary box on your Azure portal
|
||||
|
||||
### Volume by Content Type
|
||||
|
||||
- The volume of content that your MCCE cache node is distributing, broken down by the hostname used to download said content
|
||||
- The volume of content that your MCC cache node is distributing, broken down by the hostname used to download said content
|
||||
|
||||
## Additional metrics
|
||||
|
||||
|
||||
@ -13,13 +13,13 @@ appliesto:
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education Requirements (Public Preview)
|
||||
# Microsoft Connected Cache for Enterprise and Education Requirements
|
||||
|
||||
This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE).
|
||||
This article details the requirements and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC).
|
||||
|
||||
## Licensing requirements
|
||||
|
||||
- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCCE) service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management).
|
||||
- **Valid Azure subscription**: To use the Microsoft Connected Cache for Enterprise and Education (MCC) service, you'll need a valid Azure subscription that can be used to provision the necessary [Azure resources](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management).
|
||||
|
||||
If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/).
|
||||
|
||||
|
||||
@ -12,43 +12,15 @@ appliesto:
|
||||
ms.date: 06/03/2024
|
||||
---
|
||||
|
||||
<<<<<<< HEAD
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education (early preview)
|
||||
|
||||
> [!NOTE]
|
||||
> Microsoft Connected Cache for Enterprise and Education is now in public preview.
|
||||
> To know more about the program, visit [MCC program overview](mcc-ent-edu-overview.md).
|
||||
|
||||
<br>
|
||||
|
||||
Microsoft Connected Cache for Enterprise and Education is now in public preview. To get started, visit [Create MCC resource and cache node](mcc-ent-create-resource-and-cache.md)
|
||||
|
||||
>[!IMPORTANT]
|
||||
> If you are using the early preview version on MCC, please uninstall and delete the early preview cache node and the associated MCC resource and create a new one. To create a new MCC resource, visit [Create MCC resource and cache node](mcc-ent-create-resource-and-cache.md)
|
||||
|
||||
<br>
|
||||
## Enterprise requirements for MCC
|
||||
|
||||
1. **Azure subscription**: MCC management portal is hosted within Azure and is used to create the Connected Cache [Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management) and IoT Hub resource. Both are free services.
|
||||
|
||||
Your Azure subscription ID is first used to provision MCC services, and enable access to the preview. The MCC server requirement for an Azure subscription costs you nothing. If you don't have an Azure subscription already, you can create an Azure [pay-as-you-go](https://azure.microsoft.com/offers/ms-azr-0003p/) account, which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/).
|
||||
|
||||
The resources used for the preview and in the future when this product is ready for production will be free to you, like other caching solutions.
|
||||
1. **Hardware to host MCC**: The recommended configuration serves approximately 35,000 managed devices, downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.<br>
|
||||
For more information, visit [Hardware Requirments](mcc-ent-prerequisites.md)
|
||||
|
||||
=======
|
||||
# Microsoft Connected Cache for Enterprise and Education (MCCE) Private Preview
|
||||
|
||||
If you participated in the MCCE early preview, thank you for your collaboration and feedback.
|
||||
|
||||
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.
|
||||
To continue using Microsoft Connected Cache for Enterprise and Education (MCC), we strongly recommend that you upgrade your existing cache nodes to the new release. Cache nodes created and deployed during early preview should still function but can no longer be managed or monitored remotely via the MCC Azure service.
|
||||
|
||||
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
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [View documentation for MCCE Public Preview](mcc-ent-edu-overview.md)
|
||||
>>>>>>> baff7906fe02b76b4a3649d7e6c3acdac9534e66
|
||||
> [View documentation for MCC Public Preview](mcc-ent-edu-overview.md)
|
||||
|
||||
@ -14,9 +14,9 @@ appliesto:
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
|
||||
# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE)
|
||||
# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC)
|
||||
|
||||
This article contains details about the latest releases of MCCE. Since MCCE is a Preview service, some releases may contain breaking changes that will be highlighted as such.
|
||||
This article contains details about the latest releases of MCC. Since MCC is a Preview service, some releases may contain breaking changes that will be highlighted as such.
|
||||
|
||||
## Release v0.1.0 (Public Preview launch)
|
||||
|
||||
@ -37,4 +37,4 @@ This article contains details about the latest releases of MCCE. Since MCCE is a
|
||||
|
||||
## Related content
|
||||
|
||||
- [Overview of MCCE](mcc-ent-edu-overview.md)
|
||||
- [Overview of MCC](mcc-ent-edu-overview.md)
|
||||
|
||||
@ -16,73 +16,24 @@ ms.date: 09/27/2024
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCC)
|
||||
|
||||
This article contains instructions on how to troubleshoot different issues you may encounter while using MCC. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache.md).
|
||||
|
||||
|
||||
## Steps to obtain an Azure subscription ID
|
||||
|
||||
<!--Using include file, get-azure-subscription.md, do/mcc-isp.md for shared content-->
|
||||
[!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)]
|
||||
|
||||
|
||||
<<<<<<< HEAD
|
||||
|
||||
TODO: List the prerequisites
|
||||
|
||||
<!-- 4. Task H2s ------------------------------------------------------------------------------
|
||||
|
||||
Required: Multiple procedures should be organized in H2 level sections. A section contains a major grouping of steps that help users complete a task. Each section is represented as an H2 in the article.
|
||||
|
||||
For portal-based procedures, minimize bullets and numbering.
|
||||
|
||||
* Each H2 should be a major step in the task.
|
||||
* Phrase each H2 title as "<verb> * <noun>" to describe what they'll do in the step.
|
||||
* Don't start with a gerund.
|
||||
* Don't number the H2s.
|
||||
* Begin each H2 with a brief explanation for context.
|
||||
* Provide a ordered list of procedural steps.
|
||||
* Provide a code block, diagram, or screenshot if appropriate
|
||||
* An image, code block, or other graphical element comes after numbered step it illustrates.
|
||||
* If necessary, optional groups of steps can be added into a section.
|
||||
* If necessary, alternative groups of steps can be added into a section.
|
||||
|
||||
-->
|
||||
|
||||
## "\<verb\> * \<noun\>"
|
||||
=======
|
||||
<!-- 1. H1 -----------------------------------------------------------------------------
|
||||
|
||||
Required: Use a "<verb> * <noun>" format for your H1. Pick an H1 that clearly conveys the task the user will complete.
|
||||
|
||||
For example: "Migrate data from regular tables to ledger tables" or "Create a new Azure SQL Database".
|
||||
|
||||
* Include only a single H1 in the article.
|
||||
* Don't start with a gerund.
|
||||
* Don't include "Tutorial" in the H1.
|
||||
|
||||
-->
|
||||
|
||||
# Troubleshoot Microsoft Connected Cache for Enterprise and Education (MCCE)
|
||||
|
||||
<!-- 2. Introductory paragraph ----------------------------------------------------------
|
||||
|
||||
Required: Lead with a light intro that describes, in customer-friendly language, what the customer will do. Answer the fundamental “why would I want to do this?” question. Keep it short.
|
||||
|
||||
Readers should have a clear idea of what they will do in this article after reading the introduction.
|
||||
|
||||
* Introduction immediately follows the H1 text.
|
||||
* Introduction section should be between 1-3 paragraphs.
|
||||
* Don't use a bulleted list of article H2 sections.
|
||||
|
||||
Example: In this article, you will migrate your user databases from IBM Db2 to SQL Server by using SQL Server Migration Assistant (SSMA) for Db2.
|
||||
|
||||
-->
|
||||
|
||||
This article contains instructions on how to troubleshoot different issues you may encounter while using MCCE. These issues are categorized by the task in which they may be encountered. For example, this next section covers troubleshooting [MCC Azure resource creation](mcc-ent-create-resource-and-cache.md).
|
||||
|
||||
## Troubleshooting Azure resource creation
|
||||
|
||||
MCC Azure resource creation can be initiated using either the Azure portal or the Azure CLI command set. If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields.
|
||||
|
||||
## Troubleshooting cache node creation
|
||||
>>>>>>> baff7906fe02b76b4a3649d7e6c3acdac9534e66
|
||||
TODO: Add introduction sentence(s)
|
||||
[Include a sentence or two to explain only what is needed to complete the procedure.]
|
||||
TODO: Add ordered list of procedure steps
|
||||
|
||||
@ -14,18 +14,18 @@ appliesto:
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
|
||||
# Uninstall MCCE caching software from a host machine
|
||||
# Uninstall MCC caching software from a host machine
|
||||
|
||||
This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal.
|
||||
This article describes how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) caching software from a host machine. These steps should be taken after deleting the cache node in the Azure portal.
|
||||
|
||||
## Steps to uninstall MCCE from a Windows host machine
|
||||
## Steps to uninstall MCC from a Windows host machine
|
||||
|
||||
1. Launch a PowerShell window *as administrator* and navigate to the MCC installation directory (C:\mcconwsl01 by default)
|
||||
1. Run the `uninstallmcconwsl.ps1` script
|
||||
|
||||
## Steps to uninstall MCCE from a Linux host machine
|
||||
## Steps to uninstall MCC from a Linux host machine
|
||||
|
||||
The `uninstallmcc.sh` script within the provisioning package uninstalls the MCCE caching software and all related components, including:
|
||||
The `uninstallmcc.sh` script within the provisioning package uninstalls the MCC caching software and all related components, including:
|
||||
|
||||
- IoT Edge
|
||||
- IoT Edge Agent
|
||||
|
||||
@ -1,55 +0,0 @@
|
||||
---
|
||||
title: Uninstall MCC for Enterprise and Education
|
||||
description: Details on how to uninstall Microsoft Connected Cache (MCC) for Enterprise and Education for your environment.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
manager: aaroncz
|
||||
ms.reviewer: mstewart
|
||||
ms.collection:
|
||||
- tier3
|
||||
- must-keep
|
||||
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: 05/23/2024
|
||||
---
|
||||
|
||||
<!-- Customers will no longer update the private preview and instead install public preview
|
||||
# Update or uninstall Microsoft Connected Cache for Enterprise and Education
|
||||
|
||||
Throughout the preview phase, we'll send you security and feature updates for MCC. Follow these steps to perform the update.
|
||||
|
||||
## Update MCC
|
||||
|
||||
Run the following command with the **arguments** we provided in the email to update your MCC:
|
||||
|
||||
```powershell
|
||||
# .\updatemcc.ps1 version="**\<VERSION\>**" tenantid="**\<TENANTID\>**" customerid="**\<CUSTOMERID\>**" cachenodeid="**\<CACHENODEID\>**" customerkey="**\<CUSTOMERKEY\>**"
|
||||
```
|
||||
|
||||
For example:
|
||||
|
||||
```powershell
|
||||
# .\updatemcc.ps1 version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.659" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99a"
|
||||
```
|
||||
-->
|
||||
# Uninstall MCC
|
||||
|
||||
Contact the MCC Team before uninstalling to let us know if you're facing issues.
|
||||
|
||||
This script removes the following items:
|
||||
|
||||
1. EFLOW + Linux VM
|
||||
1. IoT Edge
|
||||
1. Edge Agent
|
||||
1. Edge Hub
|
||||
1. MCC
|
||||
1. Moby CLI
|
||||
1. Moby Engine
|
||||
|
||||
To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT
|
||||
Edge LTS \> Uninstall
|
||||
@ -14,15 +14,15 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
# Verify MCCE cache node functionality
|
||||
# Verify MCC cache node functionality
|
||||
|
||||
This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCCE) cache node is functioning correctly.
|
||||
This article describes how to verify that a Microsoft Connected Cache for Enterprise and Education (MCC) cache node is functioning correctly.
|
||||
|
||||
These steps should be taken after deploying MCCE caching software to a [Windows](mcc-ent-deploy-to-windows.md) or [Linux](mcc-ent-deploy-to-linux.md) host machine.
|
||||
|
||||
## Steps to verify functionality of MCCE cache node
|
||||
|
||||
1. To verify that the MCCE container on the host machine is running and reachable, run the following command from the host machine:
|
||||
1. To verify that the MCC container on the host machine is running and reachable, run the following command from the host machine:
|
||||
|
||||
```powershell
|
||||
wget http://localhost/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com
|
||||
@ -30,13 +30,13 @@ These steps should be taken after deploying MCCE caching software to a [Windows]
|
||||
|
||||
If successful, there should be an HTTP response with StatusCode 200.
|
||||
|
||||
1. To verify that Windows clients in your network can reach the MCCE cache node, visit the following address from a web browser on a Windows client device:
|
||||
1. To verify that Windows clients in your network can reach the MCC cache node, visit the following address from a web browser on a Windows client device:
|
||||
|
||||
`http://[HostMachine-IP-address]/filestreamingservice/files/7bc846e0-af9c-49be-a03d-bb04428c9bb5/Microsoft.png?cacheHostOrigin=dl.delivery.mp.microsoft.com`
|
||||
|
||||
If successful, the Windows client device should begin to download a small image file from the MCCE cache node.
|
||||
|
||||
1. To check how much content an individual Windows client has pulled from an MCCE cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
|
||||
1. To check how much content an individual Windows client has pulled from an MCC cache node, open the [Delivery Optimization activity monitor](/microsoft-365-apps/updates/delivery-optimization#viewing-data-about-the-use-of-delivery-optimization) on the Windows client device.
|
||||
|
||||
You should see a donut chart titled Download Statistics. If the Windows client has pulled content from the cache node, you'll see a segment of the donut labeled "From Microsoft cache server".
|
||||
|
||||
|
||||
Reference in New Issue
Block a user