mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-22 13:53:39 +00:00
formatting
This commit is contained in:
greg-lindsay
@ -4,24 +4,23 @@
|
||||
- name: Get started
|
||||
items:
|
||||
- name: What is Delivery Optimization?
|
||||
href: deploy-whats-new.md
|
||||
- name: What is Microsoft Connected Cache?
|
||||
href: windows-10-deployment-scenarios.md
|
||||
href: waas-delivery-optimization.md
|
||||
- name: What's new?
|
||||
href: update/waas-quick-start.md
|
||||
- name: 4
|
||||
href: update/waas-overview.md
|
||||
href: waas-delivery-optimization.md#new-in-windows-10-version-20h2-and-windows-11
|
||||
- name: What is Microsoft Connected Cache?
|
||||
href: waas-microsoft-connected-cache.md
|
||||
|
||||
|
||||
- name: Configure Delivery Optimization
|
||||
items:
|
||||
- name: Configure Windows Clients
|
||||
items:
|
||||
- name: Windows Delivery Optimization settings
|
||||
href: /windows/whats-new/windows-11-plan
|
||||
href: waas-delivery-optimization-setup.md#recommended-delivery-optimization-settings
|
||||
- name: Configure Microsoft Endpoint Manager
|
||||
items:
|
||||
- name: Configuration Manager settings
|
||||
href: /windows/whats-new/windows-11-plan
|
||||
- name: Delivery Optimization settings in Microsoft Intune
|
||||
href: /mem/intune/configuration/delivery-optimization-windows
|
||||
|
||||
- name: Microsoft Connected Cache
|
||||
items:
|
||||
@ -36,7 +35,11 @@
|
||||
|
||||
- name: Resources
|
||||
items:
|
||||
- name: Blog1
|
||||
href: /windows/whats-new/windows-11-plan
|
||||
- name: Blog2
|
||||
href: /windows/whats-new/windows-11-plan
|
||||
- name: Introducing Microsoft Connected Cache
|
||||
href: https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898
|
||||
- name: Delivery Optimization reference
|
||||
href: waas-delivery-optimization-reference.md
|
||||
- name: Delivery Optimization client-service communication
|
||||
href: delivery-optimization-workflow.md
|
||||
- name: Using a proxy with Delivery Optimization
|
||||
href: delivery-optimization-proxy.md
|
||||
@ -43,13 +43,13 @@ landingContent:
|
||||
- linkListType: how-to-guide
|
||||
links:
|
||||
- text: Delivery Optimization settings
|
||||
url: update/prepare-deploy-windows.md
|
||||
url: waas-delivery-optimization-setup.md#recommended-delivery-optimization-settings
|
||||
- text: Windows PowerShell for Delivery Optimization
|
||||
url: update/waas-manage-updates-wufb.md
|
||||
url: waas-delivery-optimization-setup.md#windows-powershell-cmdlets
|
||||
- text: Troubleshooting Delivery Optimization
|
||||
url: deploy-windows-cm/prepare-for-zero-touch-installation-of-windows-10-with-configuration-manager.md
|
||||
url: waas-delivery-optimization-setup.md#troubleshooting
|
||||
- text: Submit feedback
|
||||
url: update/waas-manage-updates-wufb.md
|
||||
url: https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app
|
||||
|
||||
# Card (optional)
|
||||
- title: Configure Delivery Optimization on Microsoft Endpoint Manager
|
||||
@ -58,6 +58,9 @@ landingContent:
|
||||
links:
|
||||
- text: Optimize Windows 10 or later update delivery with Configuration Manager
|
||||
url: /mem/configmgr/sum/deploy-use/optimize-windows-10-update-delivery#windows-delivery-optimization
|
||||
- text: Delivery Optimization settings in Microsoft Intune
|
||||
url: /mem/intune/configuration/delivery-optimization-windows
|
||||
|
||||
|
||||
# Card
|
||||
- title: Microsoft Connected Cache (MCC) for Enterprises
|
||||
|
||||
@ -48,14 +48,14 @@ For more details information on Azure IoT Edge, please see the [Azure IoT Edge d
|
||||
6. Subsequent requests from end-user devices for content will now come from cache.
|
||||
7. If the Microsoft Connected Cache node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Figure 1: Each number in the diagram corresponds to the steps above
|
||||
|
||||
## Enterprise Requirements for Microsoft Connected Cache
|
||||
|
||||
1. **Azure subscription** – Microsoft Connected Cache management portal is hosted within Azure and is used to create the [Connected Cache Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management.md) and IoT Hub resource – both are free services.
|
||||
1. **Azure subscription** – Microsoft Connected Cache management portal is hosted within Azure and is used to create the Connected Cache [Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management.md) and IoT Hub resource – both are free services.
|
||||
|
||||
We will use your Azure subscription ID to take care of some provisioning with our services, first, to give you access to the preview. The Microsoft Connected Cache server requirement for an Azure subscription will cost you nothing. If you do not have an Azure subscription already, you can create an Azure Pay-As-You-Go account which requires a credit card for verification purposes. Please visit Azure Free Account FAQ | Microsoft Azure for more information.
|
||||
Again, the resources used for the preview and in the future when this product is ready for production will be completely free to you, like other caching solutions.
|
||||
@ -95,34 +95,34 @@ The Microsoft Connected Cache Azure management portal is used to create and mana
|
||||
Use the following link and log in to Azure
|
||||
https://portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=Microsoft_ConnectedCache_EntHidden
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -287,7 +287,7 @@ This script will remove the following:
|
||||
7. Moby Engine
|
||||
To delete MCC, go to Control Panel > Uninstall a program > Select Azure IoT Edge LTS > Uninstall
|
||||
Appendix
|
||||
IoT Edge runtime The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices. The runtime sits on the IoT Edge device, and performs management and communication operations. The runtime performs several functions: • Installs and update workloads (Docker containers) on the device. • Maintains Azure IoT Edge security standards on the device. • Ensures that IoT Edge modules (Docker containers) are always running. • Reports module (Docker containers) health to the cloud for remote monitoring. • Manages communication between an IoT Edge device and the cloud. For more information on Azure IoT Edge, please see the Azure IoT Edge documentation https://docs.microsoft.com/en-us/azure/iot-edge/about-iot-edge.
|
||||
IoT Edge runtime The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices. The runtime sits on the IoT Edge device, and performs management and communication operations. The runtime performs several functions: • Installs and update workloads (Docker containers) on the device. • Maintains Azure IoT Edge security standards on the device. • Ensures that IoT Edge modules (Docker containers) are always running. • Reports module (Docker containers) health to the cloud for remote monitoring. • Manages communication between an IoT Edge device and the cloud. For more information on Azure IoT Edge, please see the Azure IoT Edge documentation https://docs.microsoft.com/azure/iot-edge/about-iot-edge.
|
||||
EFLOW
|
||||
What is Azure IoT Edge for Linux on Windows | Microsoft Docs
|
||||
Install Azure IoT Edge for Linux on Windows | Microsoft Docs
|
||||
|
||||
@ -41,7 +41,7 @@ Microsoft Connected Cache is a Hybrid (mix of on-prem and cloud resources) solut
|
||||
7. Subsequent requests from end-user devices for content will now come from cache.
|
||||
8. If the Microsoft Connected Cache node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
|
||||
|
||||
|
||||
|
||||
|
||||
## ISP Requirements for Microsoft Connected Cache
|
||||
|
||||
@ -247,7 +247,7 @@ Specifying any of the directories mentioned above will corrupt the VM and you wi
|
||||
10. If this is your first Microsoft Connected Cache deployment, select “n” when prompted for an IoT Hub. If this is not your first MCC deployment, you can use an existing IoT hub from your previous MCC installation. After selecting “Y”, we will display your existing IoT Hubs, you can copy and paste the resulting IoT Hub name to continue.
|
||||
11. If there are no errors go to the next step.
|
||||
• If there are errors, inspect the installer logs which are under /etc/mccresourcecreation/.
|
||||
• If there were follow the instructions to trouble shoot IoT edge https://docs.microsoft.com/en-us/azure/iot-edge/troubleshoot
|
||||
• If there were follow the instructions to trouble shoot IoT edge https://docs.microsoft.com/azure/iot-edge/troubleshoot
|
||||
Verify Proper Functioning Microsoft Connected Cache Server
|
||||
Verify Client Side
|
||||
Log into to the Connected Cache server or ssh and run this command from a terminal to see the running modules (containers).
|
||||
@ -338,7 +338,7 @@ b. Download Ubuntu Server
|
||||
13. Important: When prompted with the option to upgrade, decline.
|
||||
14.
|
||||
Your Ubuntu VM should now be ready for the next step: Install Microsoft Connected Cache on Your Server or VM
|
||||
IoT Edge runtime The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices. The runtime sits on the IoT Edge device, and performs management and communication operations. The runtime performs several functions: • Installs and update workloads (Docker containers) on the device. • Maintains Azure IoT Edge security standards on the device. • Ensures that IoT Edge modules (Docker containers) are always running. • Reports module (Docker containers) health to the cloud for remote monitoring. • Manages communication between an IoT Edge device and the cloud. For more information on Azure IoT Edge, please see the Azure IoT Edge documentation https://docs.microsoft.com/en-us/azure/iot-edge/about-iot-edge.
|
||||
IoT Edge runtime The Azure IoT Edge runtime enables custom and cloud logic on IoT Edge devices. The runtime sits on the IoT Edge device, and performs management and communication operations. The runtime performs several functions: • Installs and update workloads (Docker containers) on the device. • Maintains Azure IoT Edge security standards on the device. • Ensures that IoT Edge modules (Docker containers) are always running. • Reports module (Docker containers) health to the cloud for remote monitoring. • Manages communication between an IoT Edge device and the cloud. For more information on Azure IoT Edge, please see the Azure IoT Edge documentation https://docs.microsoft.com/azure/iot-edge/about-iot-edge.
|
||||
|
||||
|
||||
|
||||
|
||||
58
windows/deployment/do/waas-microsoft-connected-cache.md
Normal file
58
windows/deployment/do/waas-microsoft-connected-cache.md
Normal file
@ -0,0 +1,58 @@
|
||||
---
|
||||
title: What is Microsoft Connected Cache?
|
||||
manager: dougeby
|
||||
description: This article provides information about Microsoft Connected Cache, a software-only caching solution.
|
||||
keywords: oms, operations management suite, wdav, updates, downloads, log analytics
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: deploy
|
||||
audience: itpro
|
||||
author: carmenf
|
||||
ms.localizationpriority: medium
|
||||
ms.author: carmenf
|
||||
ms.collection:
|
||||
- M365-modern-desktop
|
||||
- m365initiative-coredeploy
|
||||
- highpri
|
||||
ms.topic: article
|
||||
ms.custom: seo-marvel-apr2020
|
||||
---
|
||||
|
||||
# What is Microsoft Connected Cache?
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
Microsoft Connected Cache (MCC) preview 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 hybrid (mix of on-prem 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. Microsoft Connected Cache will be a Linux IoT Edge module running on the Windows Host OS.
|
||||
|
||||
Even though your Microsoft Connected Cache scenario is not 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 Microsoft Connected Cache on your edge device:
|
||||
|
||||
1. Installs and updates Microsoft Connected Cache on your edge device.
|
||||
2. Maintains Azure IoT Edge security standards on your edge device.
|
||||
3. Ensures that Microsoft Connected Cache is always running.
|
||||
4. Reports Microsoft Connected Cache health and usage to the cloud for remote monitoring.
|
||||
|
||||
To deploy a functional Microsoft Connected Cache to your device, you must obtain the necessary keys to provision the Connected Cache instance that communicates with Delivery Optimization services, and enable the device to cache and deliver content. The architecture of Microsoft Connected Cache is described below.
|
||||
|
||||
For more details information on Azure IoT Edge, please see the Azure IoT Edge [documentation](/azure/iot-edge/about-iot-edge).
|
||||
|
||||
## How Microsoft Connected Cache Works
|
||||
|
||||
1. The Azure Management Portal is used to create Microsoft Connected Cache nodes.
|
||||
2. The Microsoft Connected Cache container is deployed and provisioned to the server using the installer provided in the portal.
|
||||
3. Client policy is set in your management solution to point to the IP address or FQDN of the cache server.
|
||||
4. Microsoft end-user devices make range requests for content from the Microsoft Connected Cache node.
|
||||
5. The Microsoft Connected Cache node pulls content from the CDN, seeds its local cache stored on disk, and delivers the content to the client.
|
||||
6. Subsequent requests from end-user devices for content will now come from cache.
|
||||
7. If the Microsoft Connected Cache node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
|
||||
|
||||
See the following diagram.
|
||||
|
||||
|
||||
|
||||
## Also see
|
||||
|
||||
[Introducing Microsoft Connected Cache](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898)
|
||||
Reference in New Issue
Block a user