mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Release mcc ent (#1)
* smb adds * smb adds * formatting * private preview and support content * edit removed and dep * Fix blocking issues * Acro-fix * 24H2 CSP Updates * Fix link * fix link in dep page * edit * edit index file * syntax-fix-24h2 * ltsc-edits * ltsc-edits * lichris-docs-1 * Acrolinx improvements * refresh for maxado-8631996 * update link for maxado-8631993 * additional edits, acrolinx * ltsc-tw * contentsource-8914508 * contentsource-8914508 * Updates for 1 October release * Set stale debug to false * update gp link for 24h2 * additional changes * Changes to updates, acrolinx changes * fixes broken links * Fixed alignment issues * updates from Rafal * fixed acrolinx * so many link fixes * added release notes and troubleshoot content * updates * Update security-compliance-toolkit-10.md Added Windows 11 24H2 * Update get-support-for-security-baselines.md Updated for Windows 11 24H2 * bump date * bump date * fix pde comment * fixing broken link * Fix broken redirections * fix to rel link * reset head, fix link * add cli to deploy, add script to cli * removing "mcce" * edits to create page * Update default and global release policies OS version and dates to latest release values * emoved e from mcce and other changes * updated example script * added important notice to update page * more update page changes * clarified how proxy configuration is used * anonymizing variables in example script * revise example script * acrolinx fixes to update page * changes to other pages and content in overview page * Update broken link Update broken link * Update windows-sandbox-configure-using-wsb-file.md Update `HostFolder` value description in `MappedFolder`, specifying that the path could be absolute or relative, not only absolute as, instead, is for the `SandboxFolder` value. * Remove bad link Removed bad link. There is already a second link referring to content so no need to replace the link. * docfx update for security book * Correct TOC entry changing Windows 10 to Windows * Update whats-new-do.md - Vpn to VPN - Minor improvements * Updated date for freshness reporting * Add EOS callout Fix some obvious Acrolinx issues * Fixed typo added clarity * Update mcc-ent-deploy-to-windows.md * Update .openpublishing.redirection.windows-deployment.json * Update .openpublishing.redirection.windows-deployment.json * Update policy-csp-localpoliciessecurityoptions.md * Correct indentation and spacing * Acrolinx: "Enteprise" * Update mcc-ent-edu-overview.md * refresh * Remove redirection and final bits of store-for-business store-for-business, AKA /microsoft-store/, is retired, and the content is archived in officearchive-pr. This archival was for ADO task 9268422. * added support content and other changes * fixed tabs * fixed tabs * Updated device reg policy and group information * Update delivery-optimization-endpoints.md Added a line item in MCC table for Outlook *res.cdn.office.net requirement * freshness review * Fix broken links * Minor change * content for faq * changes to landing page * more content to faqs * pencil edit * add copilot exps link * edits and ren cli file temporarily * ren file back and edit toc to lowercase * edit * edit * edit * Update windows-autopatch-configure-network.md Adding a new network endpoint required for the service 'device.autopatch.microsoft.com' @tiaraquan * Clarify some points and remove data that is confusing to customers. * fix syntax * Sentence correction * Update windows/deployment/do/waas-delivery-optimization-faq.yml Co-authored-by: Meghan Stewart <33289333+mestew@users.noreply.github.com> * Update windows/deployment/do/waas-delivery-optimization-faq.yml Co-authored-by: Meghan Stewart <33289333+mestew@users.noreply.github.com> * moved shortcuts under policy settings article --------- Co-authored-by: Alma Jenks <v-alje@microsoft.com> Co-authored-by: Meghan Stewart <33289333+mestew@users.noreply.github.com> Co-authored-by: Stacyrch140 <102548089+Stacyrch140@users.noreply.github.com> Co-authored-by: Nidhi Doshi <77081571+doshnid@users.noreply.github.com> Co-authored-by: Gary Moore <5432776+garycentric@users.noreply.github.com> Co-authored-by: Vinay Pamnani (from Dev Box) <vinpa@microsoft.com> Co-authored-by: Vinay Pamnani <37223378+vinaypamnani-msft@users.noreply.github.com> Co-authored-by: Aaron Czechowski <aczechowski@users.noreply.github.com> Co-authored-by: Aditi Srivastava <133841950+aditisrivastava07@users.noreply.github.com> Co-authored-by: Daniel H. Brown <32883970+DHB-MSFT@users.noreply.github.com> Co-authored-by: David Strome <21028455+dstrome@users.noreply.github.com> Co-authored-by: Padma Jayaraman <v-padmaj@microsoft.com> Co-authored-by: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Co-authored-by: Rebecca Agiewich <16087112+rjagiewich@users.noreply.github.com> Co-authored-by: Rick Munck <33725928+jmunck@users.noreply.github.com> Co-authored-by: Tanaka <Huios@users.noreply.github.com> Co-authored-by: Tiara Quan <95256667+tiaraquan@users.noreply.github.com> Co-authored-by: Frank Rojas <45807133+frankroj@users.noreply.github.com> Co-authored-by: Davide Piccinini <davide.piccinini.95@gmail.com> Co-authored-by: Phil Garcia <phil@thinkedge.com> Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com> Co-authored-by: tiaraquan <tiaraquan@microsoft.com> Co-authored-by: Caitlin Hart <caithart@microsoft.com> Co-authored-by: Harman Thind <63820404+hathin@users.noreply.github.com> Co-authored-by: [cmknox] <[cmknox@gmail.com]> Co-authored-by: Carmen Forsmann <cmforsmann@live.com>
This commit is contained in:
Chris J. Lin
GitHub
@ -317,7 +317,7 @@ items:
|
||||
href: configure-a-pxe-server-to-load-windows-pe.md
|
||||
- name: Windows Deployment Services (WDS) boot.wim support
|
||||
href: wds-boot-support.md
|
||||
- name: Windows ADK for Windows 10 scenarios for IT Pros
|
||||
- name: Windows ADK for Windows scenarios for IT Pros
|
||||
href: windows-adk-scenarios-for-it-pros.md
|
||||
- name: User State Migration Tool (USMT) technical reference
|
||||
items:
|
||||
|
||||
@ -38,13 +38,37 @@
|
||||
- name: MCC for Enterprise and Education Overview
|
||||
href: mcc-ent-edu-overview.md
|
||||
- name: Requirements
|
||||
href: mcc-enterprise-prerequisites.md
|
||||
- name: Deploy Microsoft Connected Cache
|
||||
href: mcc-enterprise-deploy.md
|
||||
- name: Update or uninstall MCC
|
||||
href: mcc-enterprise-update-uninstall.md
|
||||
- name: Appendix
|
||||
href: mcc-enterprise-appendix.md
|
||||
href: mcc-ent-prerequisites.md
|
||||
- name: How-to guides
|
||||
items:
|
||||
- name: Create MCC resource and cache node
|
||||
href: mcc-ent-create-resource-and-cache.md
|
||||
- name: Configure, provision and deploy cache node
|
||||
items:
|
||||
- name: Deploy MCC to Linux
|
||||
href: mcc-ent-deploy-to-linux.md
|
||||
- name: Deploy MCC to Windows
|
||||
href: mcc-ent-deploy-to-windows.md
|
||||
- name: Using CLI to create and manage cache nodes
|
||||
href: mcc-ent-manage-cache-using-cli.md
|
||||
- name: Verify cache node functionality
|
||||
href: mcc-ent-verify-cache-node.md
|
||||
- name: Monitor cache node
|
||||
href: mcc-ent-monitoring.md
|
||||
- name: Update MCC
|
||||
href: mcc-ent-update-cache-node.md
|
||||
- name: Uninstall cache node
|
||||
href: mcc-ent-uninstall-cache-node.md
|
||||
- name: Resources
|
||||
items:
|
||||
- name: Frequent Asked Questions
|
||||
href: mcc-ent-faq.yml
|
||||
- name: Support and troubleshooting
|
||||
href: mcc-ent-support-and-troubleshooting.md
|
||||
- name: MCC for Enterprise and Education (early preview)
|
||||
href: mcc-ent-private-preview.md
|
||||
- name: Release notes
|
||||
href: mcc-ent-release-notes.md
|
||||
- name: MCC for ISPs
|
||||
items:
|
||||
- name: MCC for ISPs Overview
|
||||
|
||||
@ -32,6 +32,7 @@ Use the table below to reference any particular content types or services endpoi
|
||||
| *.officecdn.microsoft.com.edgesuite.net, *.officecdn.microsoft.com, *.cdn.office.net | HTTP / 80 | Office CDN updates | [Complete list](/office365/enterprise/office-365-endpoints) of endpoints for Office CDN updates. | Both |
|
||||
| *.manage.microsoft.com, *.swda01.manage.microsoft.com, *.swda02.manage.microsoft.com, *.swdb01.manage.microsoft.com, *.swdb02.manage.microsoft.com, *.swdc01.manage.microsoft.com, *.swdc02.manage.microsoft.com, *.swdd01.manage.microsoft.com, *.swdd02.manage.microsoft.com, *.swda01-mscdn.manage.microsoft.com, *.swda02-mscdn.manage.microsoft.com, *.swdb01-mscdn.manage.microsoft.com, *.swdb02-mscdn.manage.microsoft.com, *.swdc01-mscdn.manage.microsoft.com, *.swdc02-mscdn.manage.microsoft.com, *.swdd01-mscdn.manage.microsoft.com, *.swdd02-mscdn.manage.microsoft.com | HTTP / 80 </br> HTTPs / 443 | Intune Win32 Apps | [Complete list](/mem/intune/fundamentals/intune-endpoints) of endpoints for Intune Win32 Apps updates. | Both |
|
||||
| *.statics.teams.cdn.office.net | HTTP / 80 </br> HTTPs / 443 | Teams | Future support is planned for peering and Connected Cache | TBD |
|
||||
| *.res.cdn.office.net | HTTP / 80 </br> HTTPs / 443 | Outlook | Future support is planned for peering and Connected Cache | TBD |
|
||||
| *.assets1.xboxlive.com, *.assets2.xboxlive.com, *.dlassets.xboxlive.com, *.dlassets2.xboxlive.com, *.d1.xboxlive.com, *.d2.xboxlive.com, *.assets.xbox.com, *.xbl-dlassets-origin.xboxlive.com, *.assets-origin.xboxlive.com, *.xvcb1.xboxlive.com, *.xvcb2.xboxlive.com, *.xvcf1.xboxlive.com, *.xvcf2.xboxlive.com | HTTP / 80 | Xbox | | Both |
|
||||
| *.tlu.dl.adu.microsoft.com, *.nlu.dl.adu.microsoft.com, *.dcsfe.prod.adu.microsoft.com | HTTP / 80 | Device Update | [Complete list](/azure/iot-hub-device-update/) of endpoints for Device Update updates. | Both |
|
||||
| *.do.dsp.mp.microsoft.com | HTTP / 80 </br> HTTPs / 443 | Microsoft Connected Cache -> Delivery Optimization Services communication | [Complete list](../do/waas-delivery-optimization-faq.yml) of endpoints for Delivery Optimization only. | Connected Cache Managed in Azure |
|
||||
|
||||
BIN
windows/deployment/do/images/mcc_ent_publicpreview.png
Normal file
BIN
windows/deployment/do/images/mcc_ent_publicpreview.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 257 KiB |
266
windows/deployment/do/mcc-ent-create-resource-and-cache.md
Normal file
266
windows/deployment/do/mcc-ent-create-resource-and-cache.md
Normal file
@ -0,0 +1,266 @@
|
||||
---
|
||||
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
|
||||
manager: naengler
|
||||
ms.author: nidos
|
||||
author: doshnid
|
||||
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: 06/03/2024
|
||||
---
|
||||
|
||||
# Create Microsoft Connected Cache Azure resource and cache nodes
|
||||
|
||||
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](mcc-ent-prerequisites.md).
|
||||
|
||||
|
||||
## Create MCC Azure resource
|
||||
|
||||
# [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".
|
||||
<!--
|
||||
:::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. 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.
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
### Prerequisites
|
||||
|
||||
* An Azure CLI environment:
|
||||
|
||||
* Use the Bash environment in [Azure Cloud Shell](/azure/cloud-shell/get-started/classic).
|
||||
|
||||
* Or, if you prefer to run CLI reference commands locally, [install the Azure CLI](/cli/azure/install-azure-cli)
|
||||
|
||||
* Sign in to the Azure CLI by using the [az login](/cli/azure/reference-index#az-login) command.
|
||||
|
||||
* Run [az version](/cli/azure/reference-index#az-version) to find the version and dependent libraries that are installed. To upgrade to the latest version, run [az upgrade](/cli/azure/reference-index#az-upgrade).
|
||||
|
||||
* Install Azure CLI extension **mcc** by following the instructions [here](/cli/azure/azure-cli-extensions-overview#how-to-install-extensions).
|
||||
|
||||
* 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 Azure resource
|
||||
|
||||
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.
|
||||
* *\<location>*: The Azure region where your Microsoft Connected Cache will be located.
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent resource create --mcc-resource-name <mymccresource> --resource-group <myrg> --location <region>
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Create MCC cache node
|
||||
|
||||
# [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. 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":::
|
||||
-->
|
||||
The creation of 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).
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
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:
|
||||
* *\<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.
|
||||
* *\<host-os>*: The OS on which cache node will be provisioned.
|
||||
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>
|
||||
```
|
||||
|
||||
<br>
|
||||
|
||||
>[!NOTE]
|
||||
>To ensure cache node has been created successfully, please 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.
|
||||
>To know more about different cache node state, see [Cache node states](#cache-node-states).
|
||||
|
||||
---
|
||||
|
||||
## 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.
|
||||
Don't forget to select save after adding configuration information.
|
||||
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
### Configure Linux MCC
|
||||
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>
|
||||
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.
|
||||
* *\<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
|
||||
* *\<auto-update-time>*: The time of day cache node should be updated in 24 hour format (hh:mm)
|
||||
* *\<auto-update-week>*: The week of month cache node should be updated.<br>
|
||||
Accepted values: 1,2,3,4
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg>
|
||||
--cache-drive "[{physical-path:</physical/path>,size-in-gb:<size of cache drive>},{</physical/path>,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>
|
||||
```
|
||||
|
||||
<br>
|
||||
<br>
|
||||
|
||||
### Configure Windows MCC
|
||||
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.
|
||||
* *\<physical-path>*: The cache drive path.<br>
|
||||
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>
|
||||
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.
|
||||
* *\<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
|
||||
* *\<auto-update-time>*: The time of day cache node should be updated in 24 hour format (hh:mm)
|
||||
* *\<auto-update-week>*: The week of month cache node should be updated.<br>
|
||||
Accepted values: 1,2,3,4
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg>
|
||||
--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
|
||||
|
||||
### [Azure portal](#tab/portal)
|
||||
To deploy the cache node to a **Windows** host machine, see
|
||||
>[!div class="nextstepaction"]
|
||||
>[Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
|
||||
|
||||
To deploy the cache node to a **Linux** host machine, see
|
||||
>[!div class="nextstepaction"]
|
||||
>[Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
|
||||
|
||||
### [Azure CLI](#tab/cli)
|
||||
To deploy cache nodes using Azure CLI, see
|
||||
>[!div class="nextstepaction"]
|
||||
>[Manage cache nodes using CLI](mcc-ent-manage-cache-using-CLI.md)
|
||||
|
||||
---
|
||||
<br>
|
||||
<br>
|
||||
|
||||
|
||||
### General configuration fields
|
||||
|
||||
| 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 such as "Seattle-1". This name must be unique and can't be changed later |
|
||||
|**Host OS** | Linux or Windows| This is the operating system of the host machine that the cache node will be deployed to.|
|
||||
|
||||
### Storage fields
|
||||
|
||||
##### Cache node for Linux
|
||||
|
||||
>[!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
|
||||
<br>
|
||||
|
||||
| Field Name |Expected Value |Description|
|
||||
|---|---|---|
|
||||
|**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 node for Windows
|
||||
|
||||
| Field Name |Expected Value |Description|
|
||||
|---|---|---|
|
||||
|**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. |
|
||||
|
||||
#### Proxy settings
|
||||
<br>
|
||||
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 on the host machine again. This will ensure that proxy changes are in effect on the cache node.
|
||||
|
||||
| Field Name |Expected Value |Description|
|
||||
|---|---|---|
|
||||
|**Proxy host name**| String or number| Proxy host name or address|
|
||||
|**Proxy port**| Integer| Proxy port
|
||||
|
||||
<br>
|
||||
|
||||
##### Cache node states
|
||||
| Cache node state |Description|
|
||||
|---|---|
|
||||
|Creation in progress| Cache node is being created|
|
||||
|Registration in progress| Cache node is being registered|
|
||||
|Not configured| Cache node is ready to be configured|
|
||||
|Not provisioned| Cache node is ready to be provisioned on host machine|
|
||||
|Healthy| Cache node phoning home|
|
||||
|Unhealthy| Cache node has stopped phoning home|
|
||||
|Never phoned home| Cache node has provisioned but has never phoned home|
|
||||
60
windows/deployment/do/mcc-ent-deploy-to-linux.md
Normal file
60
windows/deployment/do/mcc-ent-deploy-to-linux.md
Normal file
@ -0,0 +1,60 @@
|
||||
---
|
||||
title: Deploy MCC cache software to a Linux host machine
|
||||
description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) cache software to a Linux host machine.
|
||||
author: chrisjlin
|
||||
ms.author: lichris
|
||||
manager: naengler
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.date: 09/27/2024
|
||||
appliesto:
|
||||
- ✅ 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>
|
||||
---
|
||||
|
||||
# Deploy Microsoft Connected Cache caching software to a Linux host machine
|
||||
|
||||
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) caching software to a Linux host machine.
|
||||
|
||||
Before deploying MCC to a Linux host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource and cache node](mcc-ent-create-resource-and-cache.md).
|
||||
|
||||
## Steps to deploy MCC cache node to Linux
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
|
||||
1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.
|
||||
1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
|
||||
1. Run the provisioning command on the host machine.
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
To deploy a cache node programmatically, you'll need to use Azure CLI to get the cache node's provisioning details and then run the provisioning command on the host machine.
|
||||
|
||||
1. To get the cache node's provisioning details, use `az mcc ent node get-provisioning-details`
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
|
||||
```
|
||||
|
||||
1. Save the resulting output. These values will be passed as parameters within the provisioning command.
|
||||
1. Download and extract the [MCC provisioning package for Linux](https://aka.ms/MCC-Ent-InstallScript-Linux) to your host machine.
|
||||
1. Open a command line window *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Set access permissions to allow the `provisionmcc.sh` script within the provisioning package directory to execute.
|
||||
1. Replace the values in the following provisioning command before running it on the host machine.
|
||||
|
||||
```azurepowershell-interactive
|
||||
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
|
||||
```
|
||||
|
||||
## Next step
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Verify cache node functionality](mcc-ent-verify-cache-node.md)
|
||||
|
||||
## Related content
|
||||
|
||||
- [Deploy to a Windows host machine](mcc-ent-deploy-to-windows.md)
|
||||
- [Uninstall MCC](mcc-ent-uninstall-cache-node.md)
|
||||
70
windows/deployment/do/mcc-ent-deploy-to-windows.md
Normal file
70
windows/deployment/do/mcc-ent-deploy-to-windows.md
Normal file
@ -0,0 +1,70 @@
|
||||
---
|
||||
title: Deploy MCC cache software to a Windows host machine
|
||||
description: Details on how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) cache software to a Windows host machine.
|
||||
author: chrisjlin
|
||||
ms.author: lichris
|
||||
manager: naengler
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.date: 09/27/2024
|
||||
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/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
# Deploy Microsoft Connected Cache caching software to a Windows host machine
|
||||
|
||||
This article describes how to deploy Microsoft Connected Cache for Enterprise and Education (MCC) caching software to a Windows host machine.
|
||||
|
||||
Deploying MCC to a Windows host machine requires designating a [Group Managed Service Account (gMSA)](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts) or a [Local User Account](https://support.microsoft.com/windows/create-a-local-user-or-administrator-account-in-windows-20de74e0-ac7f-3502-a866-32915af2a34d) as the MCC runtime account. This prevents tampering with the MCC container and the cached content on the host machine.
|
||||
|
||||
Before deploying MCC to a Windows host machine, ensure that the host machine meets all [requirements](mcc-ent-prerequisites.md), and that you have [created and configured your MCC Azure resource](mcc-ent-create-resource-and-cache.md).
|
||||
|
||||
## Steps to deploy MCC cache node to Windows
|
||||
|
||||
# [Azure portal](#tab/portal)
|
||||
|
||||
1. Within the Azure portal, navigate to the "Provisioning" tab of your cache node and copy the provisioning command.
|
||||
1. Download the provisioning package using the button at the top of the Cache Node Configuration page and extract the package onto the host machine.
|
||||
1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run.
|
||||
1. Create a `$User` environment variable containing the username of the account you intend to designate as the MCC runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
|
||||
|
||||
If you're using a Local User account as the MCC runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
|
||||
|
||||
1. Run the provisioning command on the host machine.
|
||||
|
||||
# [Azure CLI](#tab/cli)
|
||||
|
||||
To deploy a cache node programmatically, you'll need to use Azure CLI to get the cache node's provisioning details and then run the provisioning command on the host machine.
|
||||
|
||||
1. To get the cache node's provisioning details, use `az mcc ent node get-provisioning-details`.
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
|
||||
```
|
||||
|
||||
1. Save the resulting output. These values will be passed as parameters within the provisioning command.
|
||||
1. Download and extract the [MCC provisioning package for Windows](https://aka.ms/MCC-Ent-InstallScript-WSL) to your host machine.
|
||||
1. Open a PowerShell window *as administrator* on the host machine, then change directory to the extracted provisioning package.
|
||||
1. Set the Execution Policy to "Unrestricted" to allow the provisioning scripts to run.
|
||||
1. Create a `$User` environment variable containing the username of the account you intend to designate as the MCC runtime account. For gMSAs, the value should be formatted as `"Domain\Username$"`. For Local User accounts, `$User` should be formatted as `"LocalMachineName\Username"`.
|
||||
|
||||
If you're using a Local User account as the MCC runtime account, you'll also need to create a [PSCredential Object](/dotnet/api/system.management.automation.pscredential) named `$myLocalAccountCredential`.
|
||||
|
||||
1. Replace the values in the following provisioning command before running it on the host machine. Note that `-mccLocalAccountCredential $myLocalAccountCredential` is only needed if you are using a Local User account as the MCC runtime account.
|
||||
|
||||
```powershell-interactive
|
||||
./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
|
||||
```
|
||||
|
||||
## Next step
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Verify cache node functionality](mcc-ent-verify-cache-node.md)
|
||||
|
||||
## Related content
|
||||
|
||||
- [Deploy to a Linux host machine](mcc-ent-deploy-to-linux.md)
|
||||
- [Uninstall MCC](mcc-ent-uninstall-cache-node.md)
|
||||
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: MCC for Enterprise and Education Overview
|
||||
description: Overview, supported scenarios, and content types for Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
title: MCC Overview
|
||||
description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
@ -13,61 +13,83 @@ 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
|
||||
ms.date: 05/09/2023
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education Overview
|
||||
|
||||
> [!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.
|
||||
The following diagram displays an overview of how MCC functions:<br>
|
||||
|
||||
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.
|
||||
:::image type="content" source="./images/mcc_ent_publicpreview.png" alt-text="Diagram displaying the components of MCC." lightbox="./images/mcc_ent_publicpreview.png":::
|
||||
|
||||
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":::
|
||||
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
|
||||
|
||||
## 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:
|
||||
## Next step
|
||||
|
||||
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).
|
||||
>[!div class="nextstepaction"]
|
||||
>[Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)
|
||||
72
windows/deployment/do/mcc-ent-faq.yml
Normal file
72
windows/deployment/do/mcc-ent-faq.yml
Normal file
@ -0,0 +1,72 @@
|
||||
### YamlMime:FAQ
|
||||
metadata:
|
||||
title: MCC Frequently Asked Questions
|
||||
description: The following article is a list of frequently asked questions for Microsoft Connected Cache for Enterprise (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: faq
|
||||
ms.author: nidos
|
||||
author: doshnid
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
ms.collection:
|
||||
- highpri
|
||||
- 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>
|
||||
ms.date: 06/03/2024
|
||||
title: Microsoft Connected Cache for Enterprise Frequently Asked Questions
|
||||
summary: |
|
||||
Frequently asked questions about Microsoft Connected Cache for Enterprise
|
||||
|
||||
sections:
|
||||
- name: Ignored
|
||||
questions:
|
||||
- question: Is this product a free service?
|
||||
answer: Yes. Microsoft Connected Cache is a free service.
|
||||
- question: Is there a nondisclosure agreement to sign?
|
||||
answer: No, a nondisclosure agreement isn't required.
|
||||
- question: What are the prerequisites and hardware requirements?
|
||||
answer: |
|
||||
- [Azure pay-as-you-go subscription](https://azure.microsoft.com/offers/ms-azr-0003p/).
|
||||
- [Hardware to host Microsoft Connected Cache](mcc-ent-edu-overview.md)
|
||||
- [Host machine requirements](mcc-ent-prerequisites.md)
|
||||
- question: What host OS do I need to deploy MCC?
|
||||
answer: You can use Linux or Windows OS. Depending on the OS, the provisioning script and certain provisioning steps are different.
|
||||
- question: What content is cached by Microsoft Connected Cache?
|
||||
answer: For more information about content cached, see [Delivery Optimization and Microsoft Connected Cache content endpoints](delivery-optimization-endpoints.md).
|
||||
- question: Do I need to provide hardware BareMetal server or a virtual machine (VM)?
|
||||
answer: Microsoft Connected Cache is a software-only caching solution and requires you to provide your own server to host the software.
|
||||
- question: Can we use hard drives instead of SSDs?
|
||||
answer: We highly recommend using SSDs as Microsoft Connected Cache is a read intensive application. We also recommend using multiple drives to improve performance.
|
||||
- question: Where should we install Microsoft Connected Cache?
|
||||
answer: You are in control of your hardware and you can pick the location based on your traffic and end clients. You can choose the location where you have your routers or where you have dense traffic or any other parameters.
|
||||
- question: How can I set up a gMSA account?
|
||||
answer: For more information about gMSA accounts, see [Learn how to provision a Group Managed Service Account on a Domain Controller](/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/getting-started-with-group-managed-service-accounts#create-group-managed-service-accounts). Make sure that your gMSA has been granted permissions to "Log on as batch job" within the host machine's [local security policies](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/how-to-configure-security-policy-settings).
|
||||
- question: How can I set up a local account?
|
||||
answer: For more information, see [Learn how to provision a Local User Account](https://support.microsoft.com/topic/104dc19f-6430-4b49-6a2b-e4dbd1dcdf32). Make sure that your gMSA has been granted permissions to "Log on as batch job" within the host machine's [local security policies](/previous-versions/windows/it-pro/windows-10/security/threat-protection/security-policy-settings/how-to-configure-security-policy-settings).
|
||||
- question: Where can I monitor cache node usage?
|
||||
answer: You can monitor your cache node usage on Azure portal. For more information, see [Monitor cache node usage Info on Reporting Capabilities](mcc-ent-monitoring.md).
|
||||
- question: Does Microsoft Connected Cache support Xbox or Microsoft Teams content?
|
||||
answer: Currently, Microsoft Connected Cache doesn't support Xbox or Microsoft Teams content. However, supporting Xbox content is of high priority, and we expect this feature soon. We'll let you know as soon as it becomes available!
|
||||
- question: How does Microsoft Connected Cache populate its content? Can I precache content?
|
||||
answer: Microsoft Connected Cache is a cold cache warmed by client requests at the byte range level so your clients only request the content they need. The client requests content and that is what fills the cache which means there's no cache fill necessary. "Preseeding" can be achieved but use of update rings. A test ring or early adopter ring can be used to fill the cache and all subsequent requests by other clients will come from cache.
|
||||
- question: How long would a piece of content live within the Microsoft Connected Cache? Is content purged from the cache?
|
||||
answer: Once a request for said content is made, NGINX looks at the cache control headers from the original acquisition. If that content is expired, NGINX continues to serve the stale content while it's downloading the new content. We cache the content for 30 days. The content is in the hot cache path (open handles and such) for 24 hrs, but will reside on disk for 30 days. The drive fills up and nginx starts to delete content based on its own algorithm, probably some combination of least recently used.
|
||||
- question: Is it possible to not update the Microsoft Connected Cache software or delay update longer than the timeline provided in the updates configuration?
|
||||
answer: No. It's important to keep the Microsoft Connected Cache software up to date, especially when it comes to security issues. Microsoft validates updates prior to releasing Enterprises Connected Cache updates and will only release updates when it's necessary to keep customers secure or to ensure the continued successful operation of Connected Cache nodes for customers.
|
||||
- question: How do I set up CLI?
|
||||
answer: For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
|
||||
- question: How do I install MCC extension?
|
||||
answer: For more information, see [Install the Microsoft Connected Cache extension](mcc-ent-install-extension.md).
|
||||
- question: What do I do if I have to set up or change existing proxy?
|
||||
answer: You can enable proxy and provide proxy information on Azure portal or use the CLI. Don't forget to rerun the provisioning script after making any proxy changes. For more information, see [Set up or change existing proxy](mcc-ent-proxy.md).
|
||||
- question: How do we set up Microsoft Connected Cache if we support multiple countries or regions?
|
||||
answer: Microsoft Connected Cache isn't a service that has dependency on a specific Azure region, and there isn't personal or organizational identifiable information stored in the resource that necessitates data residency. The three regions that the Connected Cache resource can be deployed to are (Europe) North Europe, (Asia Pacific) Korea Central, and (US) West US.
|
||||
- question: Should I use a gMSA, local user, or domain account to deploy Microsoft Connected Cache to Windows?
|
||||
answer: There are pros and cons to the account options available to customers. We anticipate that security and manageability are top priories for customers. Microsoft provides guidance on both Active Directory and Microsoft Entra-based service accounts ([Introduction to Active Directory service accounts - Choose the right type of service account](/entra/architecture/service-accounts-on-premises#types-of-on-premises-service-accounts)) and user-based service accounts ([Secure user-based service accounts in Active Directory)](/entra/architecture/service-accounts-user-on-premises#assess-on-premises-user-account-security)).
|
||||
- question: Does the user have to be logged using the account that installed Microsoft Connected Cache on Windows or Linux?
|
||||
answer: No. As part of the installation on Windows a scheduled task is created using the account used to install Connected Cache. Regardless of which user is logged in or not logged in, the schedule task remains running. On Linux Connected Cache is installed by the user and remains running regardless of which user is logged in to the OS.
|
||||
- question: What do I do if I need more support and have more questions even after reading this FAQ page?
|
||||
answer: For further support for Microsoft Connected Cache, see [Troubleshooting issues for Microsoft Connected Cache for Enterprise and Education](mcc-ent-support-and-troubleshooting.md). If you still need more support, you can contact customer support.
|
||||
209
windows/deployment/do/mcc-ent-manage-cache-using-cli.md
Normal file
209
windows/deployment/do/mcc-ent-manage-cache-using-cli.md
Normal file
@ -0,0 +1,209 @@
|
||||
---
|
||||
title: Manage MCC cache nodes using CLI
|
||||
description: Details on how to manage Microsoft Connected Cache for Enterprise (MCC) cache nodes via Azure CLI commands.
|
||||
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: 06/03/2024
|
||||
---
|
||||
|
||||
# Manage cache nodes using CLI
|
||||
|
||||
<br>
|
||||
|
||||
This article outlines how to create, configure, and deploy Microsoft Connected Cache for Enterprise (MCC) cache nodes using Azure CLI.
|
||||
|
||||
|
||||
## Prerequisites:
|
||||
1. **Install Azure CLI**: [How to install the Azure CLI](/cli/azure/install-azure-cli)
|
||||
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>
|
||||
|
||||
### 1. Create a Resource group
|
||||
|
||||
The first step is to create a resource group if you don't already have one.
|
||||
An Azure resource group is a logical container into which Azure resources are deployed and managed.
|
||||
|
||||
To create a resource group, use `az group create`. You can find more details on this CLI command [here](/cli/azure/group#az-group-create).
|
||||
<br>
|
||||
|
||||
```azurecli-interactive
|
||||
az group create --name myrg --location westus
|
||||
```
|
||||
|
||||
Once the resource group is created, you'll need to create a Microsoft Connected Cache for Enterprise resource.
|
||||
|
||||
### 2. Create an MCC Azure resource
|
||||
|
||||
An MCC Azure resource is a top-level Azure resource under which cache nodes can be created.
|
||||
|
||||
To create an MCC Azure resource, use `az mcc ent resource create`
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent resource create --mcc-resource-name mymccresource --resource-group myrg
|
||||
```
|
||||
|
||||
<br>
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating MCC resource.
|
||||
|
||||
<br>
|
||||
|
||||
The next step is to create a cache node under this resource.
|
||||
|
||||
|
||||
### 3. Create a cache node
|
||||
|
||||
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 or windows>
|
||||
```
|
||||
|
||||
<br>
|
||||
|
||||
>[!IMPORTANT]
|
||||
>In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully started creating cache node.
|
||||
|
||||
<br>
|
||||
|
||||
### 4. Confirm cache node creation
|
||||
|
||||
Before you can start configuring your cache node, you need to confirm that the cache node was successfully created.
|
||||
|
||||
To confirm cache node creation, use `az mcc ent node show`
|
||||
|
||||
<br>
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node show --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
|
||||
```
|
||||
|
||||
>[!IMPORTANT]
|
||||
>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.
|
||||
|
||||
<br>
|
||||
|
||||
Once successful cache node creation is confirmed, you can proceed to configure the cache node.
|
||||
|
||||
|
||||
### 5. Configure cache node
|
||||
|
||||
To configure your cache node, use `az mcc ent node update`
|
||||
|
||||
The below example configures a Linux cache node with proxy enabled:
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node update --cache-node-name <mycachenode> --mcc-resource-name <mymccresource> --resource-group <myrg>
|
||||
--cache-drive "[{physical-path:</physical/path>,size-in-gb:<size of cache drive>},{</physical/path>,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>
|
||||
```
|
||||
|
||||
>[!Note]
|
||||
>* For a cache node that is to be deployed on Windows host OS, the physical path of the cache drive <u>must</u> be **/var/mcc**.<br>
|
||||
>* In the output, look for operationStatus. **operationStatus = Succeeded** indicates that our services have successfully updated the cache node. You will also see that cacheNodeState will show "Not Provisioned". <br>
|
||||
>* Please save values for <u>physicalPath, sizeInGb, proxyPort, proxyHostName</u> as these values will be needed to construct the provisioning script.
|
||||
|
||||
|
||||
<br>
|
||||
|
||||
### 6. Get provisioning details for the cache node
|
||||
|
||||
After successfully configuring the cache node, the next step is to deploy the cache node to a host machine. To deploy the cache node, you'll need to create a provisioning script with relevant information.
|
||||
|
||||
To get the relevant information for provisioning script, use `az mcc ent node get-provisioning-details`
|
||||
|
||||
```azurecli-interactive
|
||||
az mcc ent node get-provisioning-details --cache-node-name mycachenode --mcc-resource-name mymccresource --resource-group myrg
|
||||
```
|
||||
|
||||
>[!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.
|
||||
|
||||
### Example script:
|
||||
|
||||
Below is a pseudocode example of how to script bulk creation and configuration of an MCC Azure resource and multiple MCC cache nodes.
|
||||
|
||||
<!--# [Bash](#tab/bash)
|
||||
|
||||
:::code language="azurecli" source="~/azure_cli_scripts/azure-cli/create-azure-resources-at-scale/bash/create-azure-resources-at-scale.sh" id="step4":::
|
||||
|
||||
In your console output, are you missing the last row in your CSV file? This can be caused by a missing line continuation character after the last line. Add a blank line at the end of your CSV file to fix the issue.
|
||||
|
||||
# [PowerShell](#tab/powershell)
|
||||
|
||||
:::code language="azurecli" source="~/azure_cli_scripts/azure-cli/create-azure-resources-at-scale/powershell/create-azure-resources-at-scale.ps1" id="step4":::
|
||||
|
||||
-->
|
||||
|
||||
# [PowerShell](#tab/powershell)
|
||||
|
||||
```powershell
|
||||
#Define variables
|
||||
$mccResourceName = "myMCCResource"
|
||||
$cacheNodeName = "demo-node"
|
||||
$cacheNodeOperatingSystem = "Windows"
|
||||
$resourceGroup = "myRG"
|
||||
$resourceLocation = "westus"
|
||||
$cacheNodesToCreate = 2
|
||||
$proxyHost = "myProxy.com"
|
||||
$proxyPort = "8080"
|
||||
$waitTime = 3
|
||||
|
||||
#Create MCC Az resource
|
||||
az mcc ent resource create --mcc-resource-name $mccResourceName --location $resourceLocation --resource-group $resourceGroup
|
||||
|
||||
#Loop through $cacheNodesToCreate iterations
|
||||
for ($cacheNodeNumber = 1; $cacheNodeNumber -le $cacheNodesToCreate; $cacheNodeNumber++) {
|
||||
$iteratedCacheNodeName = $cacheNodeName + "-" + $cacheNodeNumber
|
||||
|
||||
#Create cache node
|
||||
az mcc ent node create --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --host-os $cacheNodeOperatingSystem --resource-group $resourceGroup
|
||||
|
||||
#Get cache node state
|
||||
$cacheNodeState = $(az mcc ent node show --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --resource-group $resourceGroup --query "cacheNodeState") | ConvertFrom-Json
|
||||
|
||||
$howLong = 0
|
||||
#Wait until cache node state returns "Not Configured"
|
||||
while ($cacheNodeState -ne "Not Configured") {
|
||||
Write-Output "Waiting for cache node creation to complete...$howLong seconds"
|
||||
Start-Sleep -Seconds $waitTime
|
||||
$howLong += $waitTime
|
||||
|
||||
$cacheNodeState = $(az mcc ent node show --cache-node-name $iteratedCacheNodeName --mcc-resource-name $mccResourceName --resource-group $resourceGroup --query "cacheNodeState") | ConvertFrom-Json
|
||||
}
|
||||
|
||||
#Configure cache node
|
||||
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
|
||||
|
||||
To deploy the cache node to a **Windows** host machine, see
|
||||
>[!div class="nextstepaction"]
|
||||
>[Deploy cache node to Windows](mcc-ent-deploy-to-windows.md)
|
||||
|
||||
To deploy the cache node to a **Linux** host machine, see
|
||||
>[!div class="nextstepaction"]
|
||||
>[Deploy cache node to Linux](mcc-ent-deploy-to-linux.md)
|
||||
61
windows/deployment/do/mcc-ent-monitoring.md
Normal file
61
windows/deployment/do/mcc-ent-monitoring.md
Normal file
@ -0,0 +1,61 @@
|
||||
---
|
||||
title: Monitor usage of MCC cache nodes
|
||||
description: Details on how to monitor the usage of Microsoft Connected Cache for Enterprise (MCC) 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 Microsoft Connected Cache cache node usage
|
||||
|
||||
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
|
||||
|
||||
Add scenarios for creating custom metrics -->
|
||||
|
||||
## Cache node summary
|
||||
|
||||
The Cache Node Summary box on your Azure portal
|
||||
|
||||
| Metric | Description |
|
||||
| --- | --- |
|
||||
| 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. |
|
||||
| Average in | The average ingress (in Mb/sec.) that your node has pulled in over its lifetime. This statistic isn't 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 two 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 MCC 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 -->
|
||||
72
windows/deployment/do/mcc-ent-prerequisites.md
Normal file
72
windows/deployment/do/mcc-ent-prerequisites.md
Normal file
@ -0,0 +1,72 @@
|
||||
---
|
||||
title: MCC prerequisites
|
||||
description: Details of prerequisites and recommendations for using Microsoft Connected Cache for Enterprise and Education (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: lichris
|
||||
author: chrisjlin
|
||||
manager: naengler
|
||||
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/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education Requirements
|
||||
|
||||
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 (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/).
|
||||
|
||||
The Azure resources used for MCC 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 an MCC 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)
|
||||
|
||||
## Cache node host machine requirements
|
||||
|
||||
### General requirements
|
||||
|
||||
- Any previous installations of MCC must be [uninstalled](mcc-ent-uninstall-cache-node.md) before installing the latest version of MCC.
|
||||
- [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 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.
|
||||
- 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).
|
||||
|
||||
### Additional requirements for Linux host machines
|
||||
|
||||
- The Linux host machine must be using one of the following Operating Systems:
|
||||
|
||||
- Ubuntu 20.04
|
||||
- Red Hat Enterprise Linux (RHEL) 8.* or 9.*
|
||||
- If using RHEL, the default container engine (Podman) must be replaced with [Moby](https://github.com/moby/moby#readme)
|
||||
|
||||
### Networking recommendations for host machines
|
||||
|
||||
- Multiple network interface cards (NICs) on a single MCC instance aren't supported.
|
||||
- 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
|
||||
- The NIC and BIOS should support SR-IOV for best performance.
|
||||
|
||||
### Host machine sizing recommendations
|
||||
|
||||
| Component | Branch Office / Small Enterprise | Large Enterprise |
|
||||
| --- | --- | --- |
|
||||
| OS| Windows Server 2022 <br> Windows 11 (Pro or Enterprise) | Same |
|
||||
|NIC | 1 Gbps | 5 Gbps |
|
||||
|Disk | SSD <br>1 drive <br>50 GB each |SSD <br>1 drive <br>200 GB each |
|
||||
|Memory | 4 GB | 8 GB |
|
||||
|Cores | 4 | 8 |
|
||||
26
windows/deployment/do/mcc-ent-private-preview.md
Normal file
26
windows/deployment/do/mcc-ent-private-preview.md
Normal file
@ -0,0 +1,26 @@
|
||||
---
|
||||
title: MCC Private Preview
|
||||
description: Details on Microsoft Connected Cache for Enterprise (MCC) Private Preview
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
manager: naengler
|
||||
ms.author: lichris
|
||||
author: chrisjlin
|
||||
appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise</a>
|
||||
ms.date: 06/03/2024
|
||||
---
|
||||
|
||||
# Microsoft Connected Cache for Enterprise and Education (MCC) Private Preview
|
||||
|
||||
If you participated in the MCC early preview, thank you for your collaboration and feedback.
|
||||
|
||||
To continue using MCC, 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 MCC Azure service.
|
||||
|
||||
As such, we strongly recommend you [recreate your existing resources in Azure](mcc-ent-create-resource-and-cache.md) and then [redeploy the MCC caching software to your host machines](mcc-ent-deploy-to-windows.md) using the latest OS-specific installer.
|
||||
|
||||
## Next step
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [View documentation for MCC Public Preview](mcc-ent-edu-overview.md)
|
||||
40
windows/deployment/do/mcc-ent-release-notes.md
Normal file
40
windows/deployment/do/mcc-ent-release-notes.md
Normal file
@ -0,0 +1,40 @@
|
||||
---
|
||||
title: MCC Release Notes
|
||||
description: Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC).
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: lichris
|
||||
author: chrisjlin
|
||||
manager: naengler
|
||||
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 and Education</a>
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
|
||||
# Release Notes for Microsoft Connected Cache for Enterprise and Education (MCC)
|
||||
|
||||
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)
|
||||
|
||||
- Released on **10/17/2024**
|
||||
- Contains breaking changes
|
||||
- Contains service changes
|
||||
- Contains client changes
|
||||
- Affects Linux, Windows host machines
|
||||
|
||||
### Changenotes
|
||||
|
||||
- Added new "Outbound egress" and "Volume by Content type" monitoring charts to Azure portal user interface
|
||||
- Added ability to create custom monitoring charts under the Metrics tab in the Azure portal user interface
|
||||
- Added support for creating both Windows-hosted and Linux-hosted cache nodes under the same MCC Azure resource
|
||||
- Added Azure CLI support for programmatic creation and management of MCC Azure resources and cache nodes
|
||||
- Added support for unauthenticated proxy and cloud proxy integration
|
||||
- Added ability to set each cache node's Update Ring to govern cadence of MCC container updates
|
||||
|
||||
## Related content
|
||||
|
||||
- [Overview of MCC](mcc-ent-edu-overview.md)
|
||||
73
windows/deployment/do/mcc-ent-support-and-troubleshooting.md
Normal file
73
windows/deployment/do/mcc-ent-support-and-troubleshooting.md
Normal file
@ -0,0 +1,73 @@
|
||||
---
|
||||
title: MCC support and troubleshooting
|
||||
description: Details on how to troubleshoot and seek support for Microsoft Connected Cache for Enterprise (MCC).
|
||||
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/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)]
|
||||
|
||||
## 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 issue
|
||||
If you are facing issues with your cache node, it could be due to cache node being on the early preview version of MCC. Cache nodes belonging to early preview version will be under MCC resource that will have 'early preview' in its name. Please delete these cache nodes and associated MCC resource and create a new MCC resource on the new version.
|
||||
For detailed instructions on creating MCC resource, see [Create MCC Azure resources](mcc-ent-create-resource-and-cache.md)
|
||||
|
||||
|
||||
## Troubleshooting cache node deployment
|
||||
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
|
||||
|
||||
## Troubleshooting cache node monitoring
|
||||
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.
|
||||
|
||||
-->
|
||||
|
||||
## Diagnose and Solve
|
||||
|
||||
If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your MCC resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard.
|
||||
|
||||
You can find **Diagnose and solve problems** on the left pane within your MCC resource.
|
||||
|
||||
Within **Diagnose and solve problems**, select **Troubleshoot** under the type of problem you're facing and follow the prompts that narrow down the solution to the issue.
|
||||
|
||||
|
||||
## Filing a support request
|
||||
|
||||
TODO: Add steps for filling out a CSS ticket.
|
||||
35
windows/deployment/do/mcc-ent-uninstall-cache-node.md
Normal file
35
windows/deployment/do/mcc-ent-uninstall-cache-node.md
Normal file
@ -0,0 +1,35 @@
|
||||
---
|
||||
title: Uninstall MCC cache nodes
|
||||
description: Details on how to uninstall Microsoft Connected Cache for Enterprise and Education (MCC) from a host machine.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.author: lichris
|
||||
author: chrisjlin
|
||||
manager: naengler
|
||||
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 and Education</a>
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
|
||||
# Uninstall MCC caching software from a host machine
|
||||
|
||||
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 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 MCC from a Linux host machine
|
||||
|
||||
The `uninstallmcc.sh` script within the provisioning package uninstalls the MCC caching software and all related components, including:
|
||||
|
||||
- IoT Edge
|
||||
- IoT Edge Agent
|
||||
- IoT Edge Hub
|
||||
- MCC
|
||||
- Moby CLI
|
||||
- Moby engine
|
||||
58
windows/deployment/do/mcc-ent-update-cache-node.md
Normal file
58
windows/deployment/do/mcc-ent-update-cache-node.md
Normal file
@ -0,0 +1,58 @@
|
||||
---
|
||||
title: Update MCC cache nodes
|
||||
description: Details on how Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes are updated by Microsoft.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.author: andyriv
|
||||
author: chrisjlin
|
||||
manager: naengler
|
||||
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 and Education</a>
|
||||
ms.date: 09/27/2024
|
||||
---
|
||||
# Configure container update frequency for Microsoft Connected Cache for Enterprise and Education (MCC)
|
||||
|
||||
Microsoft Connected Cache for Enterprise and Education (MCC) 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 "MCC updates" in this article.
|
||||
|
||||
Microsoft silently deploys MCC updates to your cache nodes based on the Update Ring setting you configure for each cache node.
|
||||
|
||||
## Update rings
|
||||
|
||||
MCC 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 MCC 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 MCC 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 MCC 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 MCC update.
|
||||
|
||||
#### Fast Ring
|
||||
All MCC cache nodes are configured to update as part of the Fast ring by default. MCC 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.
|
||||
|
||||
#### Slow Ring
|
||||
Configuring an MCC cache node to update as part of the Slow ring provides users with the option to delay MCC software updates until the update can be validated. There are three settings that control when MCC updates will be applied to MCC cache nodes. All update ring settings can be managed from the Azure portal or through Azure CLI.
|
||||
|
||||
| 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. If there's 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. |
|
||||
|
||||
## Update process
|
||||
|
||||
When Microsoft publishes an MCC update, the MCC service attempts to update all MCC cache nodes based on their Update Ring membership. If a cache node can't complete the silent MCC update within 6 hours of starting, an error message is surfaced in the Azure portal.
|
||||
|
||||
## Update terminology, criteria, and SLA
|
||||
|
||||
MCC updates will be released based on need instead of on a set cadence.
|
||||
|
||||
| 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 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 [MCC release notes](mcc-ent-release-notes.md).
|
||||
46
windows/deployment/do/mcc-ent-verify-cache-node.md
Normal file
46
windows/deployment/do/mcc-ent-verify-cache-node.md
Normal file
@ -0,0 +1,46 @@
|
||||
---
|
||||
title: Verify MCC cache node functionality
|
||||
description: Details on how to verify functionality of Microsoft Connected Cache for Enterprise and Education (MCC) cache nodes.
|
||||
author: chrisjlin
|
||||
ms.author: lichris
|
||||
manager: naengler
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.date: 09/27/2024
|
||||
appliesto:
|
||||
- ✅ Windows-hosted MCC cache nodes
|
||||
- ✅ Linux-hosted MCC cache nodes
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for Enterprise and Education</a>
|
||||
---
|
||||
|
||||
# Verify MCC cache node functionality
|
||||
|
||||
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 MCC 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 MCC cache node
|
||||
|
||||
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
|
||||
```
|
||||
|
||||
If successful, there should be an HTTP response with StatusCode 200.
|
||||
|
||||
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 MCC cache node.
|
||||
|
||||
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".
|
||||
|
||||
## Related content
|
||||
|
||||
- [Monitor cache node usage](mcc-ent-monitoring.md)
|
||||
- [Troubleshoot cache node](mcc-ent-support-and-troubleshooting.md)
|
||||
@ -1,138 +0,0 @@
|
||||
---
|
||||
title: Appendix for MCC for Enterprise and Education
|
||||
description: This article contains reference information for Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: reference
|
||||
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
|
||||
---
|
||||
|
||||
# Appendix
|
||||
|
||||
## 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)]
|
||||
|
||||
### Troubleshooting
|
||||
|
||||
If you're not able to sign up for a Microsoft Azure subscription with the **Account belongs to a directory that cannot be associated with an Azure subscription. Please sign in with a different account.** error, see the following articles:
|
||||
|
||||
- [Can't sign up for a Microsoft Azure subscription](/troubleshoot/azure/general/cannot-sign-up-subscription).
|
||||
- [Troubleshoot issues when you sign up for a new account in the Azure portal](/azure/cost-management-billing/manage/troubleshoot-azure-sign-up).
|
||||
|
||||
## Hardware specifications
|
||||
|
||||
Most customers choose to install their cache node on a Windows Server with a nested Hyper-V VM. If this isn't supported in your network, some customers have also opted to install their cache node using VMware. At this time, a Linux-only solution isn't available and Azure VMs don't support the standalone Microsoft Connected Cache.
|
||||
|
||||
### Installing on VMware
|
||||
|
||||
Microsoft Connected Cache for Enterprise and Education can be successfully installed on VMware. To do so, there are a couple of additional configurations to be made. Ensure the VM is turned off before making the following configuration changes:
|
||||
|
||||
1. Ensure that you're using ESX. In the VM settings, turn on the option **Expose hardware assisted virtualization to the guest OS**.
|
||||
1. Using the Hyper-V Manager, create an external switch. For the external switch to have internet connection, ensure **"Allow promiscuous mode"** and **"Forged transmits"** are switched to **Yes**.
|
||||
|
||||
### Installing on Hyper-V
|
||||
|
||||
To learn more about how to configure Intel and AMD processors to support nested virtualization, see [Run Hyper-V in a Virtual Machine with Nested Virtualization](/virtualization/hyper-v-on-windows/user-guide/nested-virtualization).
|
||||
|
||||
## Diagnostics Script
|
||||
|
||||
If you're having issues with your MCC, we included a diagnostics script. The script collects all your logs and zips them into a single file. You can then send us these logs via email for the MCC team to debug.
|
||||
|
||||
To run this script:
|
||||
|
||||
1. Navigate to the following folder in the MCC installation files:
|
||||
|
||||
mccinstaller > Eflow > Diagnostics
|
||||
|
||||
1. Run the following commands:
|
||||
|
||||
```powershell
|
||||
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
|
||||
.\collectMccDiagnostics.ps1
|
||||
```
|
||||
|
||||
1. The script stores all the debug files into a folder and then creates a tar file. After the script is finished running, it will output the path of the tar file, which you can share with us. The location should be **\<currentpath\>**\mccdiagnostics\support_bundle_\$timestamp.tar.gz
|
||||
|
||||
1. [Email the MCC team](mailto:mccforenterprise@microsoft.com?subject=Debugging%20Help%20Needed%20for%20MCC%20for%20Enterprise) and attach this file asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during out debugging process.
|
||||
|
||||
## IoT Edge runtime
|
||||
|
||||
The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices.
|
||||
The runtime sits on the IoT Edge device, and performs management and
|
||||
communication operations. The runtime performs several functions:
|
||||
|
||||
- Installs and update workloads (Docker containers) on the device.
|
||||
- Maintains Azure IoT Edge security standards on the device.
|
||||
- Ensures that IoT Edge modules (Docker containers) are always running.
|
||||
- Reports module (Docker containers) health to the cloud for remote monitoring.
|
||||
- Manages communication between an IoT Edge device and the cloud.
|
||||
|
||||
For more information on Azure IoT Edge, see the [Azure IoT Edge documentation](/azure/iot-edge/about-iot-edge).
|
||||
|
||||
## Routing local Windows clients to an MCC
|
||||
|
||||
### Get the IP address of your MCC using ifconfig
|
||||
|
||||
There are multiple methods that can be used to apply a policy to PCs that should participate in downloading from the MCC.
|
||||
|
||||
#### Registry key
|
||||
|
||||
You can either set your MCC IP address or FQDN using:
|
||||
|
||||
1. Registry key (version 1709 and later):
|
||||
`HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization`
|
||||
</br>
|
||||
"DOCacheHost"=" "
|
||||
|
||||
From an elevated command prompt:
|
||||
|
||||
```powershell
|
||||
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f
|
||||
```
|
||||
|
||||
1. MDM path (version 1809 and later):
|
||||
|
||||
`.Vendor/MSFT/Policy/Config/DeliveryOptimization/DOCacheHost`
|
||||
|
||||
1. In Windows (release version 1809 and later), you can apply the policy via Group Policy Editor. The policy to apply is **DOCacheHost**. To configure the clients to pull content from the MCC using Group Policy, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Delivery Optimization**. Set the **Cache Server Hostname** to the IP address of your MCC, such as `10.137.187.38`.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-group-policy-hostname.png" alt-text="Screenshot of the Group Policy editor showing the Cache Server Hostname Group Policy setting." lightbox="./images/ent-mcc-group-policy-hostname.png":::
|
||||
|
||||
## Verify content using the DO client
|
||||
|
||||
To verify that the Delivery Optimization client can download content using MCC, you can use the following steps:
|
||||
|
||||
1. Download a game or application from the Microsoft Store.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-store-example-download.png" alt-text="Screenshot of the Microsoft Store with the game, Angry Birds 2, selected.":::
|
||||
|
||||
1. Verify downloads came from MCC by one of two methods:
|
||||
|
||||
- Using the PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see *BytesFromCacheServer*.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-get-deliveryoptimizationstatus.png" alt-text="Screenshot of the output of Get-DeliveryOptimization | FT from PowerShell." lightbox="./images/ent-mcc-get-deliveryoptimizationstatus.png":::
|
||||
|
||||
- Using the Delivery Optimization Activity Monitor
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-delivery-optimization-activity.png" alt-text="Screenshot of the Delivery Optimization Activity Monitor.":::
|
||||
|
||||
## EFLOW
|
||||
|
||||
- [What is Azure IoT Edge for Linux on Windows](/azure/iot-edge/iot-edge-for-linux-on-windows)
|
||||
- [Install Azure IoT Edge for Linux on Windows](/azure/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric#install-iot-edge)
|
||||
- [PowerShell functions for Azure IoT Edge for Linux on Windows](/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions)
|
||||
- EFLOW FAQ and Support: [Support · Azure/iotedge-eflow Wiki (github.com)](https://github.com/Azure/iotedge-eflow/wiki/Support#how-can-i-apply-updates-to-eflow)
|
||||
- [Now ready for Production: Linux IoT Edge Modules on Windows - YouTube](https://www.youtube.com/watch?v=pgqVCg6cxVU&ab_channel=MicrosoftIoTDevelopers)
|
||||
@ -1,418 +0,0 @@
|
||||
---
|
||||
title: Deploying your cache node
|
||||
description: How to deploy a Microsoft Connected Cache (MCC) for Enterprise and Education cache node from the Azure portal.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: how-to
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
ms.reviewer: mstewart
|
||||
manager: aaroncz
|
||||
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 and Education</a>
|
||||
ms.date: 05/23/2024
|
||||
---
|
||||
|
||||
# Deploy your cache node
|
||||
|
||||
This article describes how to deploy a Microsoft Connected Cache (MCC) for Enterprise and Education cache node.
|
||||
|
||||
## Steps to deploy MCC
|
||||
|
||||
To deploy MCC to your server:
|
||||
|
||||
1. [Provide Microsoft with the Azure subscription ID](#provide-microsoft-with-the-azure-subscription-id)
|
||||
1. [Create the MCC Resource in Azure](#create-the-mcc-resource-in-azure)
|
||||
1. [Create an MCC Node](#create-an-mcc-node-in-azure)
|
||||
1. [Edit Cache Node Information](#edit-cache-node-information)
|
||||
1. [Install MCC on a physical server or VM](#install-mcc-on-windows)
|
||||
1. [Verify MCC functionality](#verify-mcc-server-functionality)
|
||||
1. [Review common Issues](#common-issues) if needed.
|
||||
|
||||
### Provide Microsoft with the Azure subscription ID
|
||||
|
||||
As part of the MCC preview onboarding process an Azure subscription ID must be provided to Microsoft.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> 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).
|
||||
|
||||
For information about creating or locating your subscription ID, see [Steps to obtain an Azure subscription ID](mcc-enterprise-appendix.md#steps-to-obtain-an-azure-subscription-id).
|
||||
|
||||
### Create the MCC resource in Azure
|
||||
|
||||
The MCC Azure management portal is used to create and manage MCC nodes. An Azure subscription ID is used to grant access to the preview and to create the MCC resource in Azure and Cache nodes.
|
||||
|
||||
Once you take the survey above and the MCC team adds your subscription ID to the allowlist, you'll be given a link to the Azure portal where you can create the resource described below.
|
||||
|
||||
1. In the Azure portal home page, choose **Create a resource**:
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-create-azure-resource.png" alt-text="Screenshot of the Azure portal. The create a resource option is outlined in red.":::
|
||||
|
||||
1. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results.
|
||||
|
||||
> [!NOTE]
|
||||
> You won't see Microsoft Connected Cache in the drop-down list. You'll need to type the string and press enter to see the result.
|
||||
|
||||
1. Select **Microsoft Connected Cache Enterprise** and choose **Create** on the next screen to start the process of creating the MCC resource.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-azure-search-result.png" alt-text="Screenshot of the Azure portal search results for Microsoft Connected Cache.":::
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-azure-marketplace.png" alt-text="Screenshot of Microsoft Connected Cache Enterprise within the Azure Marketplace.":::
|
||||
|
||||
1. Fill in the required fields to create the MCC resource.
|
||||
|
||||
- Choose the subscription that you provided to Microsoft.
|
||||
- Azure resource groups are logical groups of resources. Create a new resource group and choose a name for your resource group.
|
||||
- Choose **(US) West US** for the location of the resource. This choice won't impact MCC if the physical location isn't in the West US, it's just a limitation of the preview.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Your MCC resource will not be created properly if you do not select **(US) West US**
|
||||
|
||||
- Choose a name for the MCC resource.
|
||||
- Your MCC resource must not contain the word **Microsoft** in it.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-azure-create-connected-cache.png" alt-text="Screenshot of the Create a Connected Cache page within the Azure Marketplace.":::
|
||||
|
||||
1. Once all the information has been entered, select the **Review + Create** button. Once validation is complete, select the **Create** button to start the resource creation.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-azure-cache-created.png" alt-text="Screenshot of the completed cache deployment within the Azure." lightbox="./images/ent-mcc-azure-cache-created.png":::
|
||||
|
||||
#### Error: Validation failed
|
||||
|
||||
- If you get a Validation failed error message on your portal, it's likely because you selected the **Location** as **US West 2** or some other location that isn't **(US) West US**.
|
||||
- To resolve this error, go to the previous step and choose **(US) West US**.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-create-cache-failed.png" alt-text="Screenshot of a failed cache deployment due to an incorrect location.":::
|
||||
|
||||
### Create an MCC node in Azure
|
||||
|
||||
Creating an MCC node is a multi-step process and the first step is to access the MCC early preview management portal.
|
||||
|
||||
1. After the successful resource creation, select **Go to resource**.
|
||||
1. Under **Cache Node Management** section on the leftmost panel, select **Cache Nodes**.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-cache-nodes.png" alt-text="Screenshot of the Cache Node Management section with the navigation link to the Cache Nodes page outlined in red.":::
|
||||
|
||||
1. On the **Cache Nodes** blade, select the **Create Cache Node** button.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-create-cache-node.png" alt-text="Screenshot of the Cache Nodes page with the Create Cache Node option outlined in red.":::
|
||||
|
||||
1. Selecting the **Create Cache Node** button will open the **Create Cache Node** page; **Cache Node Name** is the only field required for cache node creation.
|
||||
|
||||
| Field Name | Expected Value | Description |
|
||||
|---|---|---|
|
||||
| **Cache Node Name** | Alphanumeric name that doesn't include any 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. |
|
||||
|
||||
1. Enter the information for the **Cache Node** and select the **Create** button.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-create-cache-node-name.png" alt-text="Screenshot of the Cache Nodes page displaying the Cache Node Name text entry during the creation process.":::
|
||||
|
||||
If there are errors, the form will provide guidance on how to correct the errors.
|
||||
|
||||
Once the MCC node has been created, the installer instructions will be exposed. More details on the installer instructions will be addressed later in this article, in the [Install Connected Cache](#install-mcc-on-windows) section.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-connected-cache-installer-download.png" alt-text="Screenshot of the Connected Cache installer download button, installer instructions, and script.":::
|
||||
|
||||
#### Edit cache node information
|
||||
|
||||
Cache nodes can be deleted here by selecting the check box to the left of a **Cache Node Name** and then selecting the delete toolbar item. Be aware that if a cache node is deleted, there's no way to recover the cache node or any of the information related to the cache node.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-delete-cache-node.png" alt-text="Screenshot of deleting a cache node from the Cache Nodes page.":::
|
||||
|
||||
### Install MCC on Windows
|
||||
|
||||
Installing MCC on your Windows device is a simple process. A PowerShell script performs the following tasks:
|
||||
|
||||
- Installs the Azure CLI
|
||||
- Downloads, installs, and deploys EFLOW
|
||||
- Enables Microsoft Update so EFLOW can stay up to date
|
||||
- Creates a virtual machine
|
||||
- Enables the firewall and opens ports 80 and 22 for inbound and outbound traffic. Port 80 is used by MCC, and port 22 is used for SSH communications.
|
||||
- Configures Connected Cache tuning settings.
|
||||
- Creates the necessary *FREE* Azure resource - IoT Hub/IoT Edge.
|
||||
- Deploys the MCC container to server.
|
||||
|
||||
#### Run the installer
|
||||
|
||||
1. Download and unzip `mccinstaller.zip` from the create cache node page or cache node configuration page, both of which contain the necessary installation files.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-download-installer.png" alt-text="Screenshot of the download installer option on the Create Cache Node page.":::
|
||||
|
||||
The following files are contained in the `mccinstaller.zip` file:
|
||||
|
||||
- **installmcc.ps1**: Main installer file.
|
||||
- **installEflow.ps1**: Installs the necessary prerequisites such as the Linux VM, IoT Edge runtime, and Docker, and makes necessary host OS settings to optimize caching performance.
|
||||
- **resourceDeploymentForConnectedCache.ps1**: Creates Azure cloud resources required to support MCC control plane.
|
||||
- **mccdeployment.json**: Deployment manifest used by IoT Edge to deploy the MCC container and configure settings on the container, such as cache drive location sizes.
|
||||
- **updatemcc.ps1**: The update script used to upgrade MCC to a particular version.
|
||||
- **mccupdate.json**: Used as part of the update script
|
||||
|
||||
1. Open Windows PowerShell as administrator then navigate to the location of these files.
|
||||
|
||||
> [!NOTE]
|
||||
> Ensure that Hyper-V is enabled on your device.
|
||||
> - **Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
|
||||
> - **Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server)'
|
||||
>
|
||||
> Don't use PowerShell ISE, PowerShell 6.x, or PowerShell 7.x. Only Windows PowerShell version 5.x is supported.
|
||||
|
||||
1. **If you're installing MCC on a local virtual machine**, turn the virtual machine **off** while you enable nested virtualization and MAC spoofing.
|
||||
1. Enable nested virtualization:
|
||||
|
||||
```powershell
|
||||
Set-VMProcessor -VMName "VM name" -ExposeVirtualizationExtensions $true
|
||||
```
|
||||
|
||||
1. Enable MAC spoofing:
|
||||
|
||||
```powershell
|
||||
Get-VMNetworkAdapter -VMName "VM name" | Set-VMNetworkAdapter -MacAddressSpoofing On
|
||||
```
|
||||
|
||||
1. Set the execution policy.
|
||||
|
||||
```powershell
|
||||
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
|
||||
```
|
||||
|
||||
> [!NOTE]
|
||||
> After setting the execution policy, you'll see a warning asking if you wish to change the execution policy. Choose **[A] Yes to All**.
|
||||
|
||||
1. Copy the command from the Azure portal and run it in Windows PowerShell.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-installer-script.png" alt-text="Screenshot of the installer script for the connected cache node.":::
|
||||
|
||||
> [!NOTE]
|
||||
> After running the command, and multiple times throughout the installation process, you'll receive the following notice. Select **[R] Run once** to proceed.
|
||||
> </br>
|
||||
> </br> Security warning
|
||||
> </br> Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run C:\Users\mccinstaller\Eflow\installmcc.ps1?
|
||||
> </br>
|
||||
> </br> [D] Do not run **[R] Run once** [S] Suspend [?] Help (default is "D"):
|
||||
|
||||
1. Choose whether you would like to create a new external virtual switch or select an existing external virtual switch.
|
||||
|
||||
If creating a new external virtual switch, name your switch and be sure to choose a Local Area Connection (USB adapters work as well however, we do not recommend using Wi-Fi). A computer restart will be required if you're creating a new switch.
|
||||
|
||||
> [!NOTE]
|
||||
> Restarting your computer after creating a switch is recommended. You'll notice network delays during installation if the computer has not been restarted.
|
||||
|
||||
If you restarted your computer after creating a switch, start from step 2 above and skip to step 5.
|
||||
|
||||
If you opt to use an existing external switch, select the switch from the presented options. Local Area Connection (or USB) is preferable to Wi-Fi.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-script-new-switch.png" alt-text="Screenshot of the installer script running in PowerShell when a new switch is created." lightbox="./images/ent-mcc-script-new-switch.png":::
|
||||
|
||||
1. Rerun the script after the restart. This time, choose **No** when asked to create a new switch. Enter the number corresponding to the switch you previously created.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-script-existing-switch.png" alt-text="Screenshot of the installer script running in PowerShell when using an existing switch." lightbox="./images/ent-mcc-script-existing-switch.png":::
|
||||
|
||||
1. Decide whether you would like to use dynamic or static address for the Eflow VM. If you choose to use a static IP, do not use the IP address of the server. It is a VM, and it will have its own IP.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-script-dynamic-address.png" alt-text="Screenshot of the installer script running in PowerShell asking if you'd like to use a dynamic address." lightbox="./images/ent-mcc-script-dynamic-address.png":::
|
||||
|
||||
> [!NOTE]
|
||||
> Choosing a dynamic IP address might assign a different IP address when the MCC restarts. A static IP address is recommended so you don't have to change this value in your management solution when MCC restarts.
|
||||
|
||||
The IP address you assign to the EFLOW VM should be within the same subnet as the host server (based on the subnet mask) and not used by any other machine on the network.
|
||||
For example, for host configuration where the server IP Address is 192.168.1.202 and the subnet mask is 255.255.255.0, the static IP can be anything 192.168.1.* except 192.168.1.202.
|
||||
<!-- Insert Image 1 & 2. Remove ent-mcc-script-dynamic-address.png image (it is replaced by image 2) -->
|
||||
:::image type="content" source="./images/external-switch-1.jpg" alt-text="Screenshot of a sample output of ipconfig command showing example of subnet mask." lightbox="./images/external-switch-1.jpg":::
|
||||
|
||||
:::image type="content" source="./images/assigning-ip-2.png" alt-text="Screenshot of multiple installer questions about ipv4 address for Eflow." lightbox="./images/assigning-ip-2.png":::
|
||||
|
||||
If you would like to use your own DNS server instead of Google DNS 8.8.8.8, select **n** and set your own DNS server IP.
|
||||
|
||||
:::image type="content" source="./images/use-custom-dns-3.png" alt-text="Screenshot of multiple installer questions about setting an alternate DNS server." lightbox="./images/use-custom-dns-3.png":::
|
||||
|
||||
If you use a dynamic IP address, the DHCP server will automatically configure the IP address and DNS settings.
|
||||
|
||||
1. Choose where you would like to download, install, and store the virtual hard disk for EFLOW. You'll also be asked how much memory, storage, and how many cores you would like to allocate for the VM. For this example, we chose the default values for download path, install path, and virtual hard disk path.
|
||||
|
||||
<!-- Insert Image 4 -->
|
||||
:::image type="content" source="./images/installation-info-4.png" alt-text="Screenshot of multiple installer questions about memory and storage for EFLOW." lightbox="./images/installation-info-4.png":::
|
||||
|
||||
For more information, see [Sizing Recommendations](mcc-enterprise-prerequisites.md#sizing-recommendations) for memory, virtual storage, and CPU cores. For this example we chose the recommended values for a Branch Office/Small Enterprise deployment.
|
||||
|
||||
<!-- Insert Image 5 -->
|
||||
:::image type="content" source="./images/memory-storage-5.png" alt-text="Screenshot of multiple installer questions about memory and storage." lightbox="./images/memory-storage-5.png":::
|
||||
<!-- Remove: If this is your first MCC deployment, select **n** so that a new IoT Hub can be created. If you have already configured MCC before, choose **y** so that your MCCs are grouped in the same IoT Hub.
|
||||
|
||||
1. You'll be shown a list of existing IoT Hubs in your Azure subscription. Enter the number corresponding to the IoT Hub to select it. **You'll likely have only 1 IoT Hub in your subscription, in which case you want to enter "1"**
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-script-select-hub.png" alt-text="Screenshot of the installer script running in PowerShell prompting you to select which IoT Hub to use." lightbox="./images/ent-mcc-script-select-hub.png":::
|
||||
-->
|
||||
1. When the installation is complete, you should see the following output (the values below will be your own)
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-script-complete.png" alt-text="Screenshot of the installer script displaying the completion summary in PowerShell." lightbox="./images/ent-mcc-script-complete.png":::
|
||||
<!-- Insert Image 7 -->
|
||||
|
||||
:::image type="content" source="./images/installation-complete-7.png" alt-text="Screenshot of expected output when installation is complete." lightbox="./images/installation-complete-7.png":::
|
||||
|
||||
1. Your MCC deployment is now complete.
|
||||
|
||||
If you don't see any errors, continue to the next section to validate your MCC deployment. Your VM will not appear in Hyper-V Manager as it is an EFLOW VM.
|
||||
- After validating your MCC is properly functional, review your management solution documentation, such as [Intune](/mem/intune/configuration/delivery-optimization-windows), to set the cache host policy to the IP address of your MCC.
|
||||
- If you had errors during your deployment, see the [Common Issues](#common-issues) section in this article.
|
||||
|
||||
## Verify MCC server functionality
|
||||
|
||||
#### Verify client side
|
||||
|
||||
Connect to the EFLOW VM and check if MCC is properly running:
|
||||
|
||||
1. Open PowerShell as an Administrator.
|
||||
2. Enter the following commands:
|
||||
|
||||
```powershell
|
||||
Connect-EflowVm
|
||||
sudo -s
|
||||
iotedge list
|
||||
```
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-connect-eflowvm.png" alt-text="Screenshot of running connect-EflowVm, sudo -s, and iotedge list from PowerShell." lightbox="./images/ent-mcc-connect-eflowvm.png":::
|
||||
|
||||
You should see MCC, edgeAgent, and edgeHub running. If you see edgeAgent or edgeHub but not MCC, try this command in a few minutes. The MCC container can take a few minutes to deploy. If iotedge list times out, you can run docker ps -a to list the running containers.
|
||||
If the 3 containers are still not running, run the following commands to check if DNS resolution is working correctly:
|
||||
|
||||
```bash
|
||||
ping www.microsoft.com
|
||||
resolvectl query microsoft.com
|
||||
```
|
||||
|
||||
See the [common issues](#common-issues) section for more information.
|
||||
|
||||
#### Verify server side
|
||||
|
||||
To validate that MCC is properly functioning, execute the following command in the EFLOW VM or any device in the network. Replace <CacheServerIP\> with the IP address of the cache server.
|
||||
|
||||
```powershell
|
||||
wget http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com
|
||||
```
|
||||
|
||||
A successful test result will display a status code of 200 along with additional information.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-verify-server-ssh.png" alt-text="Screenshot of a successful wget with an SSH client." lightbox="./images/ent-mcc-verify-server-ssh.png":::
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-verify-server-powershell.png" alt-text="Screenshot of a successful wget using PowerShell." lightbox="./images/ent-mcc-verify-server-powershell.png":::
|
||||
|
||||
Similarly, enter the following URL from a browser in the network:
|
||||
|
||||
`http://<YourCacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com`
|
||||
|
||||
If the test fails, see the [common issues](#common-issues) section for more information.
|
||||
|
||||
### Intune (or other management software) configuration for MCC
|
||||
|
||||
For an [Intune](/mem/intune/) deployment, create a **Configuration Profile** and include the Cache Host eFlow IP Address or FQDN:
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-intune-do.png" alt-text="Screenshot of Intune showing the Delivery Optimization cache server host names.":::
|
||||
|
||||
## Common Issues
|
||||
|
||||
#### PowerShell issues
|
||||
|
||||
If you're seeing errors similar to this error: `The term Get-<Something> isn't recognized as the name of a cmdlet, function, script file, or operable program.`
|
||||
|
||||
1. Ensure you're running Windows PowerShell version 5.x.
|
||||
|
||||
1. Run \$PSVersionTable and ensure you're running version 5.x and *not version 6 or 7*.
|
||||
|
||||
1. Ensure you have Hyper-V enabled:
|
||||
|
||||
**Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
|
||||
|
||||
**Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server)
|
||||
|
||||
#### Verify Running MCC Container
|
||||
|
||||
Connect to the Connected Cache server and check the list of running IoT Edge modules using the following commands:
|
||||
|
||||
```bash
|
||||
Connect-EflowVm
|
||||
sudo iotedge list
|
||||
```
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-iotedge-list.png" alt-text="Screenshot of the iotedge list command." lightbox="./images/ent-mcc-iotedge-list.png":::
|
||||
|
||||
If edgeAgent and edgeHub containers are listed, but not "MCC", you may view the status of the IoT Edge security manager by using the command:
|
||||
|
||||
```bash
|
||||
sudo journalctl -u iotedge -f
|
||||
```
|
||||
|
||||
This command will provide the current status of the starting, stopping of a container, or the container pull and start.
|
||||
|
||||
:::image type="content" source="./images/ent-mcc-journalctl.png" alt-text="Screenshot of the output from journalctl -u iotedge -f." lightbox="./images/ent-mcc-journalctl.png":::
|
||||
|
||||
> [!NOTE]
|
||||
> You should consult the IoT Edge troubleshooting guide ([Common issues and resolutions for Azure IoT Edge](/azure/iot-edge/troubleshoot)) for any issues you may encounter configuring IoT Edge, but we've listed a few issues that we encountered during our internal validation.
|
||||
|
||||
|
||||
### DNS needs to be configured
|
||||
|
||||
Run the following IoT Edge install state check:
|
||||
|
||||
```bash
|
||||
sudo iotedge check --verbose
|
||||
```
|
||||
|
||||
If you see issues with ports 5671, 443, and 8883, your IoT Edge device needs to update the DNS for Docker.
|
||||
|
||||
To configure the device to work with your DNS, use the following steps:
|
||||
|
||||
1. Use `ifconfig` to find the appropriate NIC adapter name.
|
||||
|
||||
```bash
|
||||
ifconfig
|
||||
```
|
||||
|
||||
1. Run `nmcli device show <network adapter name>` to show the DNS name for the ethernet adapter. For example, to show DNS information for **eno1**:
|
||||
|
||||
```bash
|
||||
nmcli device show eno1
|
||||
```
|
||||
|
||||
:::image type="content" source="images/mcc-isp-nmcli.png" alt-text="Screenshot of a sample output of nmcli command to show network adapter information." lightbox="./images/mcc-isp-nmcli.png":::
|
||||
|
||||
1. Open or create the Docker configuration file used to configure the DNS server.
|
||||
|
||||
```bash
|
||||
sudo nano /etc/docker/daemon.json
|
||||
```
|
||||
|
||||
1. Paste the following string into the **daemon.json** file, and include the appropriate DNS server address. For example, in the previous screenshot, `IP4.DNS[1]` is `10.50.10.50`.
|
||||
|
||||
```bash
|
||||
{ "dns": ["x.x.x.x"]}
|
||||
```
|
||||
|
||||
1. Save the changes to daemon.json. If you need to change permissions on this file, use the following command:
|
||||
|
||||
```bash
|
||||
sudo chmod 555 /etc/docker/daemon.json
|
||||
```
|
||||
|
||||
1. Restart Docker to pick up the new DNS setting. Then restart IoT Edge.
|
||||
|
||||
```bash
|
||||
sudo systemctl restart docker
|
||||
sudo systemctl daemon-reload
|
||||
sudo restart IoTEdge
|
||||
```
|
||||
|
||||
### Resolve DNS issues
|
||||
|
||||
Follow these steps if you see a DNS error when trying to resolve hostnames during the provisioning or download of container:
|
||||
Run `Get-EflowVmEndpoint` to get interface name
|
||||
|
||||
Once you get the name:
|
||||
|
||||
```bash
|
||||
Set-EflowVmDNSServers -vendpointName "interface name from above" -dnsServers @("DNS_IP_ADDRESS")
|
||||
Stop-EflowVm
|
||||
Start-EflowVm
|
||||
```
|
||||
@ -1,61 +0,0 @@
|
||||
---
|
||||
title: Requirements for MCC for Enterprise and Education
|
||||
description: Overview of prerequisites and recommendations for using Microsoft Connected Cache (MCC) for Enterprise and Education.
|
||||
ms.service: windows-client
|
||||
ms.subservice: itpro-updates
|
||||
ms.topic: conceptual
|
||||
ms.author: carmenf
|
||||
author: cmknox
|
||||
manager: aaroncz
|
||||
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 and Education</a>
|
||||
ms.date: 05/23/2024
|
||||
---
|
||||
|
||||
# Requirements of Microsoft Connected Cache for Enterprise and Education (early preview)
|
||||
|
||||
> [!NOTE]
|
||||
> 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).
|
||||
|
||||
## 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.
|
||||
|
||||
> [!NOTE]
|
||||
> Azure VMs are not currently supported. If you'd like to install your cache node on VMWare, see the [Appendix](mcc-enterprise-appendix.md) for a few additional configurations.
|
||||
|
||||
**EFLOW requires Hyper-V support**
|
||||
- On Windows client, enable the Hyper-V feature.
|
||||
- On Windows Server, install the Hyper-V role and create a default network switch.
|
||||
- For more requirements, see [EFLOW requirements](/azure/iot-edge/iot-edge-for-linux-on-windows#prerequisites).
|
||||
|
||||
Disk recommendations:
|
||||
- Using an SSD is recommended as cache read speed of SSD is superior to HDD
|
||||
|
||||
NIC requirements:
|
||||
- Multiple NICs on a single MCC instance aren't supported.
|
||||
- 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
|
||||
- For best performance, NIC and BIOS should support SR-IOV.
|
||||
|
||||
VM networking:
|
||||
- An external virtual switch to support outbound and inbound network communication (created during the installation process)
|
||||
1. **Content endpoints**: If you're using a proxy or firewall, certain endpoints must be allowed through in order for your MCC to cache and serve content. See [Delivery Optimization and Microsoft Connected Cache content type endpoints](delivery-optimization-endpoints.md) for the list of required endpoints.
|
||||
|
||||
## Sizing recommendations
|
||||
|
||||
| Component | Branch Office / Small Enterprise | Large Enterprise |
|
||||
| -- | --- | --- |
|
||||
| OS| Windows Server 2019*/2022 <br> Windows 10*/11 (Pro or Enterprise) with Hyper-V Support <br><br>* Windows 10 and Windows Server 2019 build 17763 or later | Same |
|
||||
|NIC | 1 Gbps | 5 Gbps |
|
||||
|Disk | SSD <br>1 drive <br>50 GB each |SSD <br>1 drive <br>200 GB each |
|
||||
|Memory | 4 GB | 8 GB |
|
||||
|Cores | 4 | 8 |
|
||||
@ -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
|
||||
@ -17,7 +17,7 @@ metadata:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/en-us/windows/release-health/windows-server-release-info target=_blank>Windows Server 2019, and later</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 09/10/2024
|
||||
ms.date: 10/15/2024
|
||||
title: Frequently Asked Questions about Delivery Optimization
|
||||
summary: |
|
||||
This article answers frequently asked questions about Delivery Optimization.
|
||||
@ -42,6 +42,7 @@ summary: |
|
||||
**Peer-to-peer related questions**:
|
||||
|
||||
- [How does Delivery Optimization determine which content is available for peering?](#how-does-delivery-optimization-determine-which-content-is-available-for-peering)
|
||||
- [Where does Delivery Optimization get content from first?](#where-does-delivery-optimization-get-content-from-first)
|
||||
- [Does Delivery Optimization use multicast?](#does-delivery-optimization-use-multicast)
|
||||
- [How does Delivery Optimization deal with congestion on the router from peer-to-peer activity on the LAN?](#how-does-delivery-optimization-deal-with-congestion-on-the-router-from-peer-to-peer-activity-on-the-lan)
|
||||
- [How does Delivery Optimization handle VPNs?](#how-does-delivery-optimization-handle-vpns)
|
||||
@ -128,6 +129,11 @@ sections:
|
||||
- question: How does Delivery Optimization determine which content is available for peering?
|
||||
answer: |
|
||||
Delivery Optimization uses the cache content on the device to determine what's available for peering. For the upload source device, there's a limited number (4) of slots for cached content that's available for peering at a given time. Delivery Optimization contains logic that rotates the cached content in those slots.
|
||||
- question: Where does Delivery Optimization get content from first?
|
||||
answer: |
|
||||
When Delivery Optimization client is configured to use peers and Microsoft Connected Cache (MCC), the client connects to both MCC and peers in parallel. There is no prioritization between the two. Once downloading starts in parallel, Delivery Optimization
|
||||
will taper off requests to the HTTP source (CDN or MCC) when the peer connections are able to reach the target download speed. For background downloads, Delivery Optimization will drop HTTP connections if peers are meeting the minimum QoS speed. To manage delaying the default behavior
|
||||
there are a collection of policies that can be used. For more information, see [Delivery Optimization delay policies](waas-delivery-optimization-reference.md#policies-to-prioritize-the-use-of-peer-to-peer-and-cache-server-sources).
|
||||
- question: Does Delivery Optimization use multicast?
|
||||
answer: |
|
||||
No. It relies on the cloud service for peer discovery, resulting in a list of peers and their IP addresses. Client devices then connect to their peers to obtain download files over TCP/IP.
|
||||
|
||||
@ -14,7 +14,7 @@ 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-delivery-optimization target=_blank>Delivery Optimization</a>
|
||||
ms.date: 05/23/2024
|
||||
ms.date: 10/15/2024
|
||||
---
|
||||
|
||||
# Delivery Optimization reference
|
||||
@ -106,7 +106,7 @@ When Delivery Optimization client is configured to use peers and Microsoft Conne
|
||||
##### Microsoft Connected Cache (MCC) delay fallback settings
|
||||
|
||||
- [Delay foreground download cache server fallback (in secs)](#delay-foreground-download-cache-server-fallback-in-secs) allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use a cache server.
|
||||
- [Delay background download from HTTP (in secs)](#delay-background-download-from-http-in-secs) allows you to delay the use of an HTTP source in a background download that is allowed to use a cache server.
|
||||
- [Delay background download cache server fallback (in secs)](#delay-background-download-cache-server-fallback-in-secs) allows you to delay the use of an HTTP source in a background download that is allowed to use a cache server.
|
||||
|
||||
**If both peer-to-peer and MCC are configured, the peer-to-peer delay settings will take precedence over the cache server delay settings.** This setting allows Delivery Optimization to discover peers first then recognize the fallback setting for the MCC cache server.
|
||||
|
||||
@ -245,13 +245,13 @@ The default behaviors differ between Windows 10 and Windows 11. In Windows 10, t
|
||||
|
||||
MDM Setting: **DODelayForegroundDownloadFromHttp**
|
||||
|
||||
Starting in Windows 10, version 1803, allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use peer-to-peer. The maximum value is 4294967295 seconds. **By default, this policy isn't configured.**
|
||||
Starting in Windows 10, version 1803, allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use peer-to-peer. **By default, this policy isn't configured.**
|
||||
|
||||
### Delay background download from HTTP (in secs)
|
||||
|
||||
MDM Setting: **DODelayBackgroundDownloadFromHttp**
|
||||
|
||||
Starting in Windows 10, version 1803, this allows you to delay the use of an HTTP source in a background download that is allowed to use peer-to-peer. The maximum value is 4294967295 seconds. **By default, this policy isn't configured.**
|
||||
Starting in Windows 10, version 1803, this allows you to delay the use of an HTTP source in a background download that is allowed to use peer-to-peer. **By default, this policy isn't configured.**
|
||||
|
||||
### Delay foreground download cache server fallback (in secs)
|
||||
|
||||
|
||||
@ -24,7 +24,7 @@ ms.date: 05/23/2024
|
||||
Microsoft Connected Cache is a software-only caching solution that delivers Microsoft content. Microsoft Connected Cache has two main offerings:
|
||||
|
||||
- Microsoft Connected Cache for Internet Service Providers
|
||||
- Microsoft Connected Cache for Enterprise and Education (early preview)
|
||||
- Microsoft Connected Cache for Enterprise and Education (preview)
|
||||
|
||||
Both products are created and managed in the cloud portal.
|
||||
|
||||
@ -35,14 +35,14 @@ Both products are created and managed in the cloud portal.
|
||||
|
||||
Microsoft Connected Cache (MCC) for Internet Service Providers is currently in preview. MCC can be deployed to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, MCC can help to reduce your network bandwidth usage for Microsoft software content and updates. Cache nodes are created in the cloud portal and are configured to deliver traffic to customers by manual CIDR or BGP routing. Learn more at [Microsoft Connected Cache for ISPs Overview](mcc-isp-overview.md).
|
||||
|
||||
## Microsoft Connected Cache for Enterprise and Education (early preview)
|
||||
## Microsoft Connected Cache for Enterprise and Education (preview)
|
||||
|
||||
> [!NOTE]
|
||||
> 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 is now in public preview. To get started, follow the instructions in the [Create Microsoft Connected Cache Azure resource and cache nodes](mcc-ent-create-resource-and-cache.md) article.
|
||||
|
||||
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. Learn more at [Microsoft Connected Cache for Enterprise and Education Overview](mcc-ent-edu-overview.md).
|
||||
Microsoft Connected Cache (MCC) for Enterprise and Education 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. Learn more at [Microsoft Connected Cache for Enterprise and Education Overview](mcc-ent-edu-overview.md).
|
||||
|
||||
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 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 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)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
||||
@ -43,8 +43,8 @@ There are two different versions:
|
||||
|
||||
### Windows 11 22H2
|
||||
|
||||
- New setting: Customize vpn detection by choosing custom keywords. Now, you don't have to rely on Delivery Optimization keywords to detect your Vpn. By using the new VpnKeywords configuration you can add keywords for Delivery Optimization to use when detecting a Vpn when in use. You can find this configuration **[VPN Keywords](waas-delivery-optimization-reference.md#vpn-keywords)** in Group Policy or MDM under **DOVpnKeywords**.
|
||||
- New setting: Use the disallow downloads from a connected cache server, when a Vpn is detected and you want to prevent the download from the connected cache server. You can find this configuration **[Disallow download from MCC over VPN](waas-delivery-optimization-reference.md#disallow-cache-server-downloads-on-vpn) in Group Policy or MDM under **DODisallowCacheServerDownloadsOnVPN**.
|
||||
- New setting: Customize VPN detection by choosing custom keywords. Now, you don't have to rely on Delivery Optimization keywords to detect your VPN. By using the new VpnKeywords setting, you can add keywords for Delivery Optimization to use to detect when a VPN is in use. You can find this configuration **[VPN Keywords](waas-delivery-optimization-reference.md#vpn-keywords)** in Group Policy or MDM under **DOVpnKeywords**.
|
||||
- New setting: Use the disallow downloads from a connected cache server, when a VPN is detected and you want to prevent the download from the connected cache server. You can find this configuration **[Disallow download from MCC over VPN](waas-delivery-optimization-reference.md#disallow-cache-server-downloads-on-vpn)** in Group Policy or MDM under **DODisallowCacheServerDownloadsOnVPN**.
|
||||
- Delivery Optimization introduced support for receiver side ledbat (rLEDBAT).
|
||||
- New setting: Local Peer Discovery, a new option for **[Restrict Peer Selection By](waas-delivery-optimization-reference.md#select-a-method-to-restrict-peer-selection)** in Group Policy or MDM **DORestrictPeerSelectionBy**. This option restricts the discovery of local peers using the DNS-SD protocol. When you set Option 2, Delivery Optimization restricts peer selection to peers that are locally discovered (using DNS-SD).
|
||||
|
||||
|
||||
@ -13,7 +13,7 @@ appliesto:
|
||||
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/mem/configmgr/ > Microsoft Configuration Manager</a>
|
||||
- ✅ <a href=https://learn.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus > WSUS </a>
|
||||
ms.date: 04/22/2024
|
||||
ms.date: 10/01/2024
|
||||
---
|
||||
|
||||
# How to make Features on Demand and language packs available when you're using WSUS or Configuration Manager
|
||||
@ -31,11 +31,13 @@ Due to these changes, the **Specify settings for optional component installation
|
||||
|
||||
The introduction of the **Specify source service for specific classes of Windows Updates** ([SetPolicyDrivenUpdateSourceFor<UpdateClass\>](/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourceforfeatureupdates)) policy in Windows 10, version 2004 further complicated configuring settings for FoD and language pack content.
|
||||
|
||||
Starting in Windows 11, version 22H2, on-premises Unified Update Platform (UUP) updates were introduced. FoDs and language packs are available from WSUS again. It's no longer necessary to use the **Specify settings for optional component installation and component repair** policy for FoD and language pack content.
|
||||
Starting in Windows 11, version 22H2, on-premises Unified Update Platform (UUP) updates were introduced. FoDs and language packs are available from WSUS again. It's no longer necessary to use the **Specify settings for optional component installation and component repair** policy for FoD and language pack content. This policy was modified starting in Windows 11, version 24H2 and the following options were removed:<!--8914508-->
|
||||
- Never attempt to download payload from Windows Update
|
||||
- Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)
|
||||
|
||||
## Version specific information for Features on Demand and language packs
|
||||
|
||||
Windows 11, version 22H2, and later clients use on-premises Unified Update Platform (UUP) updates with WSUS and Microsoft Configuration Manager. These clients don't need to use **Specify settings for optional component installation and component repair** for FoDs and language packs since the content is available in WSUS due to on-premises UUP.
|
||||
Windows 11, version 22H2, and later clients use on-premises Unified Update Platform (UUP) updates with WSUS and Microsoft Configuration Manager. These clients don't need to use **Specify settings for optional component installation and component repair** for FoDs and language packs since the content is available in WSUS due to on-premises UUP. The policy was modified starting in Windows 11, version 24H2 to remove the unneeded options.<!--8914508-->
|
||||
|
||||
For Windows 10, version 2004 through Windows 11, version 21H2, clients can't download FoDs or language packs when **Specify settings for optional component installation and component repair** is set to Windows Update and **Specify source service for specific classes of Windows Updates** ([SetPolicyDrivenUpdateSourceFor<FeatureUpdates/QualityUpdates>](/windows/client-management/mdm/policy-csp-update#setpolicydrivenupdatesourceforfeatureupdates)) for either feature or quality updates is set to WSUS. If you need this content, you can set **Specify settings for optional component installation and component repair** to Windows Update and then either:
|
||||
- Change the source selection for feature and quality updates to Windows Update
|
||||
|
||||
@ -14,7 +14,7 @@ ms.localizationpriority: medium
|
||||
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>
|
||||
ms.date: 10/10/2023
|
||||
ms.date: 10/04/2024
|
||||
---
|
||||
|
||||
# Manage device restarts after updates
|
||||
@ -215,4 +215,4 @@ There are three different registry combinations for controlling restart behavior
|
||||
- [Configure Windows Update for Business](waas-configure-wufb.md)
|
||||
- [Integrate Windows Update for Business with management solutions](waas-integrate-wufb.md)
|
||||
- [Walkthrough: use Group Policy to configure Windows Update for Business](waas-wufb-group-policy.md)
|
||||
- [Walkthrough: use Intune to configure Windows Update for Business](/intune/windows-update-for-business-configure)
|
||||
- [Manage Windows 10 and Windows 11 software updates in Intune](/mem/intune/protect/windows-update-for-business-configure)
|
||||
|
||||
@ -11,7 +11,7 @@ ms.collection:
|
||||
- highpri
|
||||
- tier2
|
||||
ms.subservice: itpro-deploy
|
||||
ms.date: 10/02/2023
|
||||
ms.date: 10/04/2024
|
||||
appliesto:
|
||||
- ✅ <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/release-health/supported-versions-windows-client" target="_blank">Windows 11</a>
|
||||
@ -56,7 +56,7 @@ The following table shows the methods and paths available to change the edition
|
||||
>
|
||||
> - Each desktop edition in the table also has an N and KN SKU. These editions have had media-related functionality removed. Devices with N or KN SKUs installed can be upgraded to corresponding N or KN SKUs using the same methods.
|
||||
>
|
||||
> - Edition upgrades via Microsoft Store for Business are no longer available with the retirement of the Microsoft Store for Business. For more information, see [Microsoft Store for Business and Education retiring March 31, 2023](/lifecycle/announcements/microsoft-store-for-business-education-retiring) and [Microsoft Store for Business and Microsoft Store for Education overview](/microsoft-store/microsoft-store-for-business-overview).
|
||||
> - Edition upgrades via Microsoft Store for Business are no longer available with the retirement of the Microsoft Store for Business. For more information, see [Microsoft Store for Business and Education retiring March 31, 2023](/lifecycle/announcements/microsoft-store-for-business-education-retiring).
|
||||
|
||||
> [!TIP]
|
||||
> Edition upgrade is also possible using edition upgrade policy in Microsoft Configuration Manager. For more information, see [Upgrade Windows devices to a new edition with Configuration Manager](/mem/configmgr/compliance/deploy-use/upgrade-windows-version).
|
||||
|
||||
@ -66,8 +66,8 @@ These variables can be used within sections in the **.xml** files with `context=
|
||||
|*CSIDL_DEFAULT_TEMPLATES*|Refers to the Templates folder inside `%DEFAULTUSERPROFILE%`.|
|
||||
|*CSIDL_DEFAULT_QUICKLAUNCH*|Refers to the Quick Launch folder inside `%DEFAULTUSERPROFILE%`.|
|
||||
|*CSIDL_FONTS*|A virtual folder containing fonts. A typical path is `C:\Windows\Fonts`.|
|
||||
|*CSIDL_PROGRAM_FILESX86*|The Program Files folder on 64-bit systems. A typical path is `C:\Program Files(86)`.|
|
||||
|*CSIDL_PROGRAM_FILES_COMMONX86*|A folder for components that are shared across applications on 64-bit systems. A typical path is `C:\Program Files(86)\Common`.|
|
||||
|*CSIDL_PROGRAM_FILESX86*|The Program Files folder on 64-bit systems. A typical path is `C:\Program Files (x86)`.|
|
||||
|*CSIDL_PROGRAM_FILES_COMMONX86*|A folder for components that are shared across applications on 64-bit systems. A typical path is `C:\Program Files (x86)\Common`.|
|
||||
|*CSIDL_PROGRAM_FILES*|The Program Files folder. A typical path is `C:\Program Files`.|
|
||||
|*CSIDL_PROGRAM_FILES_COMMON*|A folder for components that are shared across applications. A typical path is `C:\Program Files\Common`.|
|
||||
|*CSIDL_RESOURCES*|The file-system directory that contains resource data. A typical path is `C:\Windows\Resources`.|
|
||||
|
||||
@ -41,7 +41,7 @@ The overall device registration process is as follows:
|
||||
:::image type="content" source="../media/windows-autopatch-device-registration-overview.png" alt-text="Overview of the device registration process" lightbox="../media/windows-autopatch-device-registration-overview.png":::
|
||||
|
||||
1. IT admin reviews [Windows Autopatch device registration prerequisites](#prerequisites-for-device-registration) before registering devices with Windows Autopatch.
|
||||
2. IT admin identifies and adds devices or nests other Microsoft Entra device groups into any Microsoft Entra group used with an Autopatch group, imported (WUfB) policies, or direct membership to the **Modern Workplace Devices-Windows-Autopatch-X-groups**.
|
||||
2. IT admin identifies and adds devices, or nests other Microsoft Entra device groups when you [create an Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#create-an-autopatch-group), [edit an Autopatch group](../manage/windows-autopatch-manage-autopatch-groups.md#edit-an-autopatch-group), or import Windows Update for Business (WUfB) policies.
|
||||
3. Windows Autopatch then:
|
||||
1. Performs device readiness prior registration (prerequisite checks).
|
||||
2. Calculates the deployment ring distribution.
|
||||
@ -77,7 +77,7 @@ The deployment ring distribution is designed to release software update deployme
|
||||
|
||||
### Device record and deployment ring assignment
|
||||
|
||||
Registering your devices with Windows Autopatch does the following:
|
||||
When you register your devices, Windows Autopatch:
|
||||
|
||||
1. Makes a record of devices in the service.
|
||||
2. Assign devices to the [deployment ring set](#default-deployment-ring-calculation-logic) and other groups required for software update management.
|
||||
|
||||
@ -42,12 +42,12 @@ These policies control the minimum target version of Windows that a device is me
|
||||
|
||||
You can see the following default policies created by the service in the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431):
|
||||
|
||||
| Policy name | Phase mapping | Feature update version | Rollout options | First deployment ring availability | Final deployment ring availability | Day between deployment rings | Support end date |
|
||||
| ----- | ----- | ----- | ----- | ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - DSS Policy [Test] | Phase 1 | Windows 10 21H2 | Make update available as soon as possible | May 9, 2023 | N/A | N/A | June 11, 2024 |
|
||||
| Windows Autopatch - DSS Policy [First] | Phase 2 | Windows 10 21H2 | Make update available as soon as possible | May 16, 2023 | N/A | N/A | June 11, 2024 |
|
||||
| Windows Autopatch - DSS Policy [Fast] | Phase 3 | Windows 10 21H2 | Make update available as soon as possible | May 23, 2023 | N/A | N/A | June 11, 2024 |
|
||||
| Windows Autopatch - DSS Policy [Broad] | Phase 4 | Windows 10 21H2 | Make update available as soon as possible | May 30, 2023 | N/A | N/A | June 11, 2024 |
|
||||
| Policy name | Phase mapping | Feature update version | Rollout options | Support end date |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - DSS Policy [Test] | Phase 1 | Windows 10 22H2 | Make update available as soon as possible | October 14, 2025 |
|
||||
| Windows Autopatch - DSS Policy [First] | Phase 2 | Windows 10 22H2 | Make update available as soon as possible | October 14, 2025 |
|
||||
| Windows Autopatch - DSS Policy [Fast] | Phase 3 | Windows 10 22H2 | Make update available as soon as possible | October 14, 2025 |
|
||||
| Windows Autopatch - DSS Policy [Broad] | Phase 4 | Windows 10 22H2 | Make update available as soon as possible | October 14, 2025 |
|
||||
|
||||
> [!NOTE]
|
||||
> Gradual rollout settings aren't configured in the default Windows Update feature policy. If the date of the final group availability is changed to a past date, all remaining devices are offered the update as soon as possible. For more information, see [rollout options for Windows Updates in Microsoft Intune](/mem/intune/protect/windows-update-rollout-options#make-updates-available-gradually).
|
||||
@ -56,9 +56,9 @@ You can see the following default policies created by the service in the [Micros
|
||||
|
||||
Windows Autopatch configures the values for its global Windows feature update policy. See the following default policies created by the service in the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431):
|
||||
|
||||
| Policy name | Feature update version | Rollout options | First deployment ring availability | Final deployment ring availability | Day between deployment rings | Support end date |
|
||||
| ----- | ----- | ----- | ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - Global DSS Policy [Test] | Windows 10 21H2 | Make update available as soon as possible | N/A | N/A | N/A | June 11, 2024 |
|
||||
| Policy name | Feature update version | Rollout options | Support end date |
|
||||
| ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - Global DSS Policy [Test] | Windows 10 22H2 | Make update available as soon as possible | October 14, 2025 |
|
||||
|
||||
> [!NOTE]
|
||||
> Gradual rollout settings aren't configured in the default Windows Update feature policy. If the date of the final group availability is changed to be a past date, all remaining devices are offered the update as soon as possible. For more information, see [rollout options for Windows Updates in Microsoft Intune](/mem/intune/protect/windows-update-rollout-options#make-updates-available-gradually).
|
||||
@ -101,11 +101,11 @@ These policies can be viewed in the [Microsoft Intune admin center](https://go.m
|
||||
|
||||
The following table is an example of the Windows feature update policies that were created for phases within a release:
|
||||
|
||||
| Policy name | Feature update version | Rollout options | First deployment date| Final deployment date availability | Day between groups | Support end date |
|
||||
| ----- | ----- | ----- | ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 1 | Windows 10 21H2 | Make update available as soon as possible | April 24, 2023 | April 24, 2023 | N/A | June 11, 2024 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 2 | Windows 10 21H2 | Make update available as soon as possible | June 26, 2023 | July 17, 2023 | 7 | June 11, 2024 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 3 | Windows 10 21H2 | Make update available as soon as possible | July 24, 2023 | August 14, 2023 | 7 | June 11, 2024 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 4 | Windows 10 21H2 | Make update available as soon as possible | August 28, 2023 | September 10, 2023 | 7 | June 11, 2024 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 5 | Windows 10 21H2 | Make update available as soon as possible | September 25, 2023 | October 16, 2023 | 7 | June 11, 2024 |
|
||||
| Policy name | Feature update version | Rollout options| Day between groups | Support end date |
|
||||
| ----- | ----- | ----- | ----- | ----- |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 1 | Windows 10 22H2 | Make update available as soon as possible| N/A | October 14, 2025 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 2 | Windows 10 22H2 | Make update available as soon as possible | 7 | October 14, 2025 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 3 | Windows 10 22H2 | Make update available as soon as possible | 7 | October 14, 2025 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 4 | Windows 10 22H2 | Make update available as soon as possible | 7 | October 14, 2025 |
|
||||
| Windows Autopatch - DSS Policy - My feature update release - Phase 5 | Windows 10 22H2 | Make update available as soon as possible | 7 | October 14, 2025 |
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Windows quality update end user experience
|
||||
description: This article explains the Windows quality update end user experience
|
||||
ms.date: 09/16/2024
|
||||
ms.date: 10/07/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: conceptual
|
||||
@ -32,9 +32,7 @@ In this section we review what an end user would see in the following three scen
|
||||
|
||||
### Typical update experience
|
||||
|
||||
The Windows quality update is published and devices in the Broad ring have a deferral period of nine days. Devices wait nine days before downloading the latest quality update.
|
||||
|
||||
In the following example, the user:
|
||||
In the following example, the Windows quality update is published and devices in the Broad ring have a deferral period of seven days. Devices wait seven days before downloading the latest quality update.
|
||||
|
||||
| Day | Description |
|
||||
| --- | --- |
|
||||
@ -46,7 +44,7 @@ In the following example, the user:
|
||||
|
||||
### Quality update deadline forces an update
|
||||
|
||||
In the following example, the user:
|
||||
In the following example:
|
||||
|
||||
| Day | Description |
|
||||
| --- | --- |
|
||||
@ -58,7 +56,7 @@ In the following example, the user:
|
||||
|
||||
### Quality update grace period
|
||||
|
||||
In the following example, the user:
|
||||
In the following example:
|
||||
|
||||
| Day | Description |
|
||||
| --- | --- |
|
||||
|
||||
@ -63,7 +63,7 @@ The following URLs must be on the allowed list of your proxy and firewall so tha
|
||||
|
||||
| Microsoft service | URLs required on allowlist |
|
||||
| ----- | ----- |
|
||||
| Windows Autopatch | <ul><li>mmdcustomer.microsoft.com</li><li>mmdls.microsoft.com</li><li>logcollection.mmd.microsoft.com</li><li>support.mmd.microsoft.com</li><li>devicelistenerprod.microsoft.com</li><li>login.windows.net</li><li>payloadprod*.blob.core.windows.net</li></ul>|
|
||||
| Windows Autopatch | <ul><li>mmdcustomer.microsoft.com</li><li>mmdls.microsoft.com</li><li>logcollection.mmd.microsoft.com</li><li>support.mmd.microsoft.com</li><li>devicelistenerprod.microsoft.com</li><li>login.windows.net</li><li>payloadprod*.blob.core.windows.net</li><li>device.autopatch.microsoft.com</li></ul>|
|
||||
|
||||
## Delivery Optimization
|
||||
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
---
|
||||
title: What's new 2023
|
||||
description: This article lists the 2023 feature releases and any corresponding Message center post numbers.
|
||||
ms.date: 12/14/2023
|
||||
ms.date: 10/07/2024
|
||||
ms.service: windows-client
|
||||
ms.subservice: autopatch
|
||||
ms.topic: whats-new
|
||||
|
||||
@ -105,7 +105,6 @@ For more information about implementing Credential Guard, see the following reso
|
||||
- [Security considerations for Original Equipment Manufacturers](/windows-hardware/design/device-experiences/oem-security-considerations)
|
||||
- [Device Guard and Credential Guard hardware readiness tool](https://www.microsoft.com/download/details.aspx?id=53337)
|
||||
|
||||
|
||||
### AppLocker management
|
||||
|
||||
AppLocker in Windows Enterprise can be managed by using Group Policy. Group Policy requires having AD DS and that the Windows Enterprise devices are joined to an AD DS domain. AppLocker rules can be created by using Group Policy. The AppLocker rules can then be targeted to the appropriate devices.
|
||||
|
||||
Reference in New Issue
Block a user