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

additional changes

Browse Source
This commit is contained in:
chrisjlin
2024-09-30 11:03:42 -07:00
parent 6747a66585
commit 34f7ff9181
15 changed files with 164 additions and 265 deletions
Download Patch File Download Diff File Expand all files Collapse all files

79
windows/deployment/do/mcc-ent-create-resource-and-cache.md
View File

@ -1,31 +1,29 @@
--- ---
title: MCC for Enterprise provision create cache node title: Create and configure MCCE cache nodes
description: Microsoft Connected Cache for Enterprise. Learn about how to create cache node. description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
manager: aaroncz manager: naengler
ms.author: nidos ms.author: nidos
author: doshnid author: doshnid
ms.reviewer: mstewart
ms.collection: tier3
appliesto: 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 11</a>
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</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> - ✅ <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 ms.date: 06/03/2024
--- ---
# Create MCC resource and cache nodes # Create MCCE Azure resource and cache nodes
This article outlines how to create and configure your Microsoft Connected Cache for Enterprise cache nodes. The creation and configuration of your cache node takes place in Azure portal. The deployment of your cache node requires downloading an installer script that will need to be run on your cache server. This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes. The creation and configuration of your cache node takes place in Azure. The deployment of your cache node requires downloading and running an OS-specific provisioning package on your host machine.
## Prerequisites ## Prerequisites
1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a completely free-of-charge service hosted in Azure. You'll need to have a Pay-As-You-Go subscription in order to onboard to our service. To create a subscription, go to [Pay-As-You-Go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/). 1. **Azure Pay-As-You-Go subscription**: Microsoft Connected Cache is a free-of-charge service hosted in Azure. You'll need a pay-as-you-go Azure subscription in order to onboard to our service. To create a subscription, go to [pay-as-you-go subscription page](https://azure.microsoft.com/offers/ms-azr-0003p/).
2. **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. 2. **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.
For more information on sizing and OS requirements, please visit [Host OS Requirement](mcc-ent-prerequisites.md) For more information on sizing and OS requirements, see [the prerequisites for using MCCE](mcc-ent-prerequisites.md).
## Create MCC resource ## Create MCCE Azure resource
# [Azure portal](#tab/portal) # [Azure portal](#tab/portal)
@ -34,13 +32,13 @@ For more information on sizing and OS requirements, please visit [Host OS Requir
:::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png"::: :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::
--> -->
1. Select Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Also, enter a name for the resource and click Review + Create. 1. Select the Microsoft Connected Cache for Enterprise resource. When prompted, choose the subscription, resource group, and location for the resource. Then enter a name for the resource and select Review + Create.
<!-- <!--
:::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png"::: :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::
--> -->
1. After a few moments, you'll see a "Validation successful" message, indicating you can move onto the next step and select Create. 1. After a few moments, you'll see a "Validation successful" message, indicating you can move onto the next step and select Create.
1. The creation of the resource may take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes. 1. The creation of the resource might take a few minutes. After a successful creation, you'll see a Deployment complete page as below. Select Go to resource to create cache nodes.
# [Azure CLI](#tab/cli) # [Azure CLI](#tab/cli)
@ -61,7 +59,7 @@ For more information on sizing and OS requirements, please visit [Host OS Requir
* Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one. * Resource group under which an MCC resource can be created. Use the [az group create](/cli/azure/group#az-group-create) command to create a new Resource group if you don't already have one.
#### Create MCC resource #### Create MCCE Azure resource
Replace the following placeholders with your own information: Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription. * *\<resource-group>*: An existing resource group in your subscription.
* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource. * *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
@ -73,26 +71,26 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
--- ---
## Create cache node ## Create MCCE cache node
# [Azure portal](#tab/portal) # [Azure portal](#tab/portal)
1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created. 1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created.
1. Under Cache Node Management, click on Cache Nodes and then on + Create Cache Node. 1. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node.
<!-- <!--
:::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png"::: :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::
--> -->
1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and click create. Please note, cache node names have to be unique under the Microsoft Connected Cache resource. 1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on and select create. Note, cache node names have to be unique under the Microsoft Connected Cache resource.
<!-- <!--
:::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png"::: :::image type="content" source="images/mcc-isp-provision-cache-node-numbered.png" alt-text="Screenshot of the Azure portal depicting the cache node configuration page of a cache node. This screenshot shows all of the fields you can choose to configure the cache node." lightbox="./images/mcc-isp-provision-cache-node-numbered.png":::
--> -->
The creation of cache node may take a few minutes. Please click Refresh to see your recently created cache node. The creation of cache node might take a few minutes. Select Refresh to see your recently created cache node.
Once the status changes to **Not Configured**, you can now configure your cache node. Once the status changes to **Not Configured**, you can now configure your cache node.
# [Azure CLI](#tab/cli) # [Azure CLI](#tab/cli)
Use the command below to create a new cache node if you don't already have one. Use the following command to create a new cache node if you don't already have one.
Replace the following placeholders with your own information: Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription. * *\<resource-group>*: An existing resource group in your subscription.
@ -123,22 +121,22 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
--- ---
## Configure cache node ## Configure MCCE cache node
# [Azure portal](#tab/portal) # [Azure portal](#tab/portal)
Please enter required values to configure your cache node. To learn more about the definitions of each field, review the Configuration fields at the bottom of this article. Enter required values to configure your cache node. To learn more about the definitions of each field, review the Configuration fields at the bottom of this article.
Don't forget to click save after adding configuration information. Don't forget to select save after adding configuration information.
# [Azure CLI](#tab/cli) # [Azure CLI](#tab/cli)
Use the command below to configure cache node for **Linux** host OS Use the following command to configure cache node for deployment to a **Linux** host machine.
Replace the following placeholders with your own information: Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription. * *\<resource-group>*: An existing resource group in your subscription.
* *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource. * *\<mcc-resource-name>*: A name for your Microsoft Connected Cache for Enterprise resource.
* *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located. * *\<cache-node-name>*: The Azure region where your Microsoft Connected Cache will be located.
* *\<physical-path>*: The cache drive path. You can add upto 9 cache drives. * *\<physical-path>*: The cache drive path. You can add upto nine cache drives.
* *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb. * *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
* *\<proxy>*: If proxy needs to be enabled or not.<br> * *\<proxy>*: If proxy needs to be enabled or not.<br>
Accepted values: enabled, disabled Accepted values: enabled, disabled
@ -162,7 +160,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
<br> <br>
<br> <br>
Use the command below to configure cache node for **Windows** host OS Use the following command to configure cache node for deployment to a **Windows** host machine.
Replace the following placeholders with your own information: Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription. * *\<resource-group>*: An existing resource group in your subscription.
@ -190,21 +188,16 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
--cache-drive "[{physical-path:/var/mcc,size-in-gb:<size of cache drive>}]" --proxy <enabled> --proxy-host <"proxy host name"> --proxy-port <proxy port> --auto-update-day <day of week> --auto-update-time <time of day> --auto-update-week <week of month> --auto-update-ring <update ring> --cache-drive "[{physical-path:/var/mcc,size-in-gb:<size of cache drive>}]" --proxy <enabled> --proxy-host <"proxy host name"> --proxy-port <proxy port> --auto-update-day <day of week> --auto-update-time <time of day> --auto-update-week <week of month> --auto-update-ring <update ring>
``` ```
--- ---
## Next step ## Next step
The next step is to deploy the cache node to the host machine.
# [Azure portal](#tab/portal) ### [Azure portal](#tab/portal)
To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md) To deploy the cache node to a **Windows** host machine, see [Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
<br>
To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md) To deploy the cache node to a **Linux** host machine, see [Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
# [Azure CLI](#tab/cli/) ### [Azure CLI](#tab/cli/)
To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md) To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-ent-manage-cache-using-CLI.md)
--- ---
@ -214,33 +207,30 @@ To deploy cache nodes using Azure CLI, see [Bulk management of cache nodes](mcc-
### General configuration fields ### General configuration fields
| Field Name |Expected Value |Description| | Field Name |Expected Value |Description|
|---|---|---| |---|---|---|
|**Cache node name** | Alphanumeric string that contains no spaces| The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later| |**Cache node name** | Alphanumeric string that contains no spaces| The name of the cache node. You may choose names based on location such as "Seattle-1". This name must be unique and can't be changed later |
|**Host OS** | Linux or Windows| This is the host operating system that the cache node will be deployed on.| |**Host OS** | Linux or Windows| This is the operating system of the host machine that the cache node will be deployed to.|
### Storage fields ### Storage fields
##### Cache node for Linux ##### Cache node for Linux
>[!Important] >[!Important]
>All cache drives must have full read/write permissions set or the cache node will not function. For example, in a terminal you can run: sudo chmod 777 /path/to/cachedrivefolder >All cache drives must have full read/write permissions set or the cache node will not function. For example, in a terminal you can run: sudo chmod 777 /path/to/cachedrivefolder
<br> <br>
| Field Name |Expected Value |Description| | Field Name |Expected Value |Description|
|---|---|---| |---|---|---|
|**Cache drive folder**| File path string |Up to 9 drive folders accessible by the cache node can be configured for each cache node to configure cache storage. Enter the location of the folder in Ubuntu where the external physical drive is mounted. For example: /dev/sda3/. Each cache drive should have read/write permissions configured. Ensure your disks are mounted and visit Attach a data disk to a Linux VM for more information.| |**Cache drive folder**| File path string |Up to nine drive folders accessible by the cache node can be configured for each cache node to configure cache storage. Enter the location of the folder in Ubuntu where the external physical drive is mounted. For example: /dev/sda3/. Each cache drive should have read/write permissions configured. Ensure your disks are mounted and visit Attach a data disk to a Linux VM for more information.|
|**Cache drive size in gigabytes**| Integer in GB| Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB.| |**Cache drive size in gigabytes**| Integer in GB| Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB.|
##### Cache node for Windows ##### Cache node for Windows
| Field Name |Expected Value |Description| | Field Name |Expected Value |Description|
|---|---|---| |---|---|---|
|**Cache drive folder**| File path string /var/mcc| This is the folder path where content will be cached. You cannot change the folder path.| |**Cache drive folder**| File path string /var/mcc| This is the folder path where content is cached. You can't change the folder path.|
|**Cache drive size in gigabytes**| Integer in GB| Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB. | |**Cache drive size in gigabytes**| Integer in GB| Set the size of each drive configured for the cache node. Minimum cache drive size is 50 GB. |
#### Proxy settings #### Proxy settings
<br> <br>
@ -255,4 +245,3 @@ You can choose to enable or disable proxy settings on your cache node.
|---|---|---| |---|---|---|
|**Proxy host name**| String or number| Proxy host name or address| |**Proxy host name**| String or number| Proxy host name or address|
|**Proxy port**| Integer| Proxy port |**Proxy port**| Integer| Proxy port

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

@ -1,6 +1,6 @@
--- ---
title: Deploy cache software to a Linux host machine title: Deploy MCCE cache software to a Linux host machine
description: How to deploy Microsoft Connected Cache for Enterprise and Education cache software to a Linux host machine. description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) cache software to a Linux host machine.
author: chrisjlin author: chrisjlin
ms.author: lichris ms.author: lichris
manager: naengler manager: naengler
@ -30,9 +30,9 @@ Before deploying MCCE to a Linux host machine, ensure that the host machine meet
## Next step ## Next step
> [!div class="nextstepaction"] > [!div class="nextstepaction"]
> [Verify cache node functionality](mcc-enterprise-verify-functionality.md) > [Verify cache node functionality](mcc-ent-verify-cache-node.md)
## Related content ## Related content
- [Deploy to a Windows host machine](mcc-enterprise-deploy-windows.md) - [Deploy to a Windows host machine](mcc-ent-deploy-to-windows.md)
- [Uninstall MCCE](mcc-enterprise-uninstall.md) - [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)

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

@ -1,6 +1,6 @@
--- ---
title: Deploy cache software to a Windows host machine title: Deploy MCCE cache software to a Windows host machine
description: How to deploy Microsoft Connected Cache for Enterprise and Education cache software to a Windows host machine. description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCCE) cache software to a Windows host machine.
author: chrisjlin author: chrisjlin
ms.author: lichris ms.author: lichris
manager: naengler manager: naengler
@ -34,11 +34,11 @@ Before deploying MCCE to a Windows host machine, ensure that the host machine me
## Next step ## Next step
> [!div class="nextstepaction"] > [!div class="nextstepaction"]
> [Verify cache node functionality](mcc-enterprise-verify-functionality.md) > [Verify cache node functionality](mcc-ent-verify-cache-node.md)
<!-- OR --> <!-- OR -->
## Related content ## Related content
- [Deploy to a Linux host machine](mcc-enterprise-deploy-linux.md) - [Deploy to a Linux host machine](mcc-ent-deploy-to-linux.md)
- [Uninstall MCCE](mcc-enterprise-uninstall.md) - [Uninstall MCCE](mcc-ent-uninstall-cache-node.md)

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

@ -1,6 +1,6 @@
--- ---
title: MCC for Enterprise and Education Overview title: MCCE Overview
description: Overview, supported scenarios, and content types for Microsoft Connected Cache (MCC) for Enterprise and Education. description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCCE).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual

4
windows/deployment/do/mcc-ent-faq.yml
View File

@ -1,7 +1,7 @@
### YamlMime:FAQ ### YamlMime:FAQ
metadata: metadata:
title: Microsoft Connected Cache for Enterprise Frequently Asked Questions title: MCCE Frequently Asked Questions
description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise. description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCCE).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: faq ms.topic: faq

4
windows/deployment/do/mcc-ent-manage-cache-using-CLI.md
View File

@ -1,6 +1,6 @@
--- ---
title: MCC for Enterprise manage cache nodes using CLI title: Manage MCCE cache nodes using CLI
description: Microsoft Connected Cache for Enterprise. Learn about managing cache nodes using CLI description: Details on how to manage Microsoft Connected Cache for Enterprise (MCCE) cache nodes via Azure CLI commands.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to

149
windows/deployment/do/mcc-ent-monitor-cache.md
View File

@ -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.
-->

61
windows/deployment/do/mcc-ent-monitoring.md Normal file
View File

@ -0,0 +1,61 @@
---
title: Monitor usage of MCCE cache nodes
description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCCE) cache nodes.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
manager: naengler
ms.author: lichris
author: chrisjlin
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: 09/04/2024
---
# Monitor MCCE 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.
<!-- Add standard metrics
Add scenarios for creating custom metrics -->
## Cache node summary
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 is functioning as expected. |
| Unhealthy nodes | If the cache node does not respond, it will be labeled as unhealthy. |
| Max in | The maximum egress (in Mb/sec.) that your node has pulled in at any given time. This statistic is not 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. |
| Average in | The average ingress (in Mb/sec.) that your node has pulled in over its lifetime. This statistic is not dependent on the time filter near the charts. |
| Average out | The average egress (in Mb/sec.) that your node has pushed out over its lifetime. |
| Cache efficiency | The percentage of all requests that your MCC node receives that are ultimately delivered by your MCC node. An effective node is generally expected to have an efficiency >95%. |
## Charts
### Filters
- Will only filter the data shown in the 2 charts, scalable from 1 hour to 30 days
- Can view data by individual cache nodes or the average of all your active MCC nodes.
### Outbound traffic
- The egress (in Mb/sec) that your MCC node is pushing out at specific time intervals
### 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
## Additional metrics
### Custom metrics
- Navigate to the "Metrics" tab in the left-hand toolbar
- Configure chart as desired using the provided metrics
<!-- ### Windows Update for Business (WUfB) reports -->

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

@ -1,6 +1,6 @@
--- ---
title: Requirements for MCC for Enterprise and Education title: MCCE prerequisites
description: Overview of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE). description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCCE).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual
@ -67,7 +67,7 @@ This article details the requirements and recommendations for using Microsoft Co
### Host machine sizing recommendations ### Host machine sizing recommendations
| Component | Branch Office / Small Enterprise | Large Enterprise | | Component | Branch Office / Small Enterprise | Large Enterprise |
| -- | --- | --- | | --- | --- | --- |
| OS| Windows Server 2022 <br> Windows 11 (Pro or Enterprise) | Same | | OS| Windows Server 2022 <br> Windows 11 (Pro or Enterprise) | Same |
|NIC | 1 Gbps | 5 Gbps | |NIC | 1 Gbps | 5 Gbps |
|Disk | SSD <br>1 drive <br>50 GB each |SSD <br>1 drive <br>200 GB each | |Disk | SSD <br>1 drive <br>50 GB each |SSD <br>1 drive <br>200 GB each |

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

@ -1,6 +1,6 @@
--- ---
title: MCC for Enterprise early preview title: MCCE early preview
description: Microsoft Connected Cache for Enterprise early preview. description: Details on Microsoft Connected Cache for Enterprise (MCCE) early preview.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to

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

@ -1,6 +1,6 @@
--- ---
title: MCC for Enterprise and Education Release Notes title: MCCE Release Notes
description: Release Notes for Microsoft Connected Cache (MCC) for Enterprise and Education. description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCCE).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: conceptual ms.topic: conceptual

12
windows/deployment/do/mcc-ent-support-and-troubleshooting.md
View File

@ -1,19 +1,17 @@
--- ---
title: MCC for Enterprise support and troubleshooting title: MCCE support and troubleshooting
description: Microsoft Connected Cache for Enterprise. Learn about support and troubleshooting description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCCE).
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
manager: aaroncz manager: naengler
ms.author: nidos ms.author: nidos
author: doshnid author: doshnid
ms.reviewer: mstewart
ms.collection: tier3
appliesto: 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 11</a>
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</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> - ✅ <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 ms.date: 09/27/2024
--- ---
<!-- <!--

2
windows/deployment/do/mcc-ent-uninstall-cache-node.md
View File

@ -1,5 +1,5 @@
--- ---
title: Uninstall MCC for Enterprise and Education title: Uninstall MCCE cache nodes
description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) from a host machine. description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCCE) from a host machine.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates

72
windows/deployment/do/mcc-ent-update-cache-node.md
View File

@ -1,55 +1,55 @@
--- ---
title: Uninstall MCC for Enterprise and Education title: Update MCCE cache nodes
description: Details on how to uninstall Microsoft Connected Cache (MCC) for Enterprise and Education for your environment. description: Details on how Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes are updated by Microsoft.
ms.service: windows-client ms.service: windows-client
ms.subservice: itpro-updates ms.subservice: itpro-updates
ms.topic: how-to ms.topic: how-to
ms.author: carmenf ms.author: andyriv
author: cmknox author: chrisjlin
manager: aaroncz manager: naengler
ms.reviewer: mstewart
ms.collection:
- tier3
- must-keep
appliesto: 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 11</a>
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</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> - ✅ <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 ms.date: 09/27/2024
--- ---
# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education (MCCE)
<!-- Customers will no longer update the private preview and instead install public preview Microsoft Connected Cache for Enterprise and Education (MCCE) caching software requires periodic updates to maintain security, performance, and reliability. Microsoft silently deploys MCCE updates to your cache nodes based on the Update Ring setting you configure for each cache node.
# 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 rings
## Update MCC MCCE cache nodes can be configured to either the "Fast" or "Slow" update ring. If configured to update as part of the Fast ring, the cache node will be silently updated by Microsoft soon after the update is made available. If configured to update as part of the Slow ring, the cache node will be silently updated by Microsoft within 5 weeks of the update becoming available.
Run the following command with the **arguments** we provided in the email to update your MCC: In other words, configuring cache nodes to update as part of the Slow ring provides users with the option to delay the update process until they have validated that the latest MCCE update works within their environment. For example, a user could configure a test cache node to update as part of the Fast ring and validate that clients can successfully interact with the test cache node after the latest MCCE update has been applied. This builds confidence that service will not be interrupted when the production cache nodes are updated as part of the Slow ring.
```powershell ### Update ring options
# .\updatemcc.ps1 version="**\<VERSION\>**" tenantid="**\<TENANTID\>**" customerid="**\<CUSTOMERID\>**" cachenodeid="**\<CACHENODEID\>**" customerkey="**\<CUSTOMERKEY\>**"
```
For example: #### Fast Ring
All MCCE cache nodes are configured to update as part of the Fast ring by default. MCCE cache nodes in the Fast ring will be updated soon after an update is made available. Microsoft will silently update cache nodes at a time of day when update traffic is likely to be minimal, such as 3:00 AM (local time) on Saturday.
```powershell #### Slow Ring
# .\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" Configuring a MCCE cache node to update as part of the Slow ring provides users with the option to delay MCCE software updates until the update can be validated. There are three settings that will control when MCCE updates will be applied to MCCE cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
```
-->
# Uninstall MCC
Contact the MCC Team before uninstalling to let us know if you're facing issues. | Setting | Description |
| --- | --- |
| Week of the month | 1st to 4th week can be selected. There are three to four months in a year that could have a 5th week. In the event that there is a 5th week, the update could be applied during that 5th week if the day of the week falls near the last day of the month.|
| Day of the week | Monday through Sunday can be selected. |
| Time of day | Time of day is based on UTC and a 24 hour clock. |
This script removes the following items: ## Update process
1. EFLOW + Linux VM When Microsoft publishes an MCCE update, the MCCE service attempts to update all MCCE cache nodes based on their Update Ring membership. If a cache node cannot complete the silent MCCE update within 6 hours of starting, an error message is surfaced in the Azure portal.
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 ## Update terminology, criteria, and SLA
Edge LTS \> Uninstall
Microsoft Connected Cache is a container and the container OS and any software component within the container will need to be updated for security vulnerabilities or quality issues, or performance improvements required to successfully operate the caching software.
Microsoft Connected cache updates will not be shipped on a set cadence but will rather release updates periodically based on the need.
| Update type | Criteria and SLA |
| --- | --- |
| Security | Security updates are the highest priority and will be released based on the severity rating of the vulnerability. [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 60 days of discovery. [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities will be released by Microsoft within 120 days |
| Quality | Quality updates fix a specific problem and addresses a noncritical, non-security-related bug. Quality updates could include performance fixes for a specific problem or changes related to cache efficiency or maximum egress for example. Quality updates will be released along with security updates or when necessary to ensure proper functioning of the Microsoft Connected Cache software. |
For information on all released Microsoft Connected Cache updates see the [MCCE release notes](mcc-ent-release-notes.md).

8
windows/deployment/do/mcc-ent-verify-cache-node.md
View File

@ -1,6 +1,6 @@
--- ---
title: Verify cache node functionality title: Verify MCCE cache node functionality
description: How to verify functionality of a Microsoft Connected Cache for Enterprise and Education cache node. description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
author: chrisjlin author: chrisjlin
ms.author: lichris ms.author: lichris
manager: naengler manager: naengler
@ -42,5 +42,5 @@ These steps should be taken after deploying MCCE caching software to a [Windows]
## Related content ## Related content
- [Monitor cache node usage](mcc-enterprise-monitoring.md) - [Monitor cache node usage](mcc-ent-monitoring.md)
- [Troubleshoot cache node](mcc-enterprise-support-troubleshoot.md) - [Troubleshoot cache node](mcc-ent-support-and-troubleshooting.md)