mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
mcc-ent-last-edits
This commit is contained in:
Meghan Stewart
parent
fe19956e54
commit
6e7d3af6c8
@ -35,7 +35,7 @@
|
||||
href: waas-microsoft-connected-cache.md
|
||||
- name: Microsoft Connected Cache for Enterprise and Education
|
||||
items:
|
||||
- name: Connected Cache for Enterprise and Education Overview
|
||||
- name: Connected Cache for Enterprise and Education overview
|
||||
href: mcc-ent-edu-overview.md
|
||||
- name: Requirements
|
||||
href: mcc-ent-prerequisites.md
|
||||
|
||||
@ -30,16 +30,16 @@ For more information on sizing and OS requirements, see [the prerequisites for u
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
1. In the [Azure portal](https://portal.azure.com), select **Create a Resource** and search for "Microsoft Connected Cache for Enterprise and Education".
|
||||
1. In the [Azure portal](https://portal.azure.com), select **Create a Resource** and search for `Microsoft Connected Cache for Enterprise and Education`.
|
||||
<!--
|
||||
:::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 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.
|
||||
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, then select Review + 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 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.
|
||||
1. The creation of the resource might take a few minutes. After a successful creation, you'll see a page stating the deployment is complete. Select **Go to resource** to create cache nodes.
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
@ -78,15 +78,15 @@ az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
1. Open Azure portal and navigate to the Microsoft Connected Cache for Enterprise resource that you created.<br>
|
||||
1. Under Cache Node Management, select on Cache Nodes and then on + Create Cache Node.<br>
|
||||
1. Under Cache Node Management, select **Cache Nodes** then **Create Cache Node**.<br>
|
||||
|
||||
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.
|
||||
1. Provide a name for your cache node and select the host OS you plan to deploy the cache node on, then 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":::
|
||||
-->
|
||||
The creation of cache node might take a few minutes. Select Refresh to see your recently created cache node.
|
||||
The creation of the cache node might take a few minutes. Select **Refresh** to see your recently created cache node.
|
||||
Once the cache node state changes to **Not Configured**, you can now configure your cache node.<br>
|
||||
To know more about different cache node state, see [Cache node states](#cache-node-states).
|
||||
For more information about different cache node states, see [Cache node states](#cache-node-states).
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
@ -98,7 +98,7 @@ Replace the following placeholders with your own information:
|
||||
* *\<mcc-resource-name>*: Name of the Microsoft Connected Cache for Enterprise resource.
|
||||
* *\<cache-node-name>*: A name for your Microsoft Connected Cache node.
|
||||
* *\<host-os>*: The OS on which cache node will be provisioned.
|
||||
Accepted values: windows, linux
|
||||
Accepted values: `windows`, `linux`
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg> --host-os <linux>
|
||||
@ -107,12 +107,12 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
|
||||
<br>
|
||||
|
||||
>[!NOTE]
|
||||
>To ensure cache node has been created successfully, please run the following command before continuing with cache node configuration.
|
||||
>To ensure cache node has been created successfully, run the following command before continuing with cache node configuration.
|
||||
>```azurecli-interactive
|
||||
>az mcc ent node show --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg>
|
||||
>```
|
||||
>In the output look for cacheNodeState. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration.
|
||||
>If ***cacheNodeState = Registration in Progress***, then the cache node is still in process of being created. Please wait for a minute or two more and run the command again.
|
||||
>In the output look for **cacheNodeState**. If ***cacheNodeState = Not Configured***, you can continue with cache node configuration.
|
||||
>If ***cacheNodeState = Registration in Progress***, then the cache node is still in process of being created. Wait a couple of minutes and run the command again.
|
||||
>To know more about different cache node state, see [Cache node states](#cache-node-states).
|
||||
|
||||
---
|
||||
@ -120,7 +120,7 @@ az mcc ent node create --cache-node-name <mycachenode> --mcc-resource-name <mymc
|
||||
## Configure Connected 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.
|
||||
Enter required values to configure your cache node. For more information about the definitions of each field, review the [Configuration fields](#general-configuration-fields) at the bottom of this article.
|
||||
Don't forget to select save after adding configuration information.
|
||||
|
||||
|
||||
@ -134,15 +134,15 @@ Replace the following placeholders with your own information:
|
||||
* *\<resource-group>*: Name of the resource group in your subscription.
|
||||
* *\<mcc-resource-name>*: Name of your Microsoft Connected Cache for Enterprise resource.
|
||||
* *\<cache-node-name>*: Name for your Microsoft Connected Cache node.
|
||||
* *\<physical-path>*: The cache drive path. You can add upto nine cache drives.
|
||||
* *\<physical-path>*: The cache drive path. You can add up to 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>
|
||||
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 Connected Cache 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>
|
||||
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.
|
||||
* *\<auto-update-day>*: The day of the week cache node should be updated. Week starts from Monday.<br>
|
||||
Accepted values: 1,2,3,4,5,6,7
|
||||
@ -170,12 +170,12 @@ 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>
|
||||
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 Connected Cache 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>
|
||||
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.
|
||||
* *\<auto-update-day>*: The day of the week cache node should be updated. Week starts from Monday.<br>
|
||||
Accepted values: 1,2,3,4,5,6,7
|
||||
|
||||
@ -49,6 +49,8 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
|
||||
sudo ./provisionmcc.sh customerid="enter mccResourceId here" cachenodeid="enter cacheNodeId here" customerkey=" enter customerKey here " registrationkey="enter registrationKey here" drivepathandsizeingb="enter physicalPath value,enter sizeInGb value here" shoulduseproxy="enter true if present, enter false if not" proxyurl=http://enter proxy hostname:enter port
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Steps to point Windows client devices at Connected Cache node
|
||||
|
||||
Once you have successfully deployed Connected Cache to your Linux host machine, you'll need to configure your Windows client devices to request Microsoft content from the Connected Cache node.
|
||||
|
||||
@ -63,6 +63,8 @@ To deploy a cache node programmatically, you'll need to use Azure CLI to get the
|
||||
./provisionmcconwsl.ps1 -installationFolder c:\mccwsl01 -customerid [enter mccResourceId here] -cachenodeid [enter cacheNodeId here] -customerkey [enter customerKey here] -registrationkey [enter registration key] -cacheDrives "/var/mcc,enter drive size" -shouldUseProxy [enter true if present, enter false if not] -proxyurl "http://[enter proxy host name]:[enter port]" -mccRunTimeAccount $User -mccLocalAccountCredential $myLocalAccountCredential
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Steps to point Windows client devices at Connected Cache node
|
||||
|
||||
Once you have successfully deployed Connected Cache to your Windows host machine, you'll need to configure your Windows client devices to request Microsoft content from the Connected Cache node.
|
||||
|
||||
@ -21,11 +21,11 @@ ms.date: 10/30/2024
|
||||
> [!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/).
|
||||
|
||||
Microsoft Connected Cache for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache 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.
|
||||
Microsoft Connected Cache for Enterprise and Education (preview) is a software-only caching solution that delivers Microsoft content within enterprise and education networks. Connected Cache can be managed from the Azure portal or through Azure CLI. It 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 Microsoft Intune.
|
||||
|
||||
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).
|
||||
For information about Microsoft Connected Cache in Configuration Manager<!-- version 2111-->, see [Microsoft Connected Cache in Configuration Manager](/configmgr/core/plan-design/hierarchy/microsoft-connected-cache).
|
||||
|
||||
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.
|
||||
Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsystem for Linux (WSL](/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.
|
||||
|
||||
## Supported scenarios and configurations
|
||||
|
||||
@ -41,10 +41,10 @@ Microsoft Connected Cache is built for flexible deployments to support several d
|
||||
|
||||
Customers may have globally dispersed offices that meet some or all of the following parameters:
|
||||
|
||||
- Have 10 – 50 Windows devices on-site
|
||||
- Have 10 to 50 Windows devices on-site
|
||||
- Don't have dedicated server hardware
|
||||
- Have Internet bandwidth that is limited (satellite internet)
|
||||
- Have intermittent Internet connectivity
|
||||
- Have internet bandwidth that is limited (satellite internet)
|
||||
- Have intermittent internet connectivity
|
||||
|
||||
To support the branch office scenario, customers can deploy a Connected Cache node to a Windows 11 client device.
|
||||
|
||||
@ -55,7 +55,7 @@ Customers may have office spaces, data centers, or Azure deployments that meet s
|
||||
- Have 100s or 1,000s of Windows devices (desktop or server)
|
||||
- Have some existing server hardware (Decommissioned Distribution Point, file server, cloud print server)
|
||||
- Have Azure VMs and/or Azure Virtual Desktop deployed
|
||||
- Have Internet bandwidth that is mediocre (T1 or T3 lines)
|
||||
- Have limited internet bandwidth (T1 or T3 lines)
|
||||
|
||||
To support the large enterprise scenario, customers can deploy a Connected Cache node to a server running Windows Server 2022 or Ubuntu 22.04.
|
||||
|
||||
@ -63,9 +63,9 @@ See [Connected Cache node host machine requirements](mcc-ent-prerequisites.md) f
|
||||
|
||||
| Enterprise configuration | Download speed range | Download speeds and approximate content volume delivered in 8 Hours |
|
||||
|---|---|---|
|
||||
|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|
|
||||
|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|
|
||||
|Medium to Large Enterprises/Autopilot Provisioning Center (500 - 5,000 devices in a single location) |5 - 101 Gbps Peak| 9 Gbps => 32,400 GB </br></br> 5 Gbps => 18,000 GB </br></br>3 Gbps => 10,800 GB|
|
||||
|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|
|
||||
|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|
|
||||
|Medium to large enterprises/Autopilot provisioning center (500 - 5,000 devices in a single location) |5 - 101 Gbps Peak| 9 Gbps => 32,400 GB </br></br> 5 Gbps => 18,000 GB </br></br>3 Gbps => 10,800 GB|
|
||||
|
||||
## Supported content types
|
||||
|
||||
@ -89,8 +89,8 @@ The following diagram displays an overview of how Connected Cache functions:
|
||||
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 fall back 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
|
||||
1. Devices can fall back to CDN if the cache server is unavailable for any reason or use Delivery Optimization delay fallback to http (CDN) settings to prefer the local cache server.
|
||||
You can view data about Microsoft Connected Cache downloads on management portal and Windows Update for Business reports.
|
||||
|
||||
## Next steps
|
||||
|
||||
|
||||
@ -31,7 +31,7 @@ This article outlines how to create, configure, and deploy Microsoft Connected C
|
||||
az extension add --name mcc
|
||||
```
|
||||
|
||||
To learn more about installing extensions, visit [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
|
||||
To learn more about installing extensions, see [Install the Connected Cache extension.](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions)
|
||||
|
||||
<br>
|
||||
<br>
|
||||
@ -138,11 +138,11 @@ az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-res
|
||||
>[!IMPORTANT]
|
||||
>* Save the resulting values for cacheNodeId, customerKey, mccResourceId, registrationKey. These GUIDs are needed to create the provisioning script.
|
||||
>* In the output look for cacheNodeState. If **cacheNodeState = Not Provisioned**, you can continue with cache node provisioning.
|
||||
>* If **cacheNodeState = Not Configured**, then the cache node has not been configured. Please configure the cache node before provisioning.
|
||||
>* If **cacheNodeState = Not Configured**, then the cache node has not been configured. Configure the cache node before provisioning.
|
||||
|
||||
### Example script:
|
||||
|
||||
Below is a pseudocode example of how to script bulk creation and configuration of a Connected Cache Azure resource and multiple Connected Cache cache nodes.
|
||||
Below is a pseudocode example of how to script bulk creation and configuration of a Connected Cache Azure resource and multiple Connected Cache cache nodes:
|
||||
|
||||
<!--# [Bash](#tab/bash)
|
||||
|
||||
@ -197,6 +197,7 @@ for ($cacheNodeNumber = 1; $cacheNodeNumber -le $cacheNodesToCreate; $cacheNodeN
|
||||
az mcc ent node update --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --resource-group $resourceGroup --cache-drive "[{physical-path:/var/mcc,size-in-gb:50}]" --proxy enabled --proxy-host $proxyHost --proxy-port $proxyPort
|
||||
}
|
||||
```
|
||||
---
|
||||
|
||||
## Next step
|
||||
|
||||
|
||||
@ -25,7 +25,7 @@ This article details the requirements and recommended specifications for using M
|
||||
|
||||
The Azure resources used for Connected Cache will be free to you during this public preview.
|
||||
|
||||
- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from a Connected Cache node.
|
||||
- **E3/E5 or A3/A5 license**: Your organization must have one of the following license subscriptions for each device that downloads content from a Connected Cache node:
|
||||
|
||||
- [Windows Enterprise E3 or E5](/windows/whats-new/windows-licensing#windows-11-enterprise), included in [Microsoft 365 F3, E3, or E5](https://www.microsoft.com/microsoft-365/enterprise/microsoft365-plans-and-pricing?msockid=32c407b43d5968050f2b13443c746916)
|
||||
- Windows Education A3 or A5, included in [Microsoft 365 A3 or A5](https://www.microsoft.com/education/products/microsoft-365?msockid=32c407b43d5968050f2b13443c746916#Education-plans)
|
||||
@ -36,21 +36,21 @@ This article details the requirements and recommended specifications for using M
|
||||
|
||||
- Any previous installations of Connected Cache must be [uninstalled](mcc-ent-uninstall-cache-node.md) from the host machine before installing the latest version of Connected Cache.
|
||||
- [These listed endpoints](delivery-optimization-endpoints.md) must be reachable by the host machine.
|
||||
- The host machine must have no other services / applications utilizing port 80 (for example, ConfigManager or Distribution Point).
|
||||
- The host machine must have no other services / applications utilizing port 80 (for example, Configuration Manager or a distribution point).
|
||||
- The host machine must have at least 4 GB of free memory.
|
||||
|
||||
### Additional requirements for Windows host machines
|
||||
|
||||
- The Windows host machine must be using Windows 11 or Windows Server 2022 with the Latest Cumulative Update (LCU) applied.
|
||||
- The Windows host machine must be using Windows 11 or Windows Server 2022 with the latest cumulative update applied.
|
||||
- Windows 11 must have [OS Build 22631.3296](https://support.microsoft.com/topic/march-12-2024-kb5035853-os-builds-22621-3296-and-22631-3296-a69ac07f-e893-4d16-bbe1-554b7d9dd39b) or later
|
||||
- Windows Server 2022 must have [OS Build 20348.2227](https://support.microsoft.com/topic/january-9-2024-kb5034129-os-build-20348-2227-6958a36f-efaf-4ef5-a576-c5931072a89a) or later
|
||||
|
||||
- The Windows host machine must support nested virtualization.
|
||||
- The Windows host machine must have [WSL2 installed](/windows/wsl/install#install-wsl-command). You can install this on Windows 11 and Windows Server 2022 by running the PowerShell command `wsl.exe --install --no-distribution`.
|
||||
- The Windows host machine must have [WSL 2 installed](/windows/wsl/install#install-wsl-command). You can install this on Windows 11 and Windows Server 2022 by running the PowerShell command `wsl.exe --install --no-distribution`.
|
||||
|
||||
### Additional requirements for Linux host machines
|
||||
|
||||
- The Linux host machine must be using one of the following Operating Systems:
|
||||
- The Linux host machine must be using one of the following operating systems:
|
||||
|
||||
- Ubuntu 20.04
|
||||
- Red Hat Enterprise Linux (RHEL) 8.* or 9.*
|
||||
@ -64,9 +64,9 @@ This article details the requirements and recommended specifications for using M
|
||||
|
||||
### Recommended host machine hardware specifications
|
||||
|
||||
Based on your [enterprise configuration](mcc-ent-edu-overview.md), it's recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications.
|
||||
Based on your [enterprise configuration](mcc-ent-edu-overview.md), it's recommended to deploy your Connected Cache nodes to host machines that meet the following recommended hardware specifications:
|
||||
|
||||
| Component | Branch Office | Small / Medium Enterprise | Large Enterprise |
|
||||
| Component | Branch office | Small / medium enterprise | Large enterprise |
|
||||
| --- | --- | --- | --- |
|
||||
| CPU cores | 4 | 8 | 16 |
|
||||
| Memory | 8 GB, 4 GB free | 16 GB, 4 GB free | 32 GB, 4 GB free |
|
||||
|
||||
@ -17,26 +17,26 @@ ms.date: 10/30/2024
|
||||
|
||||
Microsoft Connected Cache for Enterprise and Education caching software is deployed to host machines as a container. The container OS and any software component within the container need to be updated to address security vulnerabilities and improve quality and performance. These Microsoft-published container updates are referred to as "Connected Cache updates" in this article.
|
||||
|
||||
Microsoft silently deploys Connected Cache updates to your cache nodes based on the Update Ring setting you configure for each cache node.
|
||||
Microsoft silently deploys Connected Cache updates to your cache nodes based on the **Update Ring** setting you configure for each cache node.
|
||||
|
||||
## Update rings
|
||||
|
||||
Connected 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 is silently updated by Microsoft within five weeks of the update becoming available.
|
||||
Connected 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 is silently updated by Microsoft within five weeks of the update becoming available.
|
||||
|
||||
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 Connected Cache 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 Connected Cache update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the Slow ring.
|
||||
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 Connected Cache 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 Connected Cache update has been applied. This builds confidence that service won't be interrupted when the production cache nodes are updated as part of the `Slow` ring.
|
||||
|
||||
### Update ring options
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In the event of a critical security patch, Microsoft may elect to initiate an Connected Cache update to your cache node as soon as possible (even if the cache node has been set to the Slow Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each Connected Cache update.
|
||||
> In the event of a critical security patch, Microsoft may elect to initiate a Connected Cache update to your cache node as soon as possible (even if the cache node has been set to the `Slow` Ring). Visit the [Release notes](mcc-ent-release-notes.md) page for a detailed changelog of each Connected Cache update.
|
||||
|
||||
#### Fast Ring
|
||||
|
||||
All Connected Cache nodes are configured to update as part of the Fast ring by default. Connected 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.
|
||||
All Connected Cache nodes are configured to update as part of the `Fast` ring by default. Connected Cache nodes in the `Fast` ring will be updated soon after an update is made available. The update 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.
|
||||
|
||||
#### Slow Ring
|
||||
|
||||
Configuring a Connected Cache node to update as part of the Slow ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
|
||||
Configuring a Connected Cache node to update as part of the `Slow` ring provides users with the option to delay Connected Cache software updates until the update can be validated. There are three settings that control when Connected Cache updates will be applied to Connected Cache nodes. All update ring settings can be managed from the Azure portal or through the Azure CLI.
|
||||
|
||||
| Setting | Description |
|
||||
| --- | --- |
|
||||
@ -46,15 +46,15 @@ Configuring a Connected Cache node to update as part of the Slow ring provides u
|
||||
|
||||
## Update process
|
||||
|
||||
When Microsoft publishes a Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their Update Ring membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal.
|
||||
When Microsoft publishes a Connected Cache update, the Connected Cache service attempts to update all Connected Cache nodes based on their **Update Ring** membership. If a cache node can't complete the silent Connected Cache update within 6 hours of starting, an error message is surfaced in the Azure portal.
|
||||
|
||||
## Update terminology, criteria, and SLA
|
||||
## Update terminology, criteria, and information
|
||||
|
||||
Connected Cache updates are released based on need instead of on a set cadence.
|
||||
|
||||
| Update type | Criteria and SLA |
|
||||
| Update type | Criteria and information |
|
||||
| --- | --- |
|
||||
| Security | Security updates are the highest priority and are released based on the severity rating of the vulnerability. Patches for [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are released by Microsoft within 60 days of discovery. Patches for [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are released by Microsoft within 120 days. |
|
||||
| Security | Security updates are the highest priority and are released based on the severity rating of the vulnerability. Updates for [Critical and High](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are released by Microsoft within 60 days of discovery. Updates for [Medium and Low](https://nvd.nist.gov/vuln-metrics/cvss) vulnerabilities are 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 are 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 [Connected Cache release notes](mcc-ent-release-notes.md).
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user