mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-18 20:03:40 +00:00
formatting
This commit is contained in:
@ -55,7 +55,7 @@ If an MCC node is unavailable, the client will pull content from CDN to ensure u
|
|||||||
|
|
||||||
<a id="fig1">
|
<a id="fig1">
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
</a>Figure 1: **MCC processes**. Each number in the diagram corresponds to the steps described above.
|
</a>Figure 1: **MCC processes**. Each number in the diagram corresponds to the steps described above.
|
||||||
|
|
||||||
@ -111,7 +111,7 @@ For questions regarding these instructions contact [msconnectedcache@microsoft.c
|
|||||||
|
|
||||||
### Provide Microsoft with the Azure Subscription ID
|
### 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 MCC preview onboarding process an Azure subscription ID must be provided to Microsoft.
|
||||||
|
|
||||||
> [!IMPORTANT]
|
> [!IMPORTANT]
|
||||||
> [Contact Microsoft](mailto:mccforenterprise@microsoft.com?subject=[MCC%20for%20Enterprise]%20Please%20add%20our%20Azure%20subscription%20to%20the%20allow%20list) and provide this information if you have not already. You will not be able to proceed if you skip this step.
|
> [Contact Microsoft](mailto:mccforenterprise@microsoft.com?subject=[MCC%20for%20Enterprise]%20Please%20add%20our%20Azure%20subscription%20to%20the%20allow%20list) and provide this information if you have not already. You will not be able to proceed if you skip this step.
|
||||||
@ -127,7 +127,7 @@ The MCC Azure management portal is used to create and manage MCC nodes. An Azure
|
|||||||
<https://portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=Microsoft_ConnectedCache_EntHidden>
|
<https://portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=Microsoft_ConnectedCache_EntHidden>
|
||||||
|
|
||||||
1. On the Azure Portal home page, choose **Create a resource**:
|
1. On the Azure Portal home page, choose **Create a resource**:
|
||||||

|

|
||||||
|
|
||||||
2. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results.
|
2. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results.
|
||||||
|
|
||||||
@ -136,8 +136,8 @@ The MCC Azure management portal is used to create and manage MCC nodes. An Azure
|
|||||||
|
|
||||||
3. Select **Microsoft Connected Cache** and choose **Create** on the next screen to start the process of creating the MCC resource.
|
3. Select **Microsoft Connected Cache** and choose **Create** on the next screen to start the process of creating the MCC resource.
|
||||||
|
|
||||||

|

|
||||||

|

|
||||||
|
|
||||||
4. Fill in the required fields to create the MCC resource.
|
4. Fill in the required fields to create the MCC resource.
|
||||||
|
|
||||||
@ -153,19 +153,19 @@ The MCC Azure management portal is used to create and manage MCC nodes. An Azure
|
|||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Your MCC resource must not contain the word **Microsoft** in it.
|
> Your MCC resource must not contain the word **Microsoft** in it.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
5. Once all the information has been entered, click the **Review + Create** button. Once validation is complete, click the **Create** button to start the
|
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.
|
resource creation.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
#### Error: Validation failed
|
#### Error: Validation failed
|
||||||
|
|
||||||
- If you get a Validation failed error message on your portal, it is likely because you selected the **Location** as **US West 2** or some other location that is not **(US) West US**.
|
- If you get a Validation failed error message on your portal, it is likely because you selected the **Location** as **US West 2** or some other location that is not **(US) West US**.
|
||||||
- To resolve this error, go to the previous step and choose **(US) West US**.
|
- To resolve this error, go to the previous step and choose **(US) West US**.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
### Create an MCC node in Azure
|
### Create an MCC node in Azure
|
||||||
|
|
||||||
@ -174,11 +174,11 @@ Creating a MCC node is a multi-step process and the first step is to access the
|
|||||||
1. After the successful resource creation click on the **Go to resource**.
|
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**.
|
2. Under **Cache Node Management** section on the leftmost panel, click on **Cache Nodes**.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
3. On the **Cache Nodes** blade, click on the **Create Cache Node** button.
|
3. On the **Cache Nodes** blade, click on the **Create Cache Node** button.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
@ -188,19 +188,19 @@ Creating a MCC node is a multi-step process and the first step is to access the
|
|||||||
|
|
||||||
5. Enter the information for the **Cache Node** and click the **Create** button.
|
5. Enter the information for the **Cache Node** and click the **Create** button.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
If there are errors, the form will provide guidance on how to correct the errors.
|
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 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.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
#### Edit cache node information
|
#### 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.
|
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.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
### Install MCC on Windows
|
### Install MCC on Windows
|
||||||
|
|
||||||
@ -219,7 +219,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p
|
|||||||
|
|
||||||
1. Download and unzip mccinstaller.zip from the create cache node page or cache node configuration page which contains the necessary installation files.
|
1. Download and unzip mccinstaller.zip from the create cache node page or cache node configuration page which contains the necessary installation files.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Files contained in the mccinstaller.zip file:
|
Files contained in the mccinstaller.zip file:
|
||||||
|
|
||||||
@ -263,7 +263,7 @@ Files contained in the mccinstaller.zip file:
|
|||||||
|
|
||||||
4. Copy the command from the portal and run it in Windows PowerShell
|
4. Copy the command from the portal and run it in Windows PowerShell
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> After running the command, and multiple times throughout the installation process, you will receive the following notice. **Please select [R] Run once to proceed**.
|
> After running the command, and multiple times throughout the installation process, you will receive the following notice. **Please select [R] Run once to proceed**.
|
||||||
@ -280,15 +280,15 @@ Files contained in the mccinstaller.zip file:
|
|||||||
|
|
||||||
If you restarted your computer after creating a switch, start from Step 2 above and skip step 5.
|
If you restarted your computer after creating a switch, start from Step 2 above and skip step 5.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
5. Decide whether you would like to use dynamic or static address for the Eflow VM
|
5. Decide whether you would like to use dynamic or static address for the Eflow VM
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
> Choosing a dynamic IP address might assign a different IP address when the MCC restarts.
|
> Choosing a dynamic IP address might assign a different IP address when the MCC restarts.
|
||||||
@ -298,14 +298,14 @@ Files contained in the mccinstaller.zip file:
|
|||||||
|
|
||||||
7. Follow the Azure Device Login link and sign into the Azure Portal.
|
7. Follow the Azure Device Login link and sign into the Azure Portal.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
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.
|
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 will be shown a list of existing IoT Hubs in your Azure Subscription; Enter the number corresponding to the IoT Hub to select it. **You will likely have only 1 IoT Hub in your subscription, in which case you want to enter “1”**
|
1. You will be shown a list of existing IoT Hubs in your Azure Subscription; Enter the number corresponding to the IoT Hub to select it. **You will likely have only 1 IoT Hub in your subscription, in which case you want to enter “1”**
|
||||||
|
|
||||||

|

|
||||||

|

|
||||||
|
|
||||||
9. Your MCC deployment is now complete.
|
9. Your MCC deployment is now complete.
|
||||||
|
|
||||||
@ -328,7 +328,7 @@ sudo -s
|
|||||||
iotedge list
|
iotedge list
|
||||||
```
|
```
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
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
|
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
|
||||||
|
|
||||||
@ -342,11 +342,11 @@ wget [http://\<CacheServerIP\>/mscomtest/wuidt.gif?cacheHostOrigin=au.download.w
|
|||||||
|
|
||||||
A successful test result will look like this:
|
A successful test result will look like this:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
OR
|
OR
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Similarly, enter this URL from a browser in the network:
|
Similarly, enter this URL from a browser in the network:
|
||||||
|
|
||||||
@ -358,7 +358,7 @@ If the test fails, see the common issues section for more information.
|
|||||||
|
|
||||||
Example of setting the cache host policy to the MCC’s IP address / FQDN:
|
Example of setting the cache host policy to the MCC’s IP address / FQDN:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
### Common Issues
|
### Common Issues
|
||||||
|
|
||||||
@ -385,7 +385,7 @@ Connect-EflowVm
|
|||||||
sudo iotedge list
|
sudo iotedge list
|
||||||
```
|
```
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
If edgeAgent and edgeHub containers are listed, but not “MCC”, you may view the status of the IoTEdge security manager using the command:
|
If edgeAgent and edgeHub containers are listed, but not “MCC”, you may view the status of the IoTEdge security manager using the command:
|
||||||
|
|
||||||
@ -395,7 +395,7 @@ 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:
|
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:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Use this command to check the IoT Edge Journal
|
Use this command to check the IoT Edge Journal
|
||||||
|
|
||||||
@ -522,7 +522,7 @@ You can either set your MCC IP address or FQDN using:
|
|||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
**Verify Content using the DO Client**
|
**Verify Content using the DO Client**
|
||||||
|
|
||||||
@ -530,17 +530,17 @@ To verify that Delivery Optimization client can download content using Microsoft
|
|||||||
|
|
||||||
1. Download a game or application from the Microsoft Store.
|
1. Download a game or application from the Microsoft Store.
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
2. Verify downloads came from MCC by one of two methods:
|
2. Verify downloads came from MCC by one of two methods:
|
||||||
|
|
||||||
- Using PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see BytesFromCacheServer test
|
- Using PowerShell Cmdlet Get-DeliveryOptimizationStatus you should see BytesFromCacheServer test
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
- Looking at the Delivery Optimization Activity Monitor
|
- Looking at the Delivery Optimization Activity Monitor
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
## Also see
|
## Also see
|
||||||
|
|
||||||
|
@ -102,102 +102,85 @@ For questions regarding these instructions contact [msconnectedcache@microsoft.c
|
|||||||
|
|
||||||
## Provide Microsoft with the Azure Subscription ID
|
## Provide Microsoft with the Azure Subscription ID
|
||||||
|
|
||||||
As part of the MCC preview onboarding process the Azure subscription ID will have been provided to Microsoft. Please contact Microsoft and provide this information if you have not already.
|
As part of the MCC preview onboarding process an Azure subscription ID must be provided to Microsoft.
|
||||||
|
|
||||||
|
> [!IMPORTANT]
|
||||||
|
> [Contact Microsoft](mailto:mccforenterprise@microsoft.com?subject=[MCC%20for%20Enterprise]%20Please%20add%20our%20Azure%20subscription%20to%20the%20allow%20list) and provide your Azure subscription ID if you have not already. You will not be able to proceed if you skip this step.
|
||||||
|
|
||||||
|
|
||||||
## Create the MCC Resource in Azure
|
For information about creating or locating your subscription ID, see [Steps to obtain an Azure Subscription ID](#steps-to-obtain-an-azure-subscription-id).
|
||||||
|
|
||||||
[Link](https://aka.ms/MCC-ISP-PortalDemo) to video instructions:
|
### Create the MCC resource in Azure
|
||||||
<https://aka.ms/MCC-ISP-PortalDemo>
|
|
||||||
|
|
||||||
The MCC Azure management portal is used to create and
|
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.
|
||||||
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.
|
|
||||||
|
|
||||||
##### Use the following link and log in to Azure <https://portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=Microsoft_ConnectedCacheHidden>
|
Use the following link to sign in to Azure: <https://portal.azure.com/?microsoft_azure_marketplace_ItemHideKey=Microsoft_ConnectedCache_EntHidden>
|
||||||
|
|
||||||
- Choose Create a resource
|
1. Choose **Create a resource**
|
||||||

|
|
||||||
|
|
||||||
- Type " MCC" into the search box and be sure to hit the
|

|
||||||
Enter key to show search results.
|
|
||||||
|
|
||||||
- Select “MCC” and select “Create” on the next screen to
|
2. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results.
|
||||||
start the process of creating the MCC resource.
|
|
||||||
|
|
||||||

|
3. Select **Microsoft Connected Cache** and choose **Create** on the next screen to start the process of creating the MCC resource.
|
||||||
|
|
||||||

|

|
||||||
|

|
||||||
|
|
||||||
- Fill in the required fields to create the MCC
|
4. Fill in the required fields to create the MCC resource.
|
||||||
resource.
|
|
||||||
|
|
||||||
- Choose the subscription provided to Microsoft.
|
- 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 is not in the West US, it is just a limitation of the preview.
|
||||||
|
|
||||||
- Azure resource groups are logical groups of resources. Create a new
|
> [!NOTE]
|
||||||
resource group and choose a name for your resource group.
|
> Your MCC resource will not be created properly if you do not select **(US) West US**
|
||||||
|
|
||||||
- Choose “**US West**” for the location of the resource. This choice will
|
|
||||||
not impact MCC if the physical location is not in
|
|
||||||
the West US, it is just a limitation of the preview.
|
|
||||||
|
|
||||||
- Choose a name for the MCC resource.
|
- Choose a name for the MCC resource.
|
||||||
|
|
||||||

|
||||||
automatically generated](media/0485f6efd6fb9c2ff4ac19a70298e322.png)
|
|
||||||
|
|
||||||
- Once all the information has been entered, click on the “Review + Create”
|
5. Once all the information has been entered, click the **Review + Create** button. Once validation is complete, click the **Create** button to start the
|
||||||
button. Once validation is complete, click the “Create” button to start the
|
|
||||||
resource creation.
|
resource creation.
|
||||||

|
|
||||||
|
|
||||||
##### Error: Validation failed
|

|
||||||
|
|
||||||
- If you get a Validation failed error message on your portal, it is likely
|
#### Error: Validation failed
|
||||||
because you selected the Location as US West 2.
|
|
||||||
|
|
||||||
- To bypass this error, navigate to the previous step and choose (US) West US.
|
- If you get a Validation failed error message on your portal, it is likely because you selected the **Location** as **US West 2** or some other location that is not **(US) West US**.
|
||||||
|
- To resolve this error, go to the previous step and choose **(US) West US**.
|
||||||
|
|
||||||

|
||||||
generated](media/9e14217bda4114f5cacbf3edff81616a.png)
|
|
||||||
|
|
||||||
## Create a MCC Node
|
### Create an MCC node in Azure
|
||||||
|
|
||||||
Creating a MCC node is a multi-step process and the first
|
Creating a MCC node is a multi-step process and the first step is to access the MCC private preview management portal.
|
||||||
step is to access the MCC private preview management
|
|
||||||
portal.
|
|
||||||
|
|
||||||
1. After the successful resource creation click on the "Go to resource".
|
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**.
|
||||||
|
|
||||||
| Under Cache Node Management section on the leftmost panel, click on Cache Nodes.  | |
|

|
||||||
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|
|
|
||||||
|
|
||||||
1. On the Cache Nodes blade, click on the Create Cache Node button.
|
3. On the **Cache Nodes** blade, click on the **Create Cache Node** button.
|
||||||
|
|
||||||

|
||||||
generated](media/82874c0364726a752f78793e07e6d477.png)
|
|
||||||
|
|
||||||
1. Clicking the Create Cache Node button will open the Create Cache Node page,
|
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.
|
||||||
Cache Node Name is the only field required for initial cache node creation,
|
|
||||||
but end-user devices will not request content without proper configuration
|
|
||||||
of the other values. The table below describes the information required.
|
|
||||||
|
|
||||||
| **Field Name** | **Expected Value** | **Description** |
|
| **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 cannot be changed later. |
|
| **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 cannot be changed later. |
|
||||||
| **Server Ip Address** | Ipv4 Address | Ip address of your MCC server. Used to route end-user devices in your network to the server for Microsoft content downloads. Please note: IP address must be publicly accessible. |
|
| **Server II Address** | Ipv4 Address | IP address of your MCC server. This is used to route end-user devices in your network to the server for Microsoft content downloads. **The IP address must be publicly accessible.** |
|
||||||
| **Address Range/CIDR Blocks** | Ipv4 CIDR notation | 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 |
|
| **Address Range/CIDR Blocks** | IPv4 CIDR notation | 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 |
|
||||||
| **Enable Cache Node** | Enable/Disable Radio Button | Enable and the cache node will receive content requests. Disable and the cache node will not receive content requests. Cache nodes are enabled by default. |
|
| **Enable Cache Node** | Enable/Disable Radio Button | **Enable** permits the cache node to receive content requests. <br>**Disable** prevents the cache node from receiving content requests. <br>Cache nodes are enabled by default. |
|
||||||
|
|
||||||

|
||||||
generated](media/c27015e77e3e8d14da0ce802a07985b2.png)
|
|
||||||
|
|
||||||
Hovering on the info  next to
|
Hovering on the info  next to
|
||||||
each field will populate the details of that field.
|
each field will populate the details of that field.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||

|
generated](media/5db11e3290c80a5f11ffd8e8b632e866.png)
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user