From ae33c40e6103d7f7396ab40ac509f3eb520bf54f Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:13:17 -0700 Subject: [PATCH 01/11] mcc-branding --- .../client-management/mdm/policy-csp-deliveryoptimization.md | 4 ++-- windows/deployment/do/delivery-optimization-configure.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-deliveryoptimization.md b/windows/client-management/mdm/policy-csp-deliveryoptimization.md index 171f5c4349f..2d2289e9572 100644 --- a/windows/client-management/mdm/policy-csp-deliveryoptimization.md +++ b/windows/client-management/mdm/policy-csp-deliveryoptimization.md @@ -164,7 +164,7 @@ One or more values can be added as either fully qualified domain names (FQDN) or > [!NOTE] -> Clients don't talk to multiple Microsoft Connected Cache (MCC) servers at the same time. If you configure a list of MCC servers in this policy, the clients will round robin until they successfully connect to an MCC server. The clients have no way to determine if the MCC server has the content or not. If the MCC server doesn't have the content, it caches the content as it is handing the content back to the client. +> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to an Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client. @@ -578,7 +578,7 @@ Specifies the download method that Delivery Optimization can use in downloads of > [!NOTE] -> The Delivery Optimization service on the clients checks to see if there are peers and/or an MCC server which contains the content and determines the best source for the content. +> The Delivery Optimization service on the clients checks to see if there are peers and/or a Connected Cache server which contains the content and determines the best source for the content. diff --git a/windows/deployment/do/delivery-optimization-configure.md b/windows/deployment/do/delivery-optimization-configure.md index cfe43ce385f..7722670c70d 100644 --- a/windows/deployment/do/delivery-optimization-configure.md +++ b/windows/deployment/do/delivery-optimization-configure.md @@ -35,7 +35,7 @@ Use this checklist to guide you through different aspects when modifying Deliver * System resources * Improve P2P efficiencies -1. Using Connected Cache (MCC) +1. Using Microsoft Connected Cache 1. Choose where to set Delivery Optimization policies ## 1. Prerequisites to allow Delivery Optimization communication @@ -189,7 +189,7 @@ Regardless of P2P, consider setting the following policies to avoid network disr > [!NOTE] > The absolute policies are recommended in low bandwidth environments. -## 3. Using Connected Cache (MCC) +## 3. Using Connected Cache :::image type="content" source="images/do-setup-connected-cache.png" alt-text="Screenshot of Delivery Optimization options when using Connected Cache." lightbox="images/do-setup-connected-cache.png"::: From 140ca2dc603e7b5b2a971b2dfcbc53ae7c0b63a8 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:25:09 -0700 Subject: [PATCH 02/11] mcc-branding --- .../do/delivery-optimization-troubleshoot.md | 2 +- windows/deployment/do/index.yml | 12 +++---- windows/deployment/do/mcc-ent-edu-overview.md | 32 +++++++++---------- 3 files changed, 23 insertions(+), 23 deletions(-) diff --git a/windows/deployment/do/delivery-optimization-troubleshoot.md b/windows/deployment/do/delivery-optimization-troubleshoot.md index 5ade7e311fd..972b148de43 100644 --- a/windows/deployment/do/delivery-optimization-troubleshoot.md +++ b/windows/deployment/do/delivery-optimization-troubleshoot.md @@ -29,7 +29,7 @@ This article discusses how to troubleshoot Delivery Optimization. - -HealthCheck: Provides an overall check of the device setup to ensure Delivery Optimization communication is possible on the device. - -P2P: Provides output specific to P2P settings, efficiency, and errors. -- -MCC: Provides output specific to MCC settings and verifies the client can access the cache server. +- -MCC: Provides output specific to Microsoft Connected Cache settings and verifies the client can access the cache server. ## Common problems and solutions diff --git a/windows/deployment/do/index.yml b/windows/deployment/do/index.yml index d2e3a5c60a1..42eddd71c7f 100644 --- a/windows/deployment/do/index.yml +++ b/windows/deployment/do/index.yml @@ -32,7 +32,7 @@ landingContent: url: waas-delivery-optimization.md - text: What's new in Delivery Optimization url: whats-new-do.md - - text: Microsoft Connected Cache (MCC) overview + - text: Microsoft Connected Cache overview url: waas-microsoft-connected-cache.md @@ -63,25 +63,25 @@ landingContent: url: /mem/intune/configuration/delivery-optimization-windows # Card - - title: Microsoft Connected Cache (MCC) for Enterprise and Education + - title: Microsoft Connected Cache for Enterprise and Education linkLists: - linkListType: deploy links: - - text: MCC for Enterprise and Education (early preview) + - text: Connected Cache for Enterprise and Education (early preview) url: waas-microsoft-connected-cache.md - text: Sign up url: https://aka.ms/MSConnectedCacheSignup # Card - - title: Microsoft Connected Cache (MCC) for Internet Service Providers (ISPs) + - title: Microsoft Connected Cache for Internet Service Providers (ISPs) linkLists: - linkListType: deploy links: - - text: MCC for ISPs (public preview) + - text: Connected Cache for ISPs (public preview) url: mcc-isp-signup.md - text: Sign up url: https://aka.ms/MCCForISPSurvey - - text: MCC for ISPs (early preview) + - text: Connected Cache for ISPs (early preview) url: mcc-isp.md diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index b17beaa30ad..42d89b15137 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.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: Microsoft Connected Cache for Enterprise and Education Overview +description: Overview, supported scenarios, and content types for Microsoft Connected Cache for Enterprise and Education. ms.service: windows-client ms.subservice: itpro-updates ms.topic: conceptual @@ -23,9 +23,9 @@ ms.date: 05/23/2024 > - 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 for Enterprise and Education (early preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache 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 (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 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). ## Supported scenarios @@ -47,27 +47,27 @@ For the full list of content endpoints that Microsoft Connected Cache for Enterp ## 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. +Connected Cache 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. Connected Cache is a Linux IoT Edge module running on the Windows Host OS. -1. The Azure Management Portal is used to create MCC nodes. -1. The MCC container is deployed and provisioned to the server using the installer provided in the portal. +1. The Azure Management Portal is used to create Connected Cache nodes. +1. The Connected Cache 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. Microsoft end-user devices make range requests for content from the Connected Cache node. +1. The Connected Cache node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client. 1. Subsequent requests from end-user devices for content will now come from cache. -1. If the MCC node is unavailable, the client pulls content from CDN to ensure uninterrupted service for your subscribers. +1. If the Connected Cache node is unavailable, the client pulls content from CDN to ensure uninterrupted service for your subscribers. -The following diagram displays an overview of how MCC functions: +The following diagram displays an overview of how Connected Cache 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"::: +:::image type="content" source="./images/waas-mcc-diag-overview.png" alt-text="Diagram displaying the components of Connected Cache." lightbox="./images/waas-mcc-diag-overview.png"::: ## IoT Edge -Even though your MCC scenario isn't related to IoT, Azure IoT Edge is used as a more generic Linux container deployment and management infrastructure. The Azure IoT Edge runtime sits on your designated MCC device and performs management and communication operations. The runtime performs several functions important to manage MCC on your edge device: +Even though your Connected Cache 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 Connected Cache device and performs management and communication operations. The runtime performs several functions important to manage Connected Cache on your edge device: -1. Installs and updates MCC on your edge device. +1. Installs and updates Connected Cache 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. +1. Ensures that Connected Cache is always running. +1. Reports Connected Cache 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). From cfa0047001499eb75e6d1c0a5c6d59b3ba641489 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 23 Oct 2024 16:30:47 -0700 Subject: [PATCH 03/11] mcc-branding --- .../deployment/do/mcc-enterprise-appendix.md | 24 +++--- .../deployment/do/mcc-enterprise-deploy.md | 80 +++++++++---------- 2 files changed, 52 insertions(+), 52 deletions(-) diff --git a/windows/deployment/do/mcc-enterprise-appendix.md b/windows/deployment/do/mcc-enterprise-appendix.md index 6264ea32c41..aab4bc87d2b 100644 --- a/windows/deployment/do/mcc-enterprise-appendix.md +++ b/windows/deployment/do/mcc-enterprise-appendix.md @@ -1,6 +1,6 @@ --- -title: Appendix for MCC for Enterprise and Education -description: This article contains reference information for Microsoft Connected Cache (MCC) for Enterprise and Education. +title: Appendix for Microsoft Connected Cache for Enterprise and Education +description: This article contains reference information for Microsoft Connected Cache for Enterprise and Education. ms.service: windows-client ms.subservice: itpro-updates ms.topic: reference @@ -49,11 +49,11 @@ To learn more about how to configure Intel and AMD processors to support nested ## 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. +If you're having issues with your Microsoft Connected Cache, 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 Connected Cache team to debug. To run this script: -1. Navigate to the following folder in the MCC installation files: +1. Navigate to the following folder in the Connected Cache installation files: mccinstaller > Eflow > Diagnostics @@ -66,7 +66,7 @@ To run this script: 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 **\**\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. +1. [Email the Connected Cache 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 @@ -82,15 +82,15 @@ communication operations. The runtime performs several functions: 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 +## Routing local Windows clients to an Connected Cache -### Get the IP address of your MCC using ifconfig +### Get the IP address of your Connected Cache using ifconfig -There are multiple methods that can be used to apply a policy to PCs that should participate in downloading from the MCC. +There are multiple methods that can be used to apply a policy to PCs that should participate in downloading from the Connected Cache. #### Registry key -You can either set your MCC IP address or FQDN using: +You can either set your Connected Cache IP address or FQDN using: 1. Registry key (version 1709 and later): `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization` @@ -107,19 +107,19 @@ You can either set your MCC IP address or FQDN using: `.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`. +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 Connected Cache using Group Policy, go to **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Delivery Optimization**. Set the **Cache Server Hostname** to the IP address of your Connected Cache, 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: +To verify that the Delivery Optimization client can download content using Connected Cache, 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: +1. Verify downloads came from Connected Cache by one of two methods: - Using the PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see *BytesFromCacheServer*. diff --git a/windows/deployment/do/mcc-enterprise-deploy.md b/windows/deployment/do/mcc-enterprise-deploy.md index 5cc7236b510..a149ae9c8d0 100644 --- a/windows/deployment/do/mcc-enterprise-deploy.md +++ b/windows/deployment/do/mcc-enterprise-deploy.md @@ -1,6 +1,6 @@ --- title: Deploying your cache node -description: How to deploy a Microsoft Connected Cache (MCC) for Enterprise and Education cache node from the Azure portal. +description: How to deploy a Microsoft Connected Cache for Enterprise and Education cache node from the Azure portal. ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -18,34 +18,34 @@ 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. +This article describes how to deploy a Microsoft Connected Cache for Enterprise and Education cache node. -## Steps to deploy MCC +## Steps to deploy Connected Cache -To deploy MCC to your server: +To deploy Connected Cache 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. [Create the Connected Cache Resource in Azure](#create-the-mcc-resource-in-azure) +1. [Create an Connected Cache 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. [Install Connected Cache on a physical server or VM](#install-mcc-on-windows) +1. [Verify Connected Cache 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. +As part of the Connected Cache 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 +### Create the Connected Cache 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. +The Connected Cache Azure management portal is used to create and manage Connected Cache nodes. An Azure subscription ID is used to grant access to the preview and to create the Connected Cache 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. +Once you take the survey above and the Connected Cache 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**: @@ -56,23 +56,23 @@ Once you take the survey above and the MCC team adds your subscription ID to the > [!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. +1. Select **Microsoft Connected Cache Enterprise** and choose **Create** on the next screen to start the process of creating the Connected Cache 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. +1. Fill in the required fields to create the Connected Cache 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. + - Choose **(US) West US** for the location of the resource. This choice won't impact Connected Cache 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** + > Your Connected Cache 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. + - Choose a name for the Connected Cache resource. + - Your Connected Cache 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."::: @@ -87,9 +87,9 @@ Once you take the survey above and the MCC team adds your subscription ID to the :::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 +### Create an Connected Cache 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. +Creating an Connected Cache node is a multi-step process and the first step is to access the Connected Cache 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**. @@ -112,7 +112,7 @@ Creating an MCC node is a multi-step process and the first step is to access the 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. +Once the Connected Cache 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."::: @@ -122,18 +122,18 @@ Cache nodes can be deleted here by selecting the check box to the left of a **Ca :::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 +### Install Connected Cache on Windows -Installing MCC on your Windows device is a simple process. A PowerShell script performs the following tasks: +Installing Connected Cache 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. +- Enables the firewall and opens ports 80 and 22 for inbound and outbound traffic. Port 80 is used by Connected Cache, 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. +- Deploys the Connected Cache container to server. #### Run the installer @@ -145,9 +145,9 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p - **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. + - **resourceDeploymentForConnectedCache.ps1**: Creates Azure cloud resources required to support Connected Cache control plane. + - **mccdeployment.json**: Deployment manifest used by IoT Edge to deploy the Connected Cache container and configure settings on the container, such as cache drive location sizes. + - **updatemcc.ps1**: The update script used to upgrade Connected Cache 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. @@ -159,7 +159,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p > > 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. **If you're installing Connected Cache on a local virtual machine**, turn the virtual machine **off** while you enable nested virtualization and MAC spoofing. 1. Enable nested virtualization: ```powershell @@ -215,7 +215,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p :::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. + > Choosing a dynamic IP address might assign a different IP address when the Connected Cache restarts. A static IP address is recommended so you don't have to change this value in your management solution when Connected Cache 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. @@ -239,7 +239,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p :::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"::: - -# Uninstall MCC +# Uninstall Microsoft Connected Cache -Contact the MCC Team before uninstalling to let us know if you're facing issues. +Contact the Connected Cache Team before uninstalling to let us know if you're facing issues. This script removes the following items: @@ -47,9 +47,9 @@ This script removes the following items: 1. IoT Edge 1. Edge Agent 1. Edge Hub -1. MCC +1. Connected Cache 1. Moby CLI 1. Moby Engine -To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT +To delete Connected Cache, go to Control Panel \> Uninstall a program \> Select Azure IoT Edge LTS \> Uninstall From 260b66f28acecf28d9df7ce7e6327a911e32a99e Mon Sep 17 00:00:00 2001 From: vboyev-MSFT Date: Thu, 24 Oct 2024 13:59:45 -0500 Subject: [PATCH 05/11] Update appcontrol.md Clarified language. Thought I submitted this earlier but cant find the pull request --- .../application-control/app-control-for-business/appcontrol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/application-security/application-control/app-control-for-business/appcontrol.md b/windows/security/application-security/application-control/app-control-for-business/appcontrol.md index 561da483b6e..6c4ee67b41d 100644 --- a/windows/security/application-security/application-control/app-control-for-business/appcontrol.md +++ b/windows/security/application-security/application-control/app-control-for-business/appcontrol.md @@ -30,7 +30,7 @@ Windows 10 and Windows 11 include two technologies that can be used for applicat ## App Control and Smart App Control -Starting in Windows 11 version 22H2, [Smart App Control](https://support.microsoft.com/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003) provides application control for consumers. Smart App Control is based on App Control, allowing enterprise customers to create a policy that offers the same security and compatibility with the ability to customize it to run line-of-business (LOB) apps. To make it easier to implement this policy, an [example policy](design/example-appcontrol-base-policies.md) is provided. The example policy includes **Enabled:Conditional Windows Lockdown Policy** option that isn't supported for App Control enterprise policies. This rule must be removed before you use the example policy. To use this example policy as a starting point for creating your own policy, see [Create a custom base policy using an example App Control base policy](design/create-appcontrol-policy-for-lightly-managed-devices.md#create-a-custom-base-policy-using-an-example-app-control-base-policy). +Starting in Windows 11 version 22H2, [Smart App Control](https://support.microsoft.com/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003) provides application control for consumers. Smart App Control is based on App Control. App control enables enterprise customers to create a policy that offers the same security and compatibility as Smart App Control with the capability to customize policeis to run line-of-business (LOB) apps. To make it easier to implement policy, an [example policy](design/example-appcontrol-base-policies.md) is provided. The example policy includes **Enabled:Conditional Windows Lockdown Policy** option that isn't supported for App Control enterprise policies. This rule must be removed before you use the example policy. To use this example policy as a starting point for creating your own policy, see [Create a custom base policy using an example App Control base policy](design/create-appcontrol-policy-for-lightly-managed-devices.md#create-a-custom-base-policy-using-an-example-app-control-base-policy). Smart App Control is only available on clean installation of Windows 11 version 22H2 or later, and starts in evaluation mode. Smart App Control is automatically turned off for enterprise managed devices unless the user has turned it on first. To turn off Smart App Control across your organization's endpoints, you can set the **VerifiedAndReputablePolicyState** (DWORD) registry value under `HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy` as shown in the following table. After you change the registry value, you must either restart the device or use [CiTool.exe -r](operations/citool-commands.md#refresh-the-app-control-policies-on-the-system) for the change to take effect. From 48ed294f2e07ab2d6f635099af28df273c9a1115 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 24 Oct 2024 13:05:38 -0700 Subject: [PATCH 06/11] mcc-branding --- windows/deployment/do/TOC.yml | 12 +- .../do/mcc-isp-cache-node-configuration.md | 6 +- .../do/mcc-isp-create-provision-deploy.md | 18 +- windows/deployment/do/mcc-isp-faq.yml | 8 +- windows/deployment/do/mcc-isp-overview.md | 30 ++-- windows/deployment/do/mcc-isp-support.md | 6 +- windows/deployment/do/mcc-isp-update.md | 4 +- .../do/mcc-isp-verify-cache-node.md | 2 +- .../deployment/do/mcc-isp-vm-performance.md | 8 +- windows/deployment/do/mcc-isp.md | 154 +++++++++--------- .../do/waas-delivery-optimization-faq.yml | 8 +- .../do/waas-delivery-optimization-monitor.md | 4 +- 12 files changed, 130 insertions(+), 130 deletions(-) diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index fe1b2a0cf3b..a028e5929ce 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -33,21 +33,21 @@ items: - name: What is Microsoft Connected Cache? href: waas-microsoft-connected-cache.md - - name: MCC for Enterprise and Education + - name: Connected Cache for Enterprise and Education items: - - name: MCC for Enterprise and Education Overview + - name: Connected Cache 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 + - name: Update or uninstall Connected Cache href: mcc-enterprise-update-uninstall.md - name: Appendix href: mcc-enterprise-appendix.md - - name: MCC for ISPs + - name: Connected Cache for ISPs items: - - name: MCC for ISPs Overview + - name: Connected Cache for ISPs Overview href: mcc-isp-overview.md - name: How-to guides items: @@ -67,7 +67,7 @@ href: mcc-isp-vm-performance.md - name: Support and troubleshooting href: mcc-isp-support.md - - name: MCC for ISPs (early preview) + - name: Connected Cache for ISPs (early preview) href: mcc-isp.md - name: Endpoints for Microsoft Connected Cache content and services href: delivery-optimization-endpoints.md diff --git a/windows/deployment/do/mcc-isp-cache-node-configuration.md b/windows/deployment/do/mcc-isp-cache-node-configuration.md index 1b038f64049..807fdb43d0a 100644 --- a/windows/deployment/do/mcc-isp-cache-node-configuration.md +++ b/windows/deployment/do/mcc-isp-cache-node-configuration.md @@ -27,8 +27,8 @@ All cache node configuration takes place within Azure portal. This article outli | Field Name | Expected Value| Description | | -- | --- | --- | | **Cache node name** | Alphanumeric string that contains no spaces | The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later. | -| **Server IP address** | IPv4 address | IP address of your MCC server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. | -| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your MCC based on the specifications of your hardware. For example, 10,000 Mbps.| +| **Server IP address** | IPv4 address | IP address of your Microsoft Connected Cache server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. | +| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your Connected Cache based on the specifications of your hardware. For example, 10,000 Mbps.| | **Enable cache node** | Enable or Disable | You can choose to enable or disable a cache node at any time. | ## Storage @@ -42,6 +42,6 @@ All cache node configuration takes place within Azure portal. This article outli | Field Name | Expected Value| Description | | -- | --- | --- | -| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 | +| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the Connected Cache server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 | | **BGP - Neighbor ASN** | ASN | When configuring BGP, enter the ASN(s) of your neighbors that you want to establish. | | **BGP - Neighbor IP address** | IPv4 address | When configuring BGP, enter the IP address(es) of neighbors that you want to establish. | diff --git a/windows/deployment/do/mcc-isp-create-provision-deploy.md b/windows/deployment/do/mcc-isp-create-provision-deploy.md index 4b56a710bbd..fbe4478bf85 100644 --- a/windows/deployment/do/mcc-isp-create-provision-deploy.md +++ b/windows/deployment/do/mcc-isp-create-provision-deploy.md @@ -84,7 +84,7 @@ To set up and enable BGP routing for your cache node, follow the steps below: 1. Under **Routing information**, select the routing method you would like to use. For more information, see [Client routing](#client-routing). - If you choose **Manual routing**, enter your address range/CIDR blocks. - - If you choose **BGP routing**, enter the ASN and IP addresses of the neighborship. Use your ASN, the one used to sign up for MCC. MCC will be automatically assigned as the same ASN as the neighbor. + - If you choose **BGP routing**, enter the ASN and IP addresses of the neighborship. Use your ASN, the one used to sign up for Microsoft Connected Cache. Connected Cache will be automatically assigned as the same ASN as the neighbor. > [!NOTE] > **Prefix count** and **IP Space** will stop displaying `0` when BGP is successfully established. @@ -96,12 +96,12 @@ Once the user executes the cache server provisioning script, resources are creat #### IoT Edge -IoT Edge performs several functions important to manage MCC on your edge device: +IoT Edge performs several functions important to manage Connected Cache on your edge device: -1. Installs and updates MCC on your edge device. +1. Installs and updates Connected Cache 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. +1. Ensures that Connected Cache is always running. +1. Reports Connected Cache health and usage to the cloud for remote monitoring. #### Docker container engine @@ -121,7 +121,7 @@ There are five IDs that the device provisioning script takes as input in order t #### Provision your server > [!IMPORTANT] -> Have you correctly mounted your disk? Your MCC will not be successfully installed without this important step. Before provisioning your server, ensure your disk is correctly mounted by following the instructions here: [Attach a data disk to a Linux VM](/azure/virtual-machines/linux/attach-disk-portal#find-the-disk). +> Have you correctly mounted your disk? Your Connected Cache will not be successfully installed without this important step. Before provisioning your server, ensure your disk is correctly mounted by following the instructions here: [Attach a data disk to a Linux VM](/azure/virtual-machines/linux/attach-disk-portal#find-the-disk). :::image type="content" source="images/mcc-isp-deploy-cache-node-numbered.png" alt-text="Screenshot of the server provisioning tab within cache node configuration in Azure portal."::: @@ -145,8 +145,8 @@ There are five IDs that the device provisioning script takes as input in order t | Field Name | Expected Value| Description | |---|---|---| | **Cache node name** | Alphanumeric string that contains no spaces | The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and can't be changed later. | -| **Server IP address** | IPv4 address | IP address of your MCC server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. | -| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your MCC based on the specifications of your hardware. For example, 10,000 Mbps.| +| **Server IP address** | IPv4 address | IP address of your Connected Cache server. This address is used to route end-user devices in your network to the server for Microsoft content downloads. The IP address must be publicly accessible. | +| **Max allowable egress (Mbps)** | Integer in Mbps | The maximum egress (Mbps) of your Connected Cache based on the specifications of your hardware. For example, 10,000 Mbps.| | **Enable cache node** | Enable or Disable | You can choose to enable or disable a cache node at any time. | ### Storage fields @@ -164,6 +164,6 @@ There are five IDs that the device provisioning script takes as input in order t | Field Name | Expected Value| Description | |---|---|---| -| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the MCC server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 | +| **Manual routing - Address range/CIDR blocks** | IPv4 CIDR notation | The IP address range (CIDR blocks) that should be routed to the Connected Cache server as a comma separated list. For example: 2.21.234.0/24, 3.22.235.0/24, 4.23.236.0/24 | | **BGP - Neighbor ASN** | ASN | When configuring BGP, enter the ASN(s) of your neighbors that you want to establish. | | **BGP - Neighbor IP address** | IPv4 address | When configuring BGP, enter the IP address(es) of neighbors that you want to establish. | diff --git a/windows/deployment/do/mcc-isp-faq.yml b/windows/deployment/do/mcc-isp-faq.yml index d4b3478551d..a5c2e9f7826 100644 --- a/windows/deployment/do/mcc-isp-faq.yml +++ b/windows/deployment/do/mcc-isp-faq.yml @@ -28,7 +28,7 @@ sections: - question: What will Microsoft Connected Cache do for me? How will it impact our customers? answer: As an ISP, your network can benefit from reduced load on your backbone and improve customer download experience for supported Microsoft static content. It will also help you save on CDN costs. - question: I already peer with Microsoft(8075). What benefit will I receive by adding Microsoft Connected Cache to my network? - answer: MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing MCC. + answer: Microsoft Connected Cache complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing Connected Cache. - question: Is there a non-disclosure agreement to sign? answer: No, a non-disclosure agreement isn't required. - question: What are the prerequisites and hardware requirements? @@ -79,7 +79,7 @@ sections: - question: Is IPv6 supported? answer: No, we don't currently support IPV6. We plan to support it in the future. - question: Is Microsoft Connected Cache stable and reliable? - answer: We have already successfully onboarded ISPs in many countries and regions around the world and have received positive feedback! However, you can always start off with a portion of your CIDR blocks to test out the performance of MCC before expanding to more customers. + answer: We have already successfully onboarded ISPs in many countries and regions around the world and have received positive feedback! However, you can always start off with a portion of your CIDR blocks to test out the performance of Connected Cache before expanding to more customers. - question: How does Microsoft Connected Cache populate its content? answer: Microsoft Connected Cache is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There's no off-peak cache fill necessary. Microsoft Connected Cache will reach out to different CDN providers just like a client device would. The traffic flow from Microsoft Connected Cache will vary depending on how you currently transit to each of these CDN providers. The content can come from third party CDNs or from AFD. - question: What CDNs does Microsoft Connected Cache pull content from? @@ -99,7 +99,7 @@ sections: answer: First, check that the email under the NOC role is correct in your PeeringDB page. If the email associated with NOC role is correct, search for an email from the sender "microsoft-noreply@microsoft.com" with the email subject - "Here's your Microsoft Connected Cache verification code" in your Spam folders. Still can't find it? Ensure that your email admin rules allow emails from the sender `microsoft-noreply@microsoft.com`. - question: I noticed I can set up BGP for routing. How does BGP routing work for Microsoft Connected Cache? answer: BGP routing can be set up as an automatic method of routing traffic. To learn more about how BGP is used with Microsoft Connected Cache, see [BGP Routing](mcc-isp-create-provision-deploy.md#bgp-routing). - - question: I have an active MCC, but I'm noticing I hit the message limit for my IoT Hub each day. Does this affect my MCC performance and should I be concerned? - answer: Even when the quota of 8k messages is hit, the MCC functionality isn't affected. Your client devices continue to download content as normal. You also won't be charged above the 8k message limit, so you don't need to worry at all about getting a paid plan. MCC will always be a free service. So if functionality isn't impacted, what is? Instead, messages about the configuration or edge deployment would be impacted. This means that if there was a request to update your MCC and the daily quota was reached, your MCC might not update. In that case, you would just need to wait for the next day to update. This is only a limitation of the early preview and isn't an issue during public preview. + - question: I have an active Connected Cache, but I'm noticing I hit the message limit for my IoT Hub each day. Does this affect my Connected Cache performance and should I be concerned? + answer: Even when the quota of 8k messages is hit, the Connected Cache functionality isn't affected. Your client devices continue to download content as normal. You also won't be charged above the 8k message limit, so you don't need to worry at all about getting a paid plan. Connected Cache will always be a free service. So if functionality isn't impacted, what is? Instead, messages about the configuration or edge deployment would be impacted. This means that if there was a request to update your Connected Cache and the daily quota was reached, your Connected Cache might not update. In that case, you would just need to wait for the next day to update. This is only a limitation of the early preview and isn't an issue during public preview. - 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, visit [Troubleshooting Issues for Microsoft Connected Cache for ISP (public preview)](mcc-isp-support.md). diff --git a/windows/deployment/do/mcc-isp-overview.md b/windows/deployment/do/mcc-isp-overview.md index 41ecaaaf1c1..456a2aebdc8 100644 --- a/windows/deployment/do/mcc-isp-overview.md +++ b/windows/deployment/do/mcc-isp-overview.md @@ -1,6 +1,6 @@ --- -title: MCC for ISPs Overview -description: Overview of Microsoft Connected Cache for ISPs. Learn about how MCC works, supported scenarios, and supported content. +title: Microsoft Connected Cache for ISPs Overview +description: Overview of Microsoft Connected Cache for ISPs. Learn about how Connected Cache works, supported scenarios, and supported content. ms.service: windows-client ms.subservice: itpro-updates ms.topic: overview @@ -18,7 +18,7 @@ ms.date: 05/23/2024 # Microsoft Connected Cache for ISPs overview -Microsoft Connected Cache (MCC) for Internet Service Providers (preview) is a free software-only caching solution that delivers Microsoft content. MCC can be deployed free of charge 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. +Microsoft Connected Cache for Internet Service Providers (preview) is a free software-only caching solution that delivers Microsoft content. Connected Cache can be deployed free of charge to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, Connected Cache 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. ## Supported scenarios @@ -41,40 +41,40 @@ For the full list of content endpoints that Microsoft Connected Cache for ISPs s ### Are you already peering with 8075? -MCC complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing MCC. +Connected Cache complements peering by offloading static content that is served off of multiple CDNs such as Akamai, Lumen, Edgecast. Static content such as OS updates, Apps, Software installs etc. can't be served via 8075. So, even if you're peering with Microsoft, you can benefit from installing Connected Cache. :::image type="content" source="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png" alt-text="Chart containing Peering vs Cache Content Traffic." lightbox="./media/mcc-isp-overview/mcc-isp-peeringvsmcc.png"::: -## How MCC works +## How Connected Cache works :::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png"::: -The following steps describe how MCC is provisioned and used: +The following steps describe how Connected Cache is provisioned and used: -1. The Azure portal is used to create and manage MCC nodes. +1. The Azure portal is used to create and manage Connected Cache nodes. -1. A shell script is used to provision the server and deploy the MCC application. +1. A shell script is used to provision the server and deploy the Connected Cache application. -1. A combination of the Azure portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the MCC server. +1. A combination of the Azure portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the Connected Cache server. - The publicly accessible IPv4 address of the server is configured on the portal. - - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node. + - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the Connected Cache node. - - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the MCC node. + - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the Connected Cache node. > [!NOTE] > Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error. -1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding MCC node. +1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding Connected Cache node. -1. Microsoft clients make the range requests for content from the MCC node. +1. Microsoft clients make the range requests for content from the Connected Cache node. -1. An MCC node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client. +1. An Connected Cache node gets 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 be served from cache. -1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers. +1. If the Connected Cache node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers. ### Hardware recommendation diff --git a/windows/deployment/do/mcc-isp-support.md b/windows/deployment/do/mcc-isp-support.md index ba0eda79c2d..dbced5230c6 100644 --- a/windows/deployment/do/mcc-isp-support.md +++ b/windows/deployment/do/mcc-isp-support.md @@ -36,7 +36,7 @@ During sign-up, a verification code is sent to your NOC email address present in #### Unable to re-sign up -Delete any MCC resource that you're using before you resign up for the service. Deleting any existing MCC resource unlocks your ASN, which allows you to successfully sign up. +Delete any Microsoft Connected Cache resource that you're using before you resign up for the service. Deleting any existing Connected Cache resource unlocks your ASN, which allows you to successfully sign up. ### Cache Node Errors @@ -100,9 +100,9 @@ iotedge check -verbose ## Diagnose and Solve Problems -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. +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 Connected Cache 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. +You can find **Diagnose and solve problems** on the left pane within your Connected Cache resource. :::image type="content" source="images/mcc-isp-diagnose-solve.png" alt-text="A screenshot of Azure portal showing the Diagnose and Solve problems tab on the left hand pane of Azure portal." lightbox="images/mcc-isp-diagnose-solve.png"::: diff --git a/windows/deployment/do/mcc-isp-update.md b/windows/deployment/do/mcc-isp-update.md index e5140cb3159..58f6d51180e 100644 --- a/windows/deployment/do/mcc-isp-update.md +++ b/windows/deployment/do/mcc-isp-update.md @@ -33,7 +33,7 @@ To view which version your cache nodes are currently on, navigate to the **Cache There are two main steps required to uninstall your cache node: 1. Remove your cache node from Azure portal -1. Run the uninstall script to cleanly remove MCC from your server +1. Run the uninstall script to cleanly remove Microsoft Connected Cache from your server You must complete both steps to ensure a clean uninstall of your cache node. @@ -50,7 +50,7 @@ The **uninstallmcc.sh** script removes the following components: - IoT Edge - Edge Agent - Edge Hub -- MCC +- Connected Cache - Moby CLI - Moby engine diff --git a/windows/deployment/do/mcc-isp-verify-cache-node.md b/windows/deployment/do/mcc-isp-verify-cache-node.md index c43bf3738f7..1eed1cb75c3 100644 --- a/windows/deployment/do/mcc-isp-verify-cache-node.md +++ b/windows/deployment/do/mcc-isp-verify-cache-node.md @@ -49,7 +49,7 @@ Sign into the [Azure portal](https://www.portal.azure.com) and navigate to the * It can take a few minutes for the container to deploy after you've saved the configuration. -To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace `` with the IP address of the cache server. +To validate a properly functioning Microsoft Connected Cache, run the following command in the terminal of the cache server or any device in the network. Replace `` with the IP address of the cache server. ```bash wget http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com diff --git a/windows/deployment/do/mcc-isp-vm-performance.md b/windows/deployment/do/mcc-isp-vm-performance.md index 5fafc85e899..f3d3079534d 100644 --- a/windows/deployment/do/mcc-isp-vm-performance.md +++ b/windows/deployment/do/mcc-isp-vm-performance.md @@ -25,7 +25,7 @@ The Microsoft Connected Cache module is optimized for Ubuntu 20.04 LTS. Install #### NIC requirements -- Multiple NICs on a single MCC instance are supported using a *link aggregated* configuration. +- Multiple NICs on a single Microsoft Connected Cache instance are supported using a *link aggregated* configuration. - 10 Gbps NIC is the minimum speed recommended, but any NIC is supported. #### Drive performance @@ -55,9 +55,9 @@ Change the following settings to maximize the egress in virtual environments: 1. Enable **Single Root I/O Virtualization (SR-IOV)** in the following three locations: - - The BIOS of the MCC virtual machine - - The network card properties of the MCC virtual machine - - The hypervisor for the MCC virtual machine + - The BIOS of the Connected Cache virtual machine + - The network card properties of the Connected Cache virtual machine + - The hypervisor for the Connected Cache virtual machine Microsoft has found these settings to double egress when using a Microsoft Hyper-V deployment. diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md index ff0a665d2e9..4344f22ca45 100644 --- a/windows/deployment/do/mcc-isp.md +++ b/windows/deployment/do/mcc-isp.md @@ -1,6 +1,6 @@ --- title: Microsoft Connected Cache for ISPs -description: This article contains details about the early preview for Microsoft Connected Cache (MCC) for Internet Service Providers (ISPs). +description: This article contains details about the early preview for Microsoft Connected Cache for Internet Service Providers (ISPs). ms.service: windows-client ms.subservice: itpro-updates ms.topic: how-to @@ -24,57 +24,57 @@ appliesto: ## Overview -Microsoft Connected Cache (MCC) preview is a software-only caching solution that delivers Microsoft content within operator networks. MCC can be deployed to as many physical servers or VMs as needed and is managed from a cloud portal. Microsoft cloud services handle routing of consumer devices to the cache server for content downloads. +Microsoft Connected Cache preview is a software-only caching solution that delivers Microsoft content within operator networks. Connected Cache can be deployed to as many physical servers or VMs as needed and is managed from a cloud portal. Microsoft cloud services handle routing of consumer devices to the cache server for content downloads. Microsoft Connected Cache is a hybrid application, in that it's a mix of on-premises and cloud resources. It's composed of a Docker-compatible Linux container deployed to your server and a cloud management portal. Microsoft chose Azure IoT Edge as a secure and reliable control plane. For more information on IoT Edge, see the [Appendix](#appendix). Even though your scenario isn't related to IoT, Azure IoT Edge is our secure Linux container deployment and management infrastructure. -## How MCC works +## How Connected Cache works :::image type="content" source="./images/mcc-isp-diagram.png" alt-text="Data flow diagram of how Microsoft Connected Cache works." lightbox="./images/mcc-isp-diagram.png"::: -The following steps describe how MCC is provisioned and used: +The following steps describe how Connected Cache is provisioned and used: -1. The Azure Management Portal is used to create and manage MCC nodes. +1. The Azure Management Portal is used to create and manage Connected Cache nodes. -1. A shell script is used to provision the server and deploy the MCC application. +1. A shell script is used to provision the server and deploy the Connected Cache application. -1. A combination of the Azure Management Portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the MCC server. +1. A combination of the Azure Management Portal and shell script is used to configure Microsoft Delivery Optimization Services to route traffic to the Connected Cache server. - The publicly accessible IPv4 address of the server is configured on the portal. - - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the MCC node. + - **Manual Routing:** Providing the CIDR blocks that represent the client IP address space, which should be routed to the Connected Cache node. - - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the MCC node. + - **BGP Routing:** A shell script is used to initiate a peering session with a router in the operator network, and the operator initiates a session with the Connected Cache node. > [!NOTE] > Only IPv4 addresses are supported at this time. Entering IPv6 addresses will result in an error. -1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding MCC node. +1. Microsoft end-user devices (clients) periodically connect with Microsoft Delivery Optimization Services, and the services match the IP address of the client with the IP address of the corresponding Connected Cache node. -1. Microsoft clients make the range requests for content from the MCC node. +1. Microsoft clients make the range requests for content from the Connected Cache node. -1. An MCC node gets content from the CDN, seeds its local cache stored on disk, and delivers the content to the client. +1. A Connected Cache node gets 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 be served from cache. -1. If the MCC node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers. +1. If the Connected Cache node is unavailable, the client gets content from the CDN to ensure uninterrupted service for your subscribers. -## ISP requirements for MCC +## ISP requirements for Connected Cache Microsoft Connected Cache for Internet Service Providers is now in Public Preview! To get started, visit [Azure portal](https://www.portal.azure.com) to sign up for Microsoft Connected Cache for Internet Service Providers. Please see [Operator sign up and service onboarding for Microsoft Connected Cache](mcc-isp-signup.md) for more information on the requirements for sign up and onboarding. - - -## Verify properly functioning MCC server +## Verify properly functioning Connected Cache server ### Verify client side @@ -421,7 +421,7 @@ For example, this command provides the current status of the starting and stoppi It can take a few minutes for the container to deploy. -To validate a properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace `` with the IP address of the cache server. +To validate a properly functioning Connected Cache, run the following command in the terminal of the cache server or any device in the network. Replace `` with the IP address of the cache server. ```bash wget http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com @@ -511,11 +511,11 @@ To configure the device to work with your DNS, use the following steps: +1. [Email the Connected Cache team](mailto:msconnectedcache@microsoft.com?subject=Debugging%20Support%20Request%20for%20MCC) and attach this tar file, asking for debugging support. Screenshots of the error along with any other warnings you saw will be helpful during the debugging process. --> - - +1. To finish configuring your Connected Cache with BGP routing, continue from Step 10 of [Steps to Install Connected Cache](#steps-to-install-mcc). --> -## Uninstalling MCC +## Uninstalling Connected Cache -In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls MCC and all the related components. Before you run this script, contact the MCC team. Only run it if you're facing issues with MCC installation. +In the installer zip file, you'll find the file **uninstallmcc.sh**. This script uninstalls Connected Cache and all the related components. Before you run this script, contact the Connected Cache team. Only run it if you're facing issues with Connected Cache installation. > [!WARNING] > Be cautious before running this script. It will also erase existing IoT workflows in this VM. @@ -571,7 +571,7 @@ The **uninstallmcc.sh** script removes the following components: - IoT Edge - Edge Agent - Edge Hub -- MCC +- Connected Cache - Moby CLI - Moby engine @@ -589,25 +589,25 @@ sudo ./uninstallmcc.sh [!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)] -### Performance of MCC in virtual environments +### Performance of Connected Cache in virtual environments In virtual environments, the cache server egress peaks at around 1.1 Gbps. If you want to maximize the egress in virtual environments, it's critical to change the following two settings: 1. Enable **SR-IOV** in the following three locations: - - The BIOS of the MCC VM - - The MCC VM's network card properties - - The hypervisor for the MCC VM + - The BIOS of the Connected Cache VM + - The Connected Cache VM's network card properties + - The hypervisor for the Connected Cache VM Microsoft has found these settings to double egress when using a Microsoft Hyper-V deployment. 2. Enable "high performance" in the BIOS instead of energy savings. Microsoft has found this setting nearly doubled egress in a Microsoft Hyper-V deployment. -### Grant other users access to manage your MCC +### Grant other users access to manage your Connected Cache More users can be given access to manage Microsoft Connected Cache, even if they don't have an Azure account. Once you've created the first cache node in the portal, you can add other users as **Owners** of the Microsoft Connected Cache resource group and the Microsoft Connected Cache resource. -For more information on how to add other users as an owner, see [Grant a user access to Azure resources using the Azure portal](/azure/role-based-access-control/quickstart-assign-role-user-portal). Make sure to do this action for both the *MCC resource* and *MCC resource group*. +For more information on how to add other users as an owner, see [Grant a user access to Azure resources using the Azure portal](/azure/role-based-access-control/quickstart-assign-role-user-portal). Make sure to do this action for both the *Connected Cache resource* and *Connected Cache resource group*. ### Setting up a VM on Windows Server @@ -708,7 +708,7 @@ You can use hardware that will natively run Ubuntu 20.04 LTS, or you can run an > > :::image type="content" source="./images/mcc-isp-ubuntu-upgrade.png" alt-text="Screenshot of the Ubuntu install's Upgrade Available prompt with Don't Upgrade selected."::: -Your Ubuntu VM is now ready to install MCC. +Your Ubuntu VM is now ready to install Connected Cache. ### IoT Edge runtime diff --git a/windows/deployment/do/waas-delivery-optimization-faq.yml b/windows/deployment/do/waas-delivery-optimization-faq.yml index cda14c3e5eb..34e50205727 100644 --- a/windows/deployment/do/waas-delivery-optimization-faq.yml +++ b/windows/deployment/do/waas-delivery-optimization-faq.yml @@ -113,8 +113,8 @@ sections: For more information, see [Endpoints for Delivery Optimization and Microsoft Connected Cache](../do/delivery-optimization-endpoints.md) for a list of all content endpoints needed. - question: My firewall requires IP addresses and can't process FQDNs. How do I configure it to download content with Delivery Optimization? answer: | - Microsoft content, such as Windows updates, are hosted and delivered globally via Content Delivery Networks (CDNs) and [Microsoft Connected Cache](waas-microsoft-connected-cache.md) (MCC) servers, which are hosted within Internet Service Provider (ISP) networks. - The network of CDNs and MCCs allows Microsoft to reach the scale required to meet the demand of the Windows user base. Given this delivery infrastructure changes dynamically, providing an exhaustive list of IPs and keeping it up to date isn't feasible. + Microsoft content, such as Windows updates, are hosted and delivered globally via Content Delivery Networks (CDNs) and [Microsoft Connected Cache](waas-microsoft-connected-cache.md) servers, which are hosted within Internet Service Provider (ISP) networks. + The network of CDNs and Microsoft Connected Caches allows Microsoft to reach the scale required to meet the demand of the Windows user base. Given this delivery infrastructure changes dynamically, providing an exhaustive list of IPs and keeping it up to date isn't feasible. - question: What is the recommended configuration for Delivery Optimization used with cloud proxies? answer: | The recommended configuration for Delivery Optimization peer-to-peer to work most efficiently along with cloud proxy solutions (for example, Zscaler) is to allow traffic to the Delivery Optimization services to go directly to the internet and not through the cloud proxy. @@ -131,8 +131,8 @@ sections: 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 + When Delivery Optimization client is configured to use peers and Microsoft Connected Cache, the client connects to both Connected Cache 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 Connected Cache) 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: | diff --git a/windows/deployment/do/waas-delivery-optimization-monitor.md b/windows/deployment/do/waas-delivery-optimization-monitor.md index ed6710932be..c8330f03849 100644 --- a/windows/deployment/do/waas-delivery-optimization-monitor.md +++ b/windows/deployment/do/waas-delivery-optimization-monitor.md @@ -24,7 +24,7 @@ To monitor Delivery Optimization, you can use either the Windows Update for Busi ## Monitor with Windows Update for Business Delivery Optimization report -Windows Update for Business Delivery Optimization Report provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer, Microsoft Connected Cache (MCC), HTTP source/CDN distribution over the past 28 days. +Windows Update for Business Delivery Optimization Report provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer, Microsoft Connected Cache, HTTP source/CDN distribution over the past 28 days. :::image type="content" source="../update/media/wufb-do-overview.png" alt-text="This screenshot shows the Windows Update for Business report, Delivery Optimization status in Update Compliance." lightbox= "../update/media/wufb-do-overview.png"::: @@ -49,7 +49,7 @@ For details, see [Windows Update for Business Delivery Optimization Report](/win | BytesFromHTTP | Total number of bytes received over HTTP. This metric represents all HTTP sources, **which includes BytesFromCacheServer** | | Status | Current state of the operation. Possible values are: **Downloading** (download in progress); **Complete** (download completed, but isn't uploading yet); **Caching** (download completed successfully and is ready to upload or uploading); **Paused** (download/upload paused by caller) | | Priority | Priority of the download; values are **foreground** or **background** | -| BytesFromCacheServer | Total number of bytes received from cache server (MCC) | +| BytesFromCacheServer | Total number of bytes received from cache server (Connected Cache) | | BytesFromLanPeers | Total number of bytes received from peers found on the LAN | | BytesFromGroupPeers | Total number of bytes received from peers found in the group. (Note: Group mode is LAN + Group. If peers are found on the LAN, those bytes are registered in 'BytesFromLANPeers'.) | | BytesFromInternetPeers | Total number of bytes received from internet peers | From d88020638c08889c1ba43e57c6f73b6aff0be155 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 24 Oct 2024 13:13:34 -0700 Subject: [PATCH 07/11] mcc-branding --- .../do/images/elixir_ux/readme-elixir-ux-files.md | 2 +- .../deployment/do/includes/get-azure-subscription.md | 2 +- .../do/waas-delivery-optimization-reference.md | 6 +++--- windows/deployment/do/waas-delivery-optimization.md | 8 ++++---- .../deployment/do/waas-microsoft-connected-cache.md | 8 ++++---- windows/deployment/do/whats-new-do.md | 8 ++++---- windows/deployment/update/wufb-reports-do.md | 10 +++++----- .../update/wufb-reports-schema-ucdoaggregatedstatus.md | 2 +- .../update/wufb-reports-schema-ucdostatus.md | 4 ++-- windows/deployment/update/wufb-reports-workbook.md | 4 ++-- 10 files changed, 27 insertions(+), 27 deletions(-) diff --git a/windows/deployment/do/images/elixir_ux/readme-elixir-ux-files.md b/windows/deployment/do/images/elixir_ux/readme-elixir-ux-files.md index 8b132e7d769..4bf73fa9c9a 100644 --- a/windows/deployment/do/images/elixir_ux/readme-elixir-ux-files.md +++ b/windows/deployment/do/images/elixir_ux/readme-elixir-ux-files.md @@ -25,4 +25,4 @@ This file contains the images that are included in this GitHub repository that a :::image type="content" source="ux-iot-edge-list.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing all three containers running successfully."::: -:::image type="content" source="ux-mcc-failed.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing the MCC container in a failure state."::: \ No newline at end of file +:::image type="content" source="ux-mcc-failed.png" alt-text="A screenshot of the terminal after the command 'iotedge list', showing the Microsoft Connected Cache container in a failure state."::: \ No newline at end of file diff --git a/windows/deployment/do/includes/get-azure-subscription.md b/windows/deployment/do/includes/get-azure-subscription.md index 5e0061e00b4..0be764aea75 100644 --- a/windows/deployment/do/includes/get-azure-subscription.md +++ b/windows/deployment/do/includes/get-azure-subscription.md @@ -14,6 +14,6 @@ ms.localizationpriority: medium 1. Sign in to the [Azure portal](https://portal.azure.com). 1. Select **Subscriptions**. If you don't see **Subscriptions**, type **Subscriptions** in the search bar. As you begin typing, the list filters based on your input. 1. If you already have an Azure Subscription, skip to step 5. If you don't have an Azure Subscription, select **+ Add** on the top left. -1. Select the **Pay-As-You-Go** subscription. You'll be asked to enter credit card information, but you'll not be charged for using the MCC service. +1. Select the **Pay-As-You-Go** subscription. You'll be asked to enter credit card information, but you'll not be charged for using the Microsoft Connected Cache service. 1. On the **Subscriptions** page, you'll find details about your current subscription. Select the subscription name. 1. After you select the subscription name, you'll find the subscription ID in the **Overview** tab. Select the **Copy to clipboard** icon next to your Subscription ID to copy the value. diff --git a/windows/deployment/do/waas-delivery-optimization-reference.md b/windows/deployment/do/waas-delivery-optimization-reference.md index a8f8a4b5177..59d11c87f88 100644 --- a/windows/deployment/do/waas-delivery-optimization-reference.md +++ b/windows/deployment/do/waas-delivery-optimization-reference.md @@ -96,19 +96,19 @@ More options available that control the impact Delivery Optimization has on your #### Policies to prioritize the use of peer-to-peer and cache server sources -When Delivery Optimization client is configured to use peers and Microsoft Connected Cache (MCC), to achieve the best possible content delivery experience, the client connects to both MCC and peers in parallel. If the desired content can't be obtained from MCC or peers, Delivery Optimization will automatically fall back to the HTTP source to get the requested content. There are four settings that allow you to prioritize peer-to-peer or MCC sources by delaying the immediate fallback to HTTP source, which is the default behavior. +When Delivery Optimization client is configured to use peers and Microsoft Connected Cache, to achieve the best possible content delivery experience, the client connects to both Connected Cache and peers in parallel. If the desired content can't be obtained from Connected Cache or peers, Delivery Optimization will automatically fall back to the HTTP source to get the requested content. There are four settings that allow you to prioritize peer-to-peer or Connected Cache sources by delaying the immediate fallback to HTTP source, which is the default behavior. ##### Peer-to-peer delay fallback settings - [Delay foreground download from HTTP (in secs)](#delay-foreground-download-from-http-in-secs) allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use P2P. - [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 P2P. -##### Microsoft Connected Cache (MCC) delay fallback settings +##### Microsoft Connected Cache 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 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. +**If both peer-to-peer and Connected Cache 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 Connected Cache cache server. #### System resource usage diff --git a/windows/deployment/do/waas-delivery-optimization.md b/windows/deployment/do/waas-delivery-optimization.md index 735d4b1965f..4d8f36f5267 100644 --- a/windows/deployment/do/waas-delivery-optimization.md +++ b/windows/deployment/do/waas-delivery-optimization.md @@ -24,7 +24,7 @@ ms.date: 05/23/2024 Windows updates, upgrades, and applications can contain packages with large files. Downloading and distributing updates can consume quite a bit of network resources on the devices receiving them. Delivery Optimization is a reliable HTTP downloader with a cloud-managed solution that allows Windows devices to download those packages from alternate sources if desired (such as other devices on the network and/or a dedicated cache server) in addition to the traditional internet-based servers (referred to as 'HTTP sources' throughout Delivery Optimization documents). You can use Delivery Optimization to reduce bandwidth consumption by sharing the work of downloading these packages among multiple devices in your deployment however, the use of peer-to-peer is optional. -To use either the peer-to-peer functionality or the Microsoft Connected Cache features, devices must have access to the Internet and Delivery Optimization cloud services. When Delivery Optimization is configured to use peers and Microsoft Connected Cache (MCC), to achieve the best possible content delivery experience, the client connects to MCC and peers in parallel. If the desired content can't be obtained from MCC or peers, Delivery Optimization seamlessly falls back to the HTTP source to get the requested content. +To use either the peer-to-peer functionality or the Microsoft Connected Cache features, devices must have access to the Internet and Delivery Optimization cloud services. When Delivery Optimization is configured to use peers and Microsoft Connected Cache, to achieve the best possible content delivery experience, the client connects to Connected Cache and peers in parallel. If the desired content can't be obtained from Connected Cache or peers, Delivery Optimization seamlessly falls back to the HTTP source to get the requested content. You can use Delivery Optimization with Windows Update, Windows Server Update Services (WSUS), Microsoft Intune/Windows Update for Business, or Microsoft Configuration Manager (when installation of Express Updates is enabled). @@ -47,7 +47,7 @@ The following table lists the minimum Windows 10 version that supports Delivery #### Windows Client -| Windows Client | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) | +| Windows Client | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache | |------------------|---------------|----------------|----------|----------------| | Windows Update ([feature updates quality updates, language packs, drivers](../update/get-started-updates-channels-tools.md#types-of-updates)) | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | | Windows 10/11 UWP Store apps | Windows 10 1511, Windows 11 | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | @@ -66,14 +66,14 @@ The following table lists the minimum Windows 10 version that supports Delivery #### Windows Server -| Windows Server | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) | +| Windows Server | Minimum Windows version | HTTP Downloader | Peer to Peer | Microsoft Connected Cache | |----------------|--------------------------|----------------|----------|----------------| | Windows Update | Windows Server 2019 (1809) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | | Edge Browser Updates | Windows Server 2019 (1809) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: | #### Linux (Public Preview) -| Linux ([Public Preview](https://github.com/microsoft/do-client)) | Linux versions | HTTP Downloader | Peer to Peer | Microsoft Connected Cache (MCC) | +| Linux ([Public Preview](https://github.com/microsoft/do-client)) | Linux versions | HTTP Downloader | Peer to Peer | Microsoft Connected Cache | |------------------------|----------------|-----------------|--------------|---------------| | Device Update for IoT Hub | Ubuntu 18.04, 20.04 / Debian 9, 10 | :heavy_check_mark: | | :heavy_check_mark: | > [!NOTE] diff --git a/windows/deployment/do/waas-microsoft-connected-cache.md b/windows/deployment/do/waas-microsoft-connected-cache.md index a1cd9a0ca89..5fe31397096 100644 --- a/windows/deployment/do/waas-microsoft-connected-cache.md +++ b/windows/deployment/do/waas-microsoft-connected-cache.md @@ -1,6 +1,6 @@ --- title: Microsoft Connected Cache overview -description: This article provides information about Microsoft Connected Cache (MCC), a software-only caching solution. +description: This article provides information about Microsoft Connected Cache, a software-only caching solution. ms.service: windows-client ms.subservice: itpro-updates ms.topic: overview @@ -33,16 +33,16 @@ Both products are created and managed in the cloud portal. > [!NOTE] > Microsoft Connected Cache for Internet Service Providers is now in public preview. To onboard, follow the instructions in the [Operator sign up and service onboarding](mcc-isp-signup.md) article. -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 Internet Service Providers is currently in preview. Connected Cache can be deployed to as many bare-metal servers or VMs as needed and is managed from a cloud portal. When deployed, Connected Cache 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) > [!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 (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 for Enterprise and Education (early preview) is a software-only caching solution that delivers Microsoft content within Enterprise and Education networks. Connected Cache 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 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) ## Next steps diff --git a/windows/deployment/do/whats-new-do.md b/windows/deployment/do/whats-new-do.md index 496d1240c1b..607817cbf77 100644 --- a/windows/deployment/do/whats-new-do.md +++ b/windows/deployment/do/whats-new-do.md @@ -22,9 +22,9 @@ This article contains information about what's new in Delivery Optimization, a p ## Microsoft Connected Cache (early preview) -Microsoft Connected Cache (MCC) is a software-only caching solution that delivers Microsoft content within Enterprise networks. MCC can be deployed to as many 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 is a software-only caching solution that delivers Microsoft content within Enterprise networks. Connected Cache can be deployed to as many 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. -For more information about MCC, see [Microsoft Connected Cache overview](waas-microsoft-connected-cache.md). +For more information about Connected Cache, see [Microsoft Connected Cache overview](waas-microsoft-connected-cache.md). There are two different versions: @@ -39,12 +39,12 @@ There are two different versions: - -HealthCheck: Provides an overall check of the device setup to ensure Delivery Optimization communication is possible on the device. - -P2P: Provides output specific to P2P settings, efficiency, and errors. -- -MCC: Provides output specific to MCC settings and verifies the client can access the cache server. +- -MCC: Provides output specific to Connected Cache settings and verifies the client can access the cache server. ### 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 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**. +- 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 Connected Cache 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). diff --git a/windows/deployment/update/wufb-reports-do.md b/windows/deployment/update/wufb-reports-do.md index c38fa013ab0..04291e8ef23 100644 --- a/windows/deployment/update/wufb-reports-do.md +++ b/windows/deployment/update/wufb-reports-do.md @@ -42,12 +42,12 @@ Windows Update for Business reports uses the following Delivery Optimization ter - HTTP Only (0) - Simple Mode (99) - Bypass (100), deprecated in Windows 11 -- **Bandwidth savings**: The percentage of bandwidth that was downloaded from alternate sources (Peers or Microsoft Connected Cache (MCC) out of the total amount of data downloaded. +- **Bandwidth savings**: The percentage of bandwidth that was downloaded from alternate sources (Peers or Microsoft Connected Cache) out of the total amount of data downloaded. - If bandwidth savings are <= 60%, a *Warning* icon is displayed - When bandwidth savings are <10%, an *Error* icon is displayed. - **Configurations**: Based on the DownloadMode configuration set via MDM, Group Policy, or end-user via the user interface. - **P2P Device Count**: The device count is the number of devices configured to use peering. -- **Microsoft Connected Cache (MCC)**: Microsoft Connected Cache is a software-only caching solution that delivers Microsoft content. For more information, see [Microsoft Connected Cache overview](../do/waas-microsoft-connected-cache.md). +- **Microsoft Connected Cache**: Microsoft Connected Cache is a software-only caching solution that delivers Microsoft content. For more information, see [Microsoft Connected Cache overview](../do/waas-microsoft-connected-cache.md). - **MCC Device Count**: The device count is the number of devices that have received bytes from the cache server, for supported content types. - **Total # of Devices**: The total number of devices with activity in last 28 days. - **LAN Bytes**: Bytes delivered from LAN peers. @@ -68,7 +68,7 @@ The calculated values used in the Delivery Optimization report are listed below. - [UCDOAggregatedStatus](wufb-reports-schema-ucdostatus.md) table - % P2P Efficiency = 100 * (BytesFromPeers + BytesFromGroupPeers) / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache) - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table -- % MCC Efficiency = 100 * BytesFromCache / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache) +- % Connected Cache Efficiency = 100 * BytesFromCache / (BytesFromPeers + BytesFromGroupPeers+BytesFromCDN+BytesFromCache) - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table **Bytes Calculations**: @@ -88,7 +88,7 @@ The calculated values used in the Delivery Optimization report are listed below. - Volume by P2P = BytesFromPeers + BytesFromGroupPeers - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table -- Volume by MCC = BytesFromCache +- Volume by Connected Cache = BytesFromCache - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table - Volume by CDN = BytesFrom CDN - [UCDOStatus](wufb-reports-schema-ucdostatus.md) table @@ -150,7 +150,7 @@ DeviceCount = count_distinct(GlobalDeviceId) by GroupID | top 10 by DeviceCount ### Delivery Optimization Supported Content Types -There are many Microsoft [content types](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) that are supported by Delivery Optimization. All of these content types show up in the 'Content Distribution' section in the Delivery Optimization report. See the [complete table](waas-delivery-optimization.md#windows-client) for P2P/MCC support types. +There are many Microsoft [content types](waas-delivery-optimization.md#types-of-download-content-supported-by-delivery-optimization) that are supported by Delivery Optimization. All of these content types show up in the 'Content Distribution' section in the Delivery Optimization report. See the [complete table](waas-delivery-optimization.md#windows-client) for P2P/Connected Cache support types. | Content Category | Content Types Included | | --- | --- | diff --git a/windows/deployment/update/wufb-reports-schema-ucdoaggregatedstatus.md b/windows/deployment/update/wufb-reports-schema-ucdoaggregatedstatus.md index 834c5a0b298..54de3d56475 100644 --- a/windows/deployment/update/wufb-reports-schema-ucdoaggregatedstatus.md +++ b/windows/deployment/update/wufb-reports-schema-ucdoaggregatedstatus.md @@ -27,7 +27,7 @@ UCDOAggregatedStatus is an aggregation of all individual UDDOStatus records acro | **AzureADDeviceId** | [string](/azure/kusto/query/scalar-data-types/string) | `71db1a1a-f1a6-4a25-b88f-79c2f513dae0` | Microsoft Entra Device ID | | **AzureADTenantId** | [string](/azure/kusto/query/scalar-data-types/string) | `69ca04b0-703d-4b3a-9184-c4e3c15d6f5e` | Microsoft Entra tenant ID | | **BWOptPercent28Days** | [real](/azure/kusto/query/scalar-data-types/real) | `10.61` | Bandwidth optimization (as a percentage of savings of total bandwidth otherwise incurred) for this device. A rolling 28-day basis.| -| **BytesFromCache** | [long](/azure/kusto/query/scalar-data-types/long) | `285212672` | Total number of bytes that were delivered from Microsoft Connected Cache (MCC). | +| **BytesFromCache** | [long](/azure/kusto/query/scalar-data-types/long) | `285212672` | Total number of bytes that were delivered from Microsoft Connected Cache. | | **BytesFromCDN** | [long](/azure/kusto/query/scalar-data-types/long) | `11463008693388` | Total number of bytes that were delivered from a Content Delivery Network (CDN). | | **BytesFromGroupPeers** | [long](/azure/kusto/query/scalar-data-types/long) | `30830657175` | Total number of bytes that were delivered from Group peers, sharing the same GroupId. | | **BytesFromIntPeers** | [long](/azure/kusto/query/scalar-data-types/long) | `285212672` | Total number of bytes that were delivered from Internet peers. | diff --git a/windows/deployment/update/wufb-reports-schema-ucdostatus.md b/windows/deployment/update/wufb-reports-schema-ucdostatus.md index f6ff2a21b39..ede39f076e6 100644 --- a/windows/deployment/update/wufb-reports-schema-ucdostatus.md +++ b/windows/deployment/update/wufb-reports-schema-ucdostatus.md @@ -1,7 +1,7 @@ --- title: UCDOStatus data schema titleSuffix: Windows Update for Business reports -description: UCDOStatus schema for Windows Update for Business reports. UCDOStatus provides information, for a single device, on its DO and MCC bandwidth utilization. +description: UCDOStatus schema for Windows Update for Business reports. UCDOStatus provides information, for a single device, on its DO and Microsoft Connected Cache bandwidth utilization. ms.service: windows-client ms.subservice: itpro-updates ms.topic: reference @@ -27,7 +27,7 @@ UCDOStatus provides information, for a single device, on its bandwidth utilizati | **AzureADTenantId** | [string](/azure/kusto/query/scalar-data-types/string) | `69ca04b0-703d-4b3a-9184-c4e3c15d6f5e` | Microsoft Entra tenant ID | | **BWOptPercent28Days** | [real](/azure/kusto/query/scalar-data-types/real) | `10.61` | Bandwidth optimization (as a percentage of savings of total bandwidth otherwise incurred) for this device. A rolling 28-day basis.| | **BWOptPercent7Days** | [real](/azure/kusto/query/scalar-data-types/real) | `10.61` | Bandwidth optimization (as a percentage of savings of total bandwidth otherwise incurred) for this device. A rolling 7-day basis.| -| **BytesFromCache** | [long](/azure/kusto/query/scalar-data-types/long) | `285212672` | Total number of bytes that were delivered from Microsoft Connected Cache (MCC). | +| **BytesFromCache** | [long](/azure/kusto/query/scalar-data-types/long) | `285212672` | Total number of bytes that were delivered from Microsoft Connected Cache. | | **BytesFromCDN** | [long](/azure/kusto/query/scalar-data-types/long) | `11463008693388` | Total number of bytes that were delivered from a Content Delivery Network (CDN). | | **BytesFromGroupPeers** | [long](/azure/kusto/query/scalar-data-types/long) | `30830657175` | Total number of bytes that were delivered from Group peers, sharing the same GroupId. | | **BytesFromIntPeers** | [long](/azure/kusto/query/scalar-data-types/long) | `285212672` | Total number of bytes that were delivered from Internet peers. | diff --git a/windows/deployment/update/wufb-reports-workbook.md b/windows/deployment/update/wufb-reports-workbook.md index 3d76c81910c..cefc7b717e9 100644 --- a/windows/deployment/update/wufb-reports-workbook.md +++ b/windows/deployment/update/wufb-reports-workbook.md @@ -180,8 +180,8 @@ The **Delivery Optimization** tab provides a summarized view of bandwidth effici At the top of the report, tiles display the following information: - Total bandwidth savings percentage -- The percentage of the saved bandwidth broken down by peer-to-peer and MCC -- Device counts showing percentages of bytes delivered between peer-to-peer and MCC +- The percentage of the saved bandwidth broken down by peer-to-peer and Microsoft Connected Cache +- Device counts showing percentages of bytes delivered between peer-to-peer and Connected Cache - The breakdown of total downloaded GBs. The Delivery Optimization tab is further divided into the following groups: From 44d613f10c56087097c3323f15bbae363aea2b2a Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 24 Oct 2024 13:53:54 -0700 Subject: [PATCH 08/11] mcc-branding --- windows/deployment/do/mcc-enterprise-deploy.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/deployment/do/mcc-enterprise-deploy.md b/windows/deployment/do/mcc-enterprise-deploy.md index a149ae9c8d0..7c54af2fc12 100644 --- a/windows/deployment/do/mcc-enterprise-deploy.md +++ b/windows/deployment/do/mcc-enterprise-deploy.md @@ -25,11 +25,11 @@ This article describes how to deploy a Microsoft Connected Cache for Enterprise To deploy Connected Cache to your server: 1. [Provide Microsoft with the Azure subscription ID](#provide-microsoft-with-the-azure-subscription-id) -1. [Create the Connected Cache Resource in Azure](#create-the-mcc-resource-in-azure) -1. [Create an Connected Cache Node](#create-an-mcc-node-in-azure) +1. [Create the Connected Cache Resource in Azure](#create-the-connected-cache-resource-in-azure) +1. [Create an Connected Cache Node](#create-an-connected-cache-node-in-azure) 1. [Edit Cache Node Information](#edit-cache-node-information) -1. [Install Connected Cache on a physical server or VM](#install-mcc-on-windows) -1. [Verify Connected Cache functionality](#verify-mcc-server-functionality) +1. [Install Connected Cache on a physical server or VM](#install-connected-cache-on-windows) +1. [Verify Connected Cache functionality](#verify-connected-cache-server-functionality) 1. [Review common Issues](#common-issues) if needed. ### Provide Microsoft with the Azure subscription ID @@ -112,7 +112,7 @@ Creating an Connected Cache node is a multi-step process and the first step is t If there are errors, the form will provide guidance on how to correct the errors. -Once the Connected Cache 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. +Once the Connected Cache 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-connected-cache-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."::: From e4ccb2a4c2baa5ead681ffbbbc3470bcffda3714 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Thu, 24 Oct 2024 14:01:45 -0700 Subject: [PATCH 09/11] mcc-branding --- .../mdm/policy-csp-deliveryoptimization.md | 2 +- windows/deployment/do/TOC.yml | 4 ++-- windows/deployment/do/mcc-enterprise-appendix.md | 2 +- windows/deployment/do/mcc-isp.md | 8 ++++---- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-deliveryoptimization.md b/windows/client-management/mdm/policy-csp-deliveryoptimization.md index 2d2289e9572..c058b8bccf0 100644 --- a/windows/client-management/mdm/policy-csp-deliveryoptimization.md +++ b/windows/client-management/mdm/policy-csp-deliveryoptimization.md @@ -164,7 +164,7 @@ One or more values can be added as either fully qualified domain names (FQDN) or > [!NOTE] -> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to an Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client. +> Clients don't talk to multiple Microsoft Connected Cache servers at the same time. If you configure a list of Connected Cache servers in this policy, the clients will round robin until they successfully connect to a Connected Cache server. The clients have no way to determine if the Connected Cache server has the content or not. If the Connected Cache server doesn't have the content, it caches the content as it is handing the content back to the client. diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index a028e5929ce..097f3c1c5c9 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -33,7 +33,7 @@ items: - name: What is Microsoft Connected Cache? href: waas-microsoft-connected-cache.md - - name: Connected Cache for Enterprise and Education + - name: Microsoft Connected Cache for Enterprise and Education items: - name: Connected Cache for Enterprise and Education Overview href: mcc-ent-edu-overview.md @@ -45,7 +45,7 @@ href: mcc-enterprise-update-uninstall.md - name: Appendix href: mcc-enterprise-appendix.md - - name: Connected Cache for ISPs + - name: Microsoft Connected Cache for ISPs items: - name: Connected Cache for ISPs Overview href: mcc-isp-overview.md diff --git a/windows/deployment/do/mcc-enterprise-appendix.md b/windows/deployment/do/mcc-enterprise-appendix.md index aab4bc87d2b..0a0239d6908 100644 --- a/windows/deployment/do/mcc-enterprise-appendix.md +++ b/windows/deployment/do/mcc-enterprise-appendix.md @@ -82,7 +82,7 @@ communication operations. The runtime performs several functions: 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 Connected Cache +## Routing local Windows clients to a Connected Cache ### Get the IP address of your Connected Cache using ifconfig diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md index 4344f22ca45..0d3426ca7a7 100644 --- a/windows/deployment/do/mcc-isp.md +++ b/windows/deployment/do/mcc-isp.md @@ -173,13 +173,13 @@ If you get the error message "Validation failed" in the Azure portal, it's likel If you get the error message "Could not create marketplace item" in the Azure portal, use the following steps to troubleshoot: -- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create an Connected Cache resource. +- Make sure that you've selected **Microsoft Connected Cache** and not *Connected Cache resources* while trying to create a Connected Cache resource. - Make sure that you're using the same subscription that you provided to Microsoft and you have privileges to create an Azure resource. - If the issue persists, clear your browser cache and start in a new window. -### Create an Connected Cache node in Azure +### Create a Connected Cache node in Azure 1. After you successfully create the resource, select **Go to resource**. @@ -347,7 +347,7 @@ Before you start, make sure that you have a data drive configured on your server - If this process is for your *first Connected Cache deployment*, enter `n`. - - If you already have an Connected Cache deployment, you can use an existing IoT Hub from your previous installation. Select `Y` to see your existing IoT Hubs. You can copy and paste the resulting IoT Hub name to continue. + - If you already have a Connected Cache deployment, you can use an existing IoT Hub from your previous installation. Select `Y` to see your existing IoT Hubs. You can copy and paste the resulting IoT Hub name to continue. :::image type="content" source="./images/mcc-isp-bash-iot-prompt.png" alt-text="Screenshot of the Bash script output with steps for existing IoT Hub." lightbox="./images/mcc-isp-bash-iot-prompt.png"::: @@ -550,7 +550,7 @@ sudo ./updatemcc.sh version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-u