From 88467f7295a2f20e43d6a55f23a7420961103f57 Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 4 Mar 2022 16:44:22 -0800 Subject: [PATCH] formatting --- windows/deployment/do/mcc-enterprise.md | 62 +++++++-------- windows/deployment/do/mcc-isp.md | 101 ++++++++++-------------- 2 files changed, 73 insertions(+), 90 deletions(-) diff --git a/windows/deployment/do/mcc-enterprise.md b/windows/deployment/do/mcc-enterprise.md index baeb48caa8..5e5ad4be12 100644 --- a/windows/deployment/do/mcc-enterprise.md +++ b/windows/deployment/do/mcc-enterprise.md @@ -55,7 +55,7 @@ If an MCC node is unavailable, the client will pull content from CDN to ensure u -![eMCC emg01](images/emcc01.png) +![eMCC img01](images/emcc01.png) 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 -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] > [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 1. On the Azure Portal home page, choose **Create a resource**: - ![eMCC emg02](images/emcc02.png) + ![eMCC img02](images/emcc02.png) 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. - ![eMCC emg03](images/emcc03.png) - ![eMCC emg04](images/emcc04.png) + ![eMCC img03](images/emcc03.png) + ![eMCC img04](images/emcc04.png) 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] > Your MCC resource must not contain the word **Microsoft** in it. - ![eMCC emg05](images/emcc05.png) + ![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 emg06](images/emcc06.png) + ![eMCC img06](images/emcc06.png) #### 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**. - To resolve this error, go to the previous step and choose **(US) West US**. - ![eMCC emg07](images/emcc07.png) + ![eMCC img07](images/emcc07.png) ### 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**. 2. Under **Cache Node Management** section on the leftmost panel, click on **Cache Nodes**. - ![eMCC emg08](images/emcc08.png) + ![eMCC img08](images/emcc08.png) 3. On the **Cache Nodes** blade, click on the **Create Cache Node** button. - ![eMCC emg09](images/emcc09.png) + ![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. @@ -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. -![eMCC emg9.5](images/emcc09.5.png) +![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 emg10](images/emcc10.png) +![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 emg11](images/emcc11.png) +![eMCC img11](images/emcc11.png) ### 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. - ![eMCC emg12](images/emcc12.png) + ![eMCC img12](images/emcc12.png) 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 - ![eMCC emg13](images/emcc13.png) + ![eMCC img13](images/emcc13.png) > [!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**. @@ -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. - ![eMCC emg14](images/emcc14.png) + ![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 emg15](images/emcc15.png) + ![eMCC img15](images/emcc15.png) 5. Decide whether you would like to use dynamic or static address for the Eflow VM - ![eMCC emg16](images/emcc16.png) + ![eMCC img16](images/emcc16.png) > [!NOTE] > 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. - ![eMCC emg17](images/emcc17.png) + ![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 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”** - ![eMCC emg18](images/emcc18.png) - ![eMCC emg19](images/emcc19.png) + ![eMCC img18](images/emcc18.png) + ![eMCC img19](images/emcc19.png) 9. Your MCC deployment is now complete. @@ -328,7 +328,7 @@ sudo -s iotedge list ``` -![eMCC emg20](images/emcc20.png) +![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 @@ -342,11 +342,11 @@ wget [http://\/mscomtest/wuidt.gif?cacheHostOrigin=au.download.w A successful test result will look like this: -![eMCC emg21](images/emcc21.png) +![eMCC img21](images/emcc21.png) OR -![eMCC emg22](images/emcc22.png) +![eMCC img22](images/emcc22.png) 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: -![eMCC emg23](images/emcc23.png) +![eMCC img23](images/emcc23.png) ### Common Issues @@ -385,7 +385,7 @@ Connect-EflowVm sudo iotedge list​ ``` -![eMCC emg24](images/emcc24.png) +![eMCC img24](images/emcc24.png) 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: -![eMCC emg25](images/emcc25.png) +![eMCC img25](images/emcc25.png) 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. - ![eMCC emg26](images/emcc26.png) + ![eMCC img26](images/emcc26.png) **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. - ![eMCC emg27](images/emcc27.png) + ![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 emg28](images/emcc28.png) + ![eMCC img28](images/emcc28.png) - Looking at the Delivery Optimization Activity Monitor - ![eMCC emg29](images/emcc29.png) + ![eMCC img29](images/emcc29.png) ## Also see diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md index 3d8a67bb82..b6fb3e57f6 100644 --- a/windows/deployment/do/mcc-isp.md +++ b/windows/deployment/do/mcc-isp.md @@ -102,102 +102,85 @@ For questions regarding these instructions contact [msconnectedcache@microsoft.c ## 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 -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 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. -##### Use the following link and log in to Azure +Use the following link to sign in to Azure: -- Choose Create a resource - ![Graphical user interface, application Description automatically - generated](media/a29a93bb4eee0abcb1917c1b4ff23ad0.png) +1. Choose **Create a resource** -- Type " MCC" into the search box and be sure to hit the - Enter key to show search results. + ![eMCC img02](images/imcc02.png) -- Select “MCC” and select “Create” on the next screen to - start the process of creating the MCC resource. +2. Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results. - ![image](media/9f714d147e4c90275f8db945b3532ec5.png) +3. Select **Microsoft Connected Cache** and choose **Create** on the next screen to start the process of creating the MCC resource. - ![](media/ca8bd090d3d37246f99143691fabf3a2.png) + ![iMCC img03](images/imcc03.png) + ![iMCC img04](images/imcc04.png) -- Fill in the required fields to create the MCC - resource. +4. Fill in the required fields to create the MCC 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 - resource group and choose a name for your resource group. - - - 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. + > [!NOTE] + > Your MCC resource will not be created properly if you do not select **(US) West US** - Choose a name for the MCC resource. - ![Graphical user interface, text, application, email Description - automatically generated](media/0485f6efd6fb9c2ff4ac19a70298e322.png) + ![iMCC emg05](images/imcc05.png) -- Once all the information has been entered, click on the “Review + Create” - button. Once validation is complete, click the “Create” button to start the - resource creation. - ![Text, email Description automatically - generated](media/43b78ec34612279e209c137f99b0d699.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. -##### Error: Validation failed + ![iMCC img06](images/imcc06.png) -- If you get a Validation failed error message on your portal, it is likely - because you selected the Location as US West 2. +#### Error: Validation failed -- 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**. -![Graphical user interface, text, application, email Description automatically -generated](media/9e14217bda4114f5cacbf3edff81616a.png) + ![iMCC img07](images/imcc07.png) -## Create a MCC Node +### Create an MCC node in Azure -Creating a MCC node is a multi-step process and the first -step is to access the MCC private preview management -portal. +Creating a 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". +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. ![Graphical user interface, text, application Description automatically generated](media/2067264f71c854b7ce281c2f0d0478b2.png) | | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---| + ![iMCC img08](images/imcc08.png) -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. -![Graphical user interface, application Description automatically -generated](media/82874c0364726a752f78793e07e6d477.png) + ![iMCC img09](images/imcc09.png) -1. Clicking the Create Cache Node button will open the Create Cache Node page, - 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. +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 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. | -| **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. | +| **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 | +| **Enable Cache Node** | Enable/Disable Radio Button | **Enable** permits the cache node to receive content requests.
**Disable** prevents the cache node from receiving content requests.
Cache nodes are enabled by default. | -![Graphical user interface, application Description automatically -generated](media/c27015e77e3e8d14da0ce802a07985b2.png) + ![iMCC img10](images/imcc10.png) Hovering on the info ![](media/1b3a2ef4f5575feb1b68fc14074a1e08.png) next to each field will populate the details of that field. + ![iMCC img11](images/imcc11.png) + ![Graphical user interface, text, application, email Description automatically generated](media/5db11e3290c80a5f11ffd8e8b632e866.png)