deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 05:17:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

faq is now a yaml file, other restructuring and spellcheck

Browse Source
This commit is contained in:
Amy Zhou 2022-09-30 17:21:59 -07:00
parent c2f955153d
commit 899984a9d9
8 changed files with 692 additions and 163 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
windows/deployment/do/TOC.yml
View File

@ -30,7 +30,15 @@
- name: Microsoft Connected Cache overview - name: Microsoft Connected Cache overview
href: waas-microsoft-connected-cache.md href: waas-microsoft-connected-cache.md
- name: MCC for Enterprise and Education - name: MCC for Enterprise and Education
href: mcc-enterprise.md items:
- name: Overview and requirements
href: mcc-enterprise-overview.md
- name: Deploy Microsoft Connected Cache
href: mcc-enterprise-deploy.md
- name: Update and uninstall cache node
href: mcc-enterprise-update-uninstall.md
- name: Appendix
href: mcc-enterprise-appendix.md
- name: MCC for ISPs - name: MCC for ISPs
items: items:
- name: How-to guides - name: How-to guides
@ -45,8 +53,8 @@
href: mcc-isp-update.md href: mcc-isp-update.md
- name: Resources - name: Resources
items: items:
- name: FAQs - name: Frequently Asked Questions
href: mcc-isp-faq.md href: mcc-isp-faq.yml
- name: Enhancing VM performance - name: Enhancing VM performance
href: mcc-isp-vm-performance.md href: mcc-isp-vm-performance.md
- name: Support and troubleshooting - name: Support and troubleshooting

122
windows/deployment/do/mcc-enterprise-appendix.md Normal file
View File

@ -0,0 +1,122 @@
---
title: Appendix
manager: dougeby
description: Appendix on Microsoft Connected Cache (MCC) for Enterprise and Education.
ms.prod: w10
author: amymzhou
ms.localizationpriority: medium
ms.author: amymzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
# Appendix
## Diagnostics Script
If you're having issues with your MCC, we included a diagnostics script which will collect all your logs and zip them into a single file. You can then send us these logs via email for the MCC team to debug.
To run this script:
1. Navigate to the following folder in the MCC installation files:
mccinstaller \> Eflow \> Diagnostics
2. Run the following commands:
```powershell
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
.\collectMccDiagnostics.ps1
```
3. 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 (should be “**\<currentpath\>**\\mccdiagnostics\\support_bundle_\$timestamp.tar.gz”)
4. [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.
## Steps to obtain an Azure Subscription ID
1. Sign in to https://portal.azure.com/ and navigate to the Azure services section.
2. Click on **Subscriptions**. If you do not see **Subscriptions**, click on the **More Services** arrow and search for **Subscriptions**.
3. If you already have an Azure Subscription, skip to step 5. If you do not have an Azure Subscription, select **+ Add** on the top left.
4. 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.
5. On the **Subscriptions** blade, you'll find details about your current subscription. Click on the subscription name.
6. After you select the subscription name, you'll find the subscription ID in the **Overview** tab. Click on the **Copy to clipboard** icon next to your Subscription ID to copy the value.
## Troubleshooting
If you’re not able to sign up for a Microsoft Azure subscription with the error: **Account belongs to a directory that cannot be associated with an Azure subscription. Please sign in with a different account.** See [Can't sign up for a Microsoft Azure subscription](/troubleshoot/azure/general/cannot-sign-up-subscription).
Also see [Troubleshoot issues when you sign up for a new account in the Azure portal](/azure/cost-management-billing/manage/troubleshoot-azure-sign-up).
## 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](/azure/iot-edge/about-iot-edge).
## EFLOW
- [What is Azure IoT Edge for Linux on Windows](/azure/iot-edge/iot-edge-for-linux-on-windows)
- [Install Azure IoT Edge for Linux on Windows](/azure/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric#install-iot-edge)
- [PowerShell functions for Azure IoT Edge for Linux on Windows](/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions)
- EFLOW FAQ and Support: [Support · Azure/iotedge-eflow Wiki (github.com)](https://github.com/Azure/iotedge-eflow/wiki/Support#how-can-i-apply-updates-to-eflow)
- [Now ready for Production: Linux IoT Edge Modules on Windows - YouTube](https://www.youtube.com/watch?v=pgqVCg6cxVU&ab_channel=MicrosoftIoTDevelopers)
## Routing local Windows Clients to an MCC
### Get the IP address of your MCC using ifconfig
There are multiple methods that can be used to apply a policy to PCs that should participate in downloading from the MCC.
#### Registry Key
You can either set your MCC IP address or FQDN using:
1. Registry Key in 1709 and higher -
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization]<br>
"DOCacheHost"=" "
From an elevated command prompt:
```
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f
```
2. MDM Path in 1809 or higher:
.Vendor/MSFT/Policy/Config/DeliveryOptimization/DOCacheHost
3. 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, set the Cache Server Hostname (Setting found under Computer Configuration, Administrative Templates, Windows Components, Delivery Optimization) to the IP address of your MCC. For example 10.137.187.38.
![eMCC img26](images/emcc26.png)
**Verify Content using the DO Client**
To verify that the Delivery Optimization client can download content using MCC, you can use the following steps:
1. Download a game or application from the Microsoft Store.
![eMCC img27](images/emcc27.png)
2. Verify downloads came from MCC by one of two methods:
- Using PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see BytesFromCacheServer test
![eMCC img28](images/emcc28.png)
- Looking at the Delivery Optimization Activity Monitor
![eMCC img29](images/emcc29.png)
### Also see
[Microsoft Connected Cache for ISPs](mcc-isp.md)<br>
[Introducing Microsoft Connected Cache](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/introducing-microsoft-connected-cache-microsoft-s-cloud-managed/ba-p/963898)

326
windows/deployment/do/mcc-enterprise-deploy.md Normal file
View File

@ -0,0 +1,326 @@
---
title: Deploying your cache node
manager: dougeby
description: How to deploy Microsoft Connected Cache (MCC) for Enterprise and Education cache node
ms.prod: w10
author: amymzhou
ms.localizationpriority: medium
ms.author: amymzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
# Deploying your cache node
**Applies to**
- Windows 10
- Windows 11
## Steps to deploy MCC
To deploy MCC to your server:
1. [Provide Microsoft with the Azure subscription ID](#provide-microsoft-with-the-azure-subscription-id)
2. [Create the MCC Resource in Azure](#create-the-mcc-resource-in-azure)
3. [Create an MCC Node](#create-an-mcc-node-in-azure)
4. [Edit Cache Node Information](#edit-cache-node-information)
5. [Install MCC on a physical server or VM](#install-mcc-on-windows)
6. [Verify proper functioning MCC server](#verify-proper-functioning-mcc-server)
7. [Review common Issues](#common-issues) if needed.
For questions regarding these instructions contact [msconnectedcache@microsoft.com](mailto:msconnectedcache@microsoft.com)
### Provide Microsoft with the Azure Subscription ID
As part of the MCC preview onboarding process an Azure subscription ID must be provided to Microsoft.
> [!IMPORTANT]
> [Take this survey](https://aka.ms/MSConnectedCacheSignup) and provide your Azure subscription ID and contact information to be added to the allowlist for this preview. You will not be able to proceed if you skip this step.
For information about creating or locating your subscription ID, see [Steps to obtain an Azure Subscription ID](#steps-to-obtain-an-azure-subscription-id).
### Create the MCC resource in Azure
The MCC Azure management portal is used to create and manage MCC nodes. An Azure Subscription ID is used to grant access to the preview and to create the MCC resource in Azure and Cache nodes.
Once you take the survey above and the MCC team adds your subscription ID to the allowlist, you will be given a link to the Azure portal where you can create the resource described below.
1. On the Azure portal home page, choose **Create a resource**:
![eMCC img02](images/emcc02.png)
2. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results.
> [!NOTE]
> You'll not see Microsoft Connected Cache in the drop-down list. You need to type it and press enter to see the result.
3. Select **Microsoft Connected Cache** and choose **Create** on the next screen to start the process of creating the MCC resource.
![eMCC img03](images/emcc03.png)
![eMCC img04](images/emcc04.png)
4. Fill in the required fields to create the MCC resource.
- Choose the subscription that you provided to Microsoft.
- Azure resource groups are logical groups of resources. Create a new resource group and choose a name for your resource group.
- Choose **(US) West US** for the location of the resource. This choice will not impact MCC if the physical location isn't in the West US, it's just a limitation of the preview.
> [!NOTE]
> Your MCC resource will not be created properly if you do not select **(US) West US**
- Choose a name for the MCC resource.
> [!NOTE]
> Your MCC resource must not contain the word **Microsoft** in it.
![eMCC img05](images/emcc05.png)
5. Once all the information has been entered, click the **Review + Create** button. Once validation is complete, click the **Create** button to start the
resource creation.
![eMCC img06](images/emcc06.png)
#### Error: Validation failed
- If you get a Validation failed error message on your portal, it's likely because you selected the **Location** as **US West 2** or some other location that isn't **(US) West US**.
- To resolve this error, go to the previous step and choose **(US) West US**.
![eMCC img07](images/emcc07.png)
### Create an MCC node in Azure
Creating an MCC node is a multi-step process and the first step is to access the MCC private preview management portal.
1. After the successful resource creation click on the **Go to resource**.
2. Under **Cache Node Management** section on the leftmost panel, click on **Cache Nodes**.
![eMCC img08](images/emcc08.png)
3. On the **Cache Nodes** blade, click on the **Create Cache Node** button.
![eMCC img09](images/emcc09.png)
4. Clicking the **Create Cache Node** button will open the **Create Cache Node** page; **Cache Node Name** is the only field required for cache node creation.
| **Field Name** | **Expected Value** | **Description** |
|---------------------|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
| **Cache Node Name** | Alphanumeric name that includes no spaces. | The name of the cache node. You may choose names based on location like Seattle-1. This name must be unique and cannot be changed later. |
5. Enter the information for the **Cache Node** and click the **Create** button.
![eMCC img9.5](images/emcc09.5.png)
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.
![eMCC img10](images/emcc10.png)
#### Edit cache node information
Cache nodes can be deleted here by clicking the check box to the left of a **Cache Node Name** and then clicking the delete toolbar item. Be aware that if a cache node is deleted, there is no way to recover the cache node or any of the information related to the cache node.
![eMCC img11](images/emcc11.png)
### Install MCC on Windows
Installing MCC on your Windows device is a simple process. A PowerShell script performs the following tasks:
- Installs the Azure CLI
- Downloads, installs, and deploys EFLOW
- Enables Microsoft Update so EFLOW can stay up to date
- Creates a virtual machine
- Enables the firewall and opens ports 80 and 22 for inbound and outbound traffic. Port 80 is used by MCC, and port 22 is used for SSH communications.
- Configures Connected Cache tuning settings.
- Creates the necessary *FREE* Azure resource - IoT Hub/IoT Edge.
- Deploys the MCC container to server.
#### Run the installer
1. Download and unzip mccinstaller.zip from the create cache node page or cache node configuration page which contains the necessary installation files.
![eMCC img12](images/emcc12.png)
Files contained in the mccinstaller.zip file:
- **installmcc.ps1**: Main installer file.
- **installEflow.ps1**: Installs the necessary prerequisites such as the Linux VM, IoT Edge runtime, and Docker, and makes necessary host OS settings to optimize caching performance.
- **resourceDeploymentForConnectedCache.ps1**: Creates Azure cloud resources required to support MCC control plane.
- **mccdeployment.json**: Deployment manifest used by IoT Edge to deploy the MCC container and configure settings on the container, such as cache drive location sizes.
- **updatemcc.ps1**: The update script used to upgrade MCC to a particular version.
- **mccupdate.json**: Used as part of the update script
1. Open Windows PowerShell as administrator and navigate to the location of these files.
> [!NOTE]
> Ensure that Hyper-V is enabled on your device.
> Do not use PowerShell ISE, PowerShell 6.x, or PowerShell 7.x. Only Windows PowerShell version 5.x is supported.
**Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
**Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server)
#### If you're installing MCC on a local virtual machine:
1. Enable Nested Virtualization
```powershell
Set -VMProcessor -VMName "VM name" -ExposeVirtualizationExtensions $true
```
2. Enable Mac Spoofing
```powershell
Get-VMNetworkAdapter -VMName "VM name" | Set-VMNetworkAdapter -MacAddressSpoofing On
```
**Virtual machine should be in the OFF state while enabling Nested Virtualization and Mac Spoofing**
3. Set the execution policy
```powershell
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
```
> [!NOTE]
> After setting the execution policy, you'll see a warning asking if you wish to change the execution policy. Choose **[A] Yes to All**.
4. Copy the command from the portal and run it in Windows PowerShell
![eMCC img13](images/emcc13.png)
> [!NOTE]
> After running the command, and multiple times throughout the installation process, you'll receive the following notice. **Please select [R] Run once to proceed**.
> <br>
> <br>Security warning
> <br>Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run C:\\Users\\mccinstaller\\Eflow\\installmcc.ps1?
><br>
> <br>[D] Do not run **[R] Run once** [S] Suspend [?] Help (default is "D"):
3. Choose whether you would like to create a new virtual switch or select an existing one. Name your switch and select the Net Adapter to use for the switch. A computer restart will be required if you're creating a new switch.
> [!NOTE]
> Restarting your computer after creating a switch is recommended. You'll notice network delays during installation if the computer has not been restarted.
If you restarted your computer after creating a switch, start from Step 2 above and skip step 5.
![eMCC img14](images/emcc14.png)
4. Re-run the script after the restart. This time, choose **No** when asked to create a new switch. Enter the number corresponding to the switch you previously created.
![eMCC img15](images/emcc15.png)
5. Decide whether you would like to use dynamic or static address for the Eflow VM
![eMCC img16](images/emcc16.png)
> [!NOTE]
> Choosing a dynamic IP address might assign a different IP address when the MCC restarts.
> <br>A static IP address is recommended so you do not have to change this value in your management solution when MCC restarts.
6. Choose where you would like to download, install, and store the virtual hard disk for EFLOW. You'll also be asked how much memory, storage, and cores you would like to allocate for the VM. In this example, we chose the default values for all prompts.
7. Follow the Azure Device Login link and sign into the Azure portal.
![eMCC img17](images/emcc17.png)
8. If this is your first MCC deployment, please select **n** so that a new IoT Hub can be created. If you have already configured MCC before, choose **y** so that your MCCs are grouped in the same IoT Hub.
1. You'll be shown a list of existing IoT Hubs in your Azure Subscription; Enter the number corresponding to the IoT Hub to select it. **You'll likely have only 1 IoT Hub in your subscription, in which case you want to enter “1”**
![eMCC img18](images/emcc18.png)
![eMCC img19](images/emcc19.png)
9. Your MCC deployment is now complete.
1. If you do not see any errors, please continue to the next section to validate your MCC deployment.
2. After validating your MCC is properly functional, please review your management solution documentation, such as [Intune](/mem/intune/configuration/delivery-optimization-windows), to set the cache host policy to the IP address of your MCC.
3. If you had errors during your deployment, see the [Troubleshooting](#troubleshooting) section in this article.
### Verify proper functioning MCC server
#### Verify Client Side
Connect to the EFLOW VM and check if MCC is properly running:
1. Open PowerShell as an Administrator
2. Enter the following commands:
```powershell
Connect-EflowVm
sudo -s
iotedge list
```
![eMCC img20](images/emcc20.png)
You should see MCC, edgeAgent, and edgeHub running. If you see edgeAgent or edgeHub but not MCC, please try this command in a few minutes. The MCC container can take a few minutes to deploy
#### Verify server side
For a validation of properly functioning MCC, execute the following command in the EFLOW VM or any device in the network. Replace <CacheServerIP\> with the IP address of the cache server.
```powershell
wget [http://<CacheServerIP>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com]
```
A successful test result will look like this:
![eMCC img21](images/emcc21.png)
OR
![eMCC img22](images/emcc22.png)
Similarly, enter this URL from a browser in the network:
[http://YourCacheServerIP/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com]()
If the test fails, see the common issues section for more information.
### Intune (or other management software) configuration for MCC
For an Intune deployment, create a Configuration Profile and include the Cache Host eFlow IP Address or FQDN:
![eMCC img23](images/emcc23.png)
### Common Issues
#### PowerShell issues
If you're seeing errors similar to this: “The term ‘Get-Something’ isn't recognized as the name of a cmdlet, function, script file, or operable program.”
1. Ensure you're running Windows PowerShell version 5.x.
2. Run \$PSVersionTable and ensure you’re running version 5.x and *not version 6 or 7*.
3. Ensure you have Hyper-V enabled:
**Windows 10:** [Enable Hyper-V on Windows 10](/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v)
**Windows Server:** [Install the Hyper-V role on Windows Server](/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server)
#### Verify Running MCC Container
Connect to the Connected Cache server and check the list of running IoT Edge modules using the following commands:
```bash
Connect-EflowVm
sudo iotedge list​
```
![eMCC img24](images/emcc24.png)
If edgeAgent and edgeHub containers are listed, but not “MCC”, you may view the status of the IoT Edge security manager using the command:
```bash
sudo journalctl -u iotedge -f
```
For example, this command will provide the current status of the starting, stopping of a container, or the container pull and start as is shown in the sample below:
![eMCC img25](images/emcc25.png)
Use this command to check the IoT Edge Journal
```bash
sudo journalctl -u iotedge –f
```
Please note: You should consult the IoT Edge troubleshooting guide ([Common issues and resolutions for Azure IoT Edge](/azure/iot-edge/troubleshoot)) for any issues you may encounter configuring IoT Edge, but we have listed a few issues below that we hit during our internal validation.

93
windows/deployment/do/mcc-enterprise-overview.md Normal file
View File

@ -0,0 +1,93 @@
---
title: Overview and requirements
manager: dougeby
description: Overview and requirements of Microsoft Connected Cache (MCC) for Enterprise and Education.
ms.prod: w10
author: amymzhou
ms.localizationpriority: medium
ms.author: amymzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
# Overview and requirements of Microsoft Connected Cache for Enterprise and Education (private preview)
**Applies to**
- Windows 10
- Windows 11
## Overview
> [!IMPORTANT]
> Microsoft Connected Cache is currently a private preview feature. During this phase we invite customers to take part in early access for testing purposes. This phase does not include formal support, and should not be used for production workloads. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
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 physical 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 a client policy using your management tool, such as [Intune](/mem/intune/).
MCC is a hybrid (a mix of on-premises and cloud resources) SaaS solution built as an Azure IoT Edge module; it's a Docker compatible Linux container that is deployed to your Windows devices. IoT Edge for Linux on Windows (EFLOW) was chosen because it's 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 will be a Linux IoT Edge module running on the Windows Host OS.
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 the following important functions to manage MCC on your edge device:
1. Installs and updates MCC on your edge device.
2. Maintains Azure IoT Edge security standards on your edge device.
3. Ensures that MCC is always running.
4. Reports MCC health and usage to the cloud for remote monitoring.
To deploy a functional MCC to your device, you must obtain the necessary keys that will provision the Connected Cache instance to communicate with Delivery Optimization services and enable the device to cache and deliver content. See [figure 1](#fig1) below for a summary of the architecture of MCC, built using IoT Edge.
For more information about Azure IoT Edge, see [What is Azure IoT Edge](/azure/iot-edge/about-iot-edge).
## How MCC works
The following steps describe how MCC is provisioned and used.
1. The Azure Management Portal is used to create MCC nodes.
2. The MCC container is deployed and provisioned to a server using the installer provided in the portal.
3. Client policy is configured 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 MCC node.
5. An MCC node pulls content from the CDN, seeds its local cache stored on disk, and delivers content to the client.
6. Subsequent requests from end-user devices for content come from the cache.
If an MCC node is unavailable, the client will pull content from CDN to ensure uninterrupted service for your subscribers.
<a id="fig1">
![eMCC img01](images/emcc01.png)
</a>Figure 1: **MCC processes**. Each number in the diagram corresponds to the steps described above.
## Enterprise requirements for MCC
1. **Azure subscription**: MCC management portal is hosted within Azure and is used to create the Connected Cache [Azure resource](/azure/cloud-adoption-framework/govern/resource-consistency/resource-access-management) and IoT Hub resource. Both are free services.
Your Azure subscription ID is first used to provision MCC services, and enable access to the preview. The MCC server requirement for an Azure subscription will cost you nothing. If you do not have an Azure subscription already, you can create an Azure [Pay-As-You-Go](https://azure.microsoft.com/offers/ms-azr-0003p/) account which requires a credit card for verification purposes. For more information, see the [Azure Free Account FAQ](https://azure.microsoft.com/free/free-account-faq/).
The resources used for the preview and in the future when this product is ready for production will be completely free to you, like other caching solutions.
2. **Hardware to host MCC**: The recommended configuration will serve approximately 35000 managed devices, downloading a 2GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
**EFLOW Requires Hyper-V support**
- On Windows client, enable the Hyper-V feature
- On Windows Server, install the Hyper-V role and create a default network switch
Disk recommendations:
- Using an SSD is recommended as cache read speed of SSD is superior to HDD
NIC requirements:
- Multiple NICs on a single MCC instance aren't supported.
- 1 Gbps NIC is the minimum speed recommended but any NIC is supported.
- For best performance, NIC and BIOS should support SR-IOV
VM networking:
- An external virtual switch to support outbound and inbound network communication (created during the installation process)
### Sizing recommendations
| Component | Branch Office / Small Enterprise | Large Enterprise |
| -- | --- | --- |
| OS| Windows Server 2019*/2022 <br> Windows 10*/11 (Pro or Enterprise) with Hyper-V Support <br><br>* Windows 10 and Windows Server 2019 build 17763 or later | Same |
|NIC | 1 Gbps | 5 Gbps |
|Disk | SSD <br>1 drive <br>50GB each |SSD <br>1 drive <br>200GB each |
|Memory | 4GB | 8GB |
|Cores | 4 | 8 |

45
windows/deployment/do/mcc-enterprise-update-uninstall.md Normal file
View File

@ -0,0 +1,45 @@
---
title: Update or uninstall Microsoft Connected Cache for Enterprise and Education
manager: dougeby
description: Details on updating or uninstalling Microsoft Connected Cache (MCC) for Enterprise and Education.
ms.prod: w10
author: amymzhou
ms.localizationpriority: medium
ms.author: amymzhou
ms.collection: M365-modern-desktop
ms.topic: article
---
# Update or uninstall Microsoft Connected Cache for Enterprise and Education
## Update MCC
Throughout the private preview phase, we will send you security and feature updates for MCC. Please follow these steps to perform the update.
Run the following command with the **arguments** we provided in the email to update your MCC:
```powershell
# .\updatemcc.ps1 version="**\<VERSION\>**" tenantid="**\<TENANTID\>**" customerid="**\<CUSTOMERID\>**" cachenodeid="**\<CACHENODEID\>**" customerkey="**\<CUSTOMERKEY\>**"
```
For example:
```powershell
# .\updatemcc.ps1 version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.659" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99a”
```
## Uninstall MCC
Please contact the MCC Team before uninstalling to let us know if you're facing
issues.
This script will remove the following:
1. EFLOW + Linux VM
2. IoT Edge
3. Edge Agent
4. Edge Hub
5. MCC
6. Moby CLI
7. Moby Engine
To delete MCC, go to Control Panel \> Uninstall a program \> Select Azure IoT
Edge LTS \> Uninstall

138
windows/deployment/do/mcc-isp-faq.md
View File

@ -1,138 +0,0 @@
---
title: FAQs on Microsoft Connected Cache for ISP
manager: dougeby
description: FAQs on Microsoft Connected Cache (MCC) for ISP
keywords: updates, downloads, network, bandwidth
ms.prod: w10
ms.mktglfcycl: deploy
audience: itpro
author: nidos
ms.localizationpriority: medium
ms.author: nidos
ms.collection: M365-modern-desktop
ms.topic: article
---
# Microsoft Connected Cache for ISP (public preview)
**Applies to**
- Windows 10
- Windows 11
<br/>
**1. Is this a free service?**
Yes. Microsoft Connected Cache is a free service.
<br/>
**2. What will Microsoft Connected Cache do for me? How will it impact our customers?**
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.
<br/>
**3. Is there an NDA to sign?**
No NDA is required.
<br/>
**4. What are the prerequisites and hardware requirements?**
- Azure subscription
- Hardware to host Microsoft Connected Cache - The recommended configuration below will serve approximately 35,000 consumer devices downloading a 2GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
We have 1 customer who is able to achieve 40 Gbps egress rate using the following hardware specification:
- Dell PowerEdge R330
- 2 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz , total 32core
- 48GB, Micron Technology 18ASF1G72PDZ-2G1A1, Speed: 2133 MT/s
- 4 - Transcend SSD230s 1TB SATA Drives
Intel Corporation Ethernet 10G 2P X520 Adapter (Link Aggregated)
<br/>
| Taffic Estimate | Hardware/VM Recommendation |
|-----------|:-----------:|
| <5G Peak | 8 Cores<br/>16 GB Memory<br/>1 SSD Drive 500 GB |
| 10 - 20G Peak | 16 Cores<br/>32 GB Memory<br/>2 - 3 SSD Drives 1 TB |
| 20 - 40G Peak | 32 Cores<br/>64 GB Memory<br/>4 - 6 SSDs 1 TB |
<br/>
<br/>
**5. Will I need to provide hardware BareMetal server or VM?**
Microsoft Connected Cache is a software-only caching solution and will require you to provide your own server to host the software.
<br/>
**6. Can we use hard drives instead of SSDs?**
We highly recommend using SSDs as Microsoft Connected Cache is a read intensive application. We also recommend using multiple drives to improve performance.
<br/>
**7. Will I need to manually enter the CIDR blocks? If I have multiple cache nodes, should I configure a subset of CIDR blocks to each cache node?**
You have the option to route your traffic using manual CIDR blocks or BGP. If you have multiple Microsoft Connected Cache(s), you can allocate subsets of CIDR blocks to each cache node if you wish. However, since Microsoft Connected Cache has automatic load balancing, we recommend adding all of your traffic to all of your cache nodes.
<br/>
**8. Should I add any load balancing mechanism?**
You do not need to add any load balancing. Our service will take care of routing traffic if you have multiple cache nodes serving the same CIDR blocks based on the reported health of the cache node.
<br/>
**9. How many Microsoft Connected Cache instances will I need? How do we setup if we support multiple countries?**
As stated in the table above, the recommended configuration will achieve near the maximum possible egress of 20Gbps with a two-port link aggregated NIC and four cache drives. If you provide us with your ASN numbers, we can give a rough estimate of how many Microsoft Connected Cache instances may be needed. If your ISP spans multiple countries, you can set up separate cache nodes per country.
<br/>
**10. Where should we install Microsoft Connected Cache?**
You are in control of your hardware and you can pick the location based on your traffic and end customers. You can choose the location where you have your routers or where you have dense traffic or any other parameters.
<br/>
**11. How long would a piece of content live within the Microsoft Connected Cache? Is content purged from the cache?**
A request for said content is made, and NGINX looks at the cache control headers from the original acquisition, and if that content has expired, NGINX will continue to serve the stale content while it is downloading the new content. We are caching the content for 30 days. The content will be in the hot cache path (open handles and such) for 24 hrs, but will reside on disk for 30 days.
The drive fills up and nginx will start to delete content based on its own algorithm, probably some combination of least recently used.
<br/>
**12. What content is cached by Microsoft Connected Cache?**
See [Delivery Optimization and Microsoft Connected Cache content endpoints - Windows Deployment](delivery-optimization-endpoints.md) for more information.
<br/>
**13. Does Microsoft Connected Cache support Xbox or Teams content?**
Currently, Microsoft Connected Cache does not support Xbox or Teams content. However, supporting Xbox content is of high priority, and we expect this feature in the near future. We'll let you know as soon as it becomes available!
<br/>
**14. Is IPV6 supported?**
No, we do not currently support IPV6. We plan to support it in the future.
<br/>
**15. Is Microsoft Connected Cache stable and reliable?**
We have already successfully onboarded ISPs in many countries 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.
<br/>
**16.How does Microsoft Connected Cache populate its content?**
Microsoft Connected Cache is a cold cache warmed by client requests. The client requests content and that is what fills up the cache. There is 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 3rd party CDNs or from AFD.
<br/>
**17. What do I do if I need more support and have more questions even after reading this FAQ page?**
You can find more information or post your questions on MCC Community Forum.
<link to community forum>
For further support for your Microsoft Connected Cache you can find solutions to common problems here. <link to common issues>
<br/>
**18. What CDNs will Microsoft Connected Cache pull content from?**
Microsoft relies on a dynamic mix of 1st and 3rd party CDN providers to ensure enough capacity, redundancy, and performance for the delivery of Microsoft served content. Though we do not provide lists of the CDN vendors we utilize as they can change without notice, our endpoints are public knowledge. If someone were to perform a series of DNS lookups against our endpoints (tlu.dl.delivery.mp.microsoft.com for example), they would be able to determine which CDN or CDNs were in rotation at a given point in time:
$ dig +noall +answer tlu.dl.delivery.mp.microsoft.com | grep -P "IN\tA"
c-0001.c-msedge.net. 20 IN A 13.107.4.50
$ whois 13.107.4.50|grep "Organization:"
Organization: Microsoft Corporation (MSFT)

77
windows/deployment/do/mcc-isp-faq.yml Normal file
View File

@ -0,0 +1,77 @@
### YamlMime:FAQ
metadata:
title: Microsoft Connected Cache Frequently Asked Questions
description: The following article is a list of frequently asked questions for Microsoft Connected Cache.
ms.sitesec: library
ms.pagetype: security
ms.localizationpriority: medium
author: amymzhou
ms.author: amymzhou
manager: dougeby
audience: ITPro
ms.collection:
- M365-security-compliance
- highpri
ms.topic: faq
ms.date: 09/30/2022
ms.custom: seo-marvel-apr2020
title: Microsoft Connected Cache Frequently Asked Questions
summary: |
**Applies to**
- Windows 10
- Windows 11
sections:
- name: Ignored
questions:
- question: Is this product a free service?
answer: Yes. Microsoft Connected Cache is a free service.
- 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: Is there a non-disclosure agreement to sign?
answer: No non-disclosure agreement is required.
- question: What are the prerequisites and hardware requirements?
answer: |
- Azure subscription
- Hardware to host Microsoft Connected Cache - The recommended configuration below will serve approximately 35,000 consumer devices downloading a 2-GB payload in 24-hour timeframe at a sustained rate of 6.5 Gbps.
We have one customer who is able to achieve 40-Gbps egress rate using the following hardware specification:
- Dell PowerEdge R330
- 2 x Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40 GHz , total 32 core
- 48 GB, Micron Technology 18ASF1G72PDZ-2G1A1, Speed: 2133 MT/s
- 4 - Transcend SSD230s 1 TB SATA Drives
Intel Corporation Ethernet 10G 2P X520 Adapter (Link Aggregated)
- question: Will I need to provide hardware BareMetal server or VM?
answer: Microsoft Connected Cache is a software-only caching solution and will require you to provide your own server to host the software.
- question: Can we use hard drives instead of SSDs?
answer: We highly recommend using SSDs as Microsoft Connected Cache is a read intensive application. We also recommend using multiple drives to improve performance.
- question: Will I need to manually enter the CIDR blocks? If I have multiple cache nodes, should I configure a subset of CIDR blocks to each cache node?
answer: You can choose route your traffic using manual CIDR blocks or BGP. If you have multiple Microsoft Connected Cache(s), you can allocate subsets of CIDR blocks to each cache node if you wish. However, since Microsoft Connected Cache has automatic load balancing, we recommend adding all of your traffic to all of your cache nodes.
- question: Should I add any load balancing mechanism?
answer: You don't need to add any load balancing. Our service will take care of routing traffic if you have multiple cache nodes serving the same CIDR blocks based on the reported health of the cache node.
- question: How many Microsoft Connected Cache instances will I need? How do we set up if we support multiple countries?
answer: As stated in the table above, the recommended configuration will achieve near the maximum possible egress of 20 Gbps with a two-port link aggregated NIC and four cache drives. If you provide us with your ASN numbers, we can give a rough estimate of how many Microsoft Connected Cache instances may be needed. If your ISP spans multiple countries, you can set up separate cache nodes per country.
- question: Where should we install Microsoft Connected Cache?
answer: You are in control of your hardware and you can pick the location based on your traffic and end customers. You can choose the location where you have your routers or where you have dense traffic or any other parameters.
- question: How long would a piece of content live within the Microsoft Connected Cache? Is content purged from the cache?
answer: Once a request for said content is made, NGINX will look at the cache control headers from the original acquisition. If that content has expired, NGINX will continue to serve the stale content while it's downloading the new content. We cache the content for 30 days. The content will be in the hot cache path (open handles and such) for 24 hrs, but will reside on disk for 30 days. The drive fills up and nginx will start to delete content based on its own algorithm, probably some combination of least recently used.
- question: What content is cached by Microsoft Connected Cache?
answer: For more information about content cached, see [Delivery Optimization and Microsoft Connected Cache content endpoints - Windows Deployment](delivery-optimization-endpoints.md).
- question: Does Microsoft Connected Cache support Xbox or Teams content?
answer: Currently, Microsoft Connected Cache doesn't support Xbox or Teams content. However, supporting Xbox content is of high priority, and we expect this feature soon. We'll let you know as soon as it becomes available!
- question: 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 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.
- 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 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).
- question: What CDNs will Microsoft Connected Cache pull content from?
answer: |
Microsoft relies on a dynamic mix of 1st and 3rd party CDN providers to ensure enough capacity, redundancy, and performance for the delivery of Microsoft served content. Though we don't provide lists of the CDN vendors we utilize as they can change without notice, our endpoints are public knowledge. If someone were to perform a series of DNS lookups against our endpoints (tlu.dl.delivery.mp.microsoft.com for example), they would be able to determine which CDN or CDNs were in rotation at a given point in time:
$ dig +noall +answer tlu.dl.delivery.mp.microsoft.com | grep -P "IN\tA"
c-0001.c-msedge.net. 20 IN A 13.107.4.50
$ whois 13.107.4.50|grep "Organization:"
Organization: Microsoft Corporation (MSFT)

40
windows/deployment/do/mcc-isp-support.md
View File

@ -1,5 +1,5 @@
--- ---
title: Troubleshooting Issues for Microsoft Connected Cache for ISP title: Support and troubleshooting
manager: dougeby manager: dougeby
description: Troubleshooting Issues for Microsoft Connected Cache for ISP description: Troubleshooting Issues for Microsoft Connected Cache for ISP
keywords: updates, downloads, network, bandwidth keywords: updates, downloads, network, bandwidth
@ -13,38 +13,34 @@ ms.collection: M365-modern-desktop
ms.topic: article ms.topic: article
--- ---
# Troubleshooting Issues for Microsoft Connected Cache for ISP (public preview) # Support and troubleshooting
**Applies to** **Applies to**
- Windows 10 - Windows 10
- Windows 11 - Windows 11
<br/> ## Sign up errors
## Sign up Errors #### Cannot verify account
### Could not verify account: During sign-up, we verify the information you provide against what is present in [Peering DB](https://www.peeringdb.com/). Make sure the information for your ISP entry on [Peering DB](https://www.peeringdb.com/) is up to date and matches what you provide during sign-up.
During sign up we verify the information you provide against what is present in [Peering DB]. Make sure the information you have provided on Peering DB is up to date and matches what you provide during sign up.
<br/>
<br/>
### Invalid verification code: #### Invalid verification code
During sign up, a verification code is sent to your NOC email address present in Peering DB. **TBD** This code expires in 24 hours. You will need to request a new verification code and use that to complete sign up.
<br/>
<br/>
During sign-up, a verification code is sent to your NOC email address present in [Peering DB](https://www.peeringdb.com/). This code expires in 24 hours. If expired, you'll need to request a new verification code to complete sign up.
## Cache Node Errors ## Cache Node Errors
### Cannot find my cache node: #### Cannot find my cache node
If you previously had access to your cache nodes but it is now no longer accessible, it may be because you had a trial subscription and its trial period ended.
#### Recommended steps: Did you previously had access to your cache nodes but it's now no longer accessible? If so, it may be because you had a trial subscription, and its trial period ended. To resolve this issue, complete the following two steps:
1. Create a new Azure Pay As You Go subscription
1. Recreate the cache nodes using the new subscription
#### Recommended Documents: 1. Create a new Azure Pay-As-You-Go subscription
[Steps to obtain Azure subscription](https://aka.ms/MCC-Azure-Subscription) 1. Recreate the cache nodes using the new subscription
[Pay-as-you-go-subscription](https://azure.microsoft.com/en-us/offers/ms-azr-0003p/)
[Azure free account FAQs](https://azure.microsoft.com/en-us/free/free-account-faq/) #### Recommended Documents
[Steps to obtain Azure subscription](https://aka.ms/MCC-Azure-Subscription)
[Pay-as-you-go-subscription](https://azure.microsoft.com/en-us/offers/ms-azr-0003p/)
[Azure free account FAQs](https://azure.microsoft.com/en-us/free/free-account-faq/)