Merge branch 'release-mcc-ent' into nidos-mcc

This commit is contained in:
Vinay Pamnani
2024-10-07 17:34:36 -06:00
committed by GitHub
20 changed files with 218 additions and 119 deletions

View File

@ -1,6 +1,6 @@
---
title: Create and configure MCCE cache nodes
description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCCE) cache nodes.
title: Create and configure MCC cache nodes
description: Details on how to create and configure Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes.
ms.service: windows-client
ms.subservice: itpro-updates
ms.topic: how-to
@ -19,9 +19,12 @@ ms.date: 06/03/2024
This article outlines how to create and configure your Microsoft Connected Cache for Enterprise and Education (MCC) 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
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.
For more information on sizing and OS requirements, see [the prerequisites for using MCC for Enterprise and Education](mcc-ent-prerequisites.md).
For more information on sizing and OS requirements, see [the prerequisites for using MCC](mcc-ent-prerequisites.md).
## Create MCC Azure resource
@ -72,7 +75,7 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
---
## Create cache node
## Create MCC cache node
# [Azure portal](#tab/portal)
@ -118,7 +121,7 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
---
## Configure cache node
## Configure MCC cache node
# [Azure portal](#tab/portal)
Enter required values to configure your cache node. To learn more about the definitions of each field, review the [Configuration](#general-configuration-fields) fields at the bottom of this article.
@ -132,16 +135,17 @@ Don't forget to select save after adding configuration information.
Use the following command to configure cache node for deployment to a **Linux** host machine.
Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription.
* *\<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.
* *\<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.
* *\<proxy>*: If proxy needs to be enabled or not.<br>
Accepted values: enabled, disabled.<br>
If proxy is set to enabled, you must provide proxy host and proxy port information
* *\<proxy-host>*: The proxy host name or ip address
* *\<proxy-port>*: Proxy port
Accepted values: enabled, disabled<br>
Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
* *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
* *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
* *\<auto-update-ring>*: Update ring the cache node should have.<br>
Accepted values: slow, fast.<br>
If update ring is set to slow, you must provide the day of week, time of day and week of month the cache node should be updated.
@ -164,6 +168,7 @@ az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymc
Use the following command to configure cache node for deployment to a **Windows** host machine.
Replace the following placeholders with your own information:
* *\<resource-group>*: An existing resource group in your subscription.
* *\<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.
@ -171,10 +176,10 @@ Replace the following placeholders with your own information:
Accepted value: /var/mcc
* *\<size-in-gb>*: The size of cache drive. Must be at least 50 Gb.
* *\<proxy>*: If proxy needs to be enabled or not.<br>
Accepted values: enabled, disabled.<br>
If proxy is set to enabled, you must provide proxy host and proxy port information
* *\<proxy-host>*: The proxy host name or ip address
* *\<proxy-port>*: Proxy port
Accepted values: enabled, disabled<br>
Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
* *\<proxy-host>*: The proxy host name or ip address. Required if proxy is set to enabled.
* *\<proxy-port>*: Proxy port number. Required if proxy is set to enabled.
* *\<auto-update-ring>*: Update ring the cache node should have.<br>
Accepted values: slow, fast.<br>
If update ring is set to slow, you must provide the day of week, time of day and week of month the cache node should be updated.
@ -235,12 +240,12 @@ To deploy cache nodes using Azure CLI, see [Manage cache nodes using CLI](mcc-en
#### Proxy settings
<br>
You can choose to enable or disable proxy settings on your cache node.
You can choose to enable or disable proxy settings on your cache node. Proxy should be set to enabled if the cache node will need to pass through a network proxy to download content. The provided proxy will also be used during deployment of the MCC cache node to your host machine.
<br>
>[!IMPORTANT]
>Enabling or disabling the proxy settings after your cache node has been deployed will require running the provisioning script again. This will ensure that proxy changes are in effect on the cache node.
>Enabling or disabling the proxy settings after your cache node has been deployed will require running the provisioning script on the host machine again. This will ensure that proxy changes are in effect on the cache node.
| Field Name |Expected Value |Description|
|---|---|---|