formatting

2025-06-18 11:53:37 +00:00 · 2022-03-04 13:14:29 -08:00
parent b7450c4059
commit 5d8c40ab16
1 changed files with 120 additions and 163 deletions
--- a/windows/deployment/do/mcc-enterprise.md
+++ b/windows/deployment/do/mcc-enterprise.md
@ -114,7 +114,7 @@ For questions regarding these instructions contact [msconnectedcache@microsoft.c
 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.
+> [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.
 For information about creating or locating your subscription ID, see [Steps to obtain an Azure Subscription ID](#steps-to-obtain-an-azure-subscription-id).
@ -122,138 +122,113 @@ For information about creating or locating your subscription ID, see [Steps to o
 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 and sign in to Azure
 <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**:  
    ![eMCC emg02](images/emcc02.png)
-2.  Type "Microsoft Connected Cache" into the search box and be sure to hit the
+2.  Type **Microsoft Connected Cache** into the search box, and hit **Enter** to show search results.
    Enter key to show search results.
-    **NOTE:**
+> [!NOTE]
 > You will not see Microsoft Connected Cache in the drop-down list. You need to type it and press enter to see the result.
-    **You will not see Microsoft Connected Cache in the drop down box, you need
+3.  Select **Microsoft Connected Cache** and choose **Create** on the next screen to start the process of creating the MCC resource.
    to type it and press enter to see the result**
 3.  Select “Microsoft Connected Cache” and select “Create” on the next screen to
    start the process of creating the MCC resource.
    ![eMCC emg03](images/emcc03.png)
    ![eMCC emg04](images/emcc04.png)
 4.  Fill in the required fields to create the MCC resource.
-4.  Fill in the required fields to create the MCC
+    -   Choose the subscription that you provided to Microsoft.
-    resource.
+    -   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.
-    -   Choose the subscription provided to Microsoft.
+       > [!NOTE]
-
+       > Your MCC resource will not be created properly if you do not select **(US) West US**
    -   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.
        **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.
+      > Your MCC resource must not contain the word **Microsoft** in it.
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;![eMCC emg05](images/emcc05.png)
+      ![eMCC emg05](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
 5.  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.
    ![eMCC emg06](images/emcc06.png)
    ![eMCC emg06](images/emcc06.png)
 #### Error: Validation failed
-   If you get a Validation failed error message on your portal, it is likely
+-   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**.
-    because you selected the Location as US West 2 or another location.
+-   To resolve this error, go to the previous step and choose **(US) West US**.
 -   To bypass this error, navigate to the previous step and choose (US) West US.
    ![eMCC emg07](images/emcc07.png)
 ### 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.
-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.
    ![eMCC emg08](images/emcc08.png)
-
+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.
    ![eMCC emg09](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.
 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. |
+| **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 on the Create button.
+5.  Enter the information for the **Cache Node** and click the **Create** button.
 ![eMCC emg9.5](images/emcc09.5.png)
 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
+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.
 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 doc can be found at the [Install Connected Cache](#install-mcc-on-windows) section.
 ![eMCC emg10](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.
+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)
 ### Install MCC on Windows
-Installing MCC on your Windows machine is a
+Installing MCC on your Windows device is a simple process. A PowerShell script performs the following tasks:
 straightforward 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
+  - 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.
    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
+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)
 Files contained in the mccinstaller.zip file:
-   installmcc.ps1: Main installer 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.
+  - **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.
+  - **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.
+  - **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.
+  - **updatemcc.ps1**: The update script used to upgrade MCC to a particular version.
-   mccupdate.json: Used as part of the update script
+  - **mccupdate.json**: Used as part of the update script
 1.  Open Windows PowerShell as administrator and navigate to the location of these files.
@ -269,95 +244,80 @@ Files contained in the mccinstaller.zip file:
 1. Enable Nested Virtualization
-Set -VMProcessor -VMName **\<"VM name"\>** -ExposeVirtualizationExtensions \$true
+  ```
-
+  Set -VMProcessor -VMName "VM name" -ExposeVirtualizationExtensions \$true
  ```
 2. Enable Mac Spoofing
-
+  ```
-  Get-VMNetworkAdapter -VMName **\<"VM name"\>**\| Set-VMNetworkAdapter \-MacAddressSpoofing On
+  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
  ```
  Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process
-
+  ```
-    **NOTE:**
+  > [!NOTE]
-
+  >  After setting the execution policy, you will see a warning asking if you wish to change the execution policy. Choose **[A] Yes to All**.
    After setting the execution policy, you will see the following message: **Execution Policy Change**. Select **\[A\] Yes to all** to proceed.
    The execution policy helps protect you from scripts that you do not trust.
    Changing the execution policy might expose you to the security risks described in the about_Execution_Policies help topic at https:/go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the  execution policy?
    [Y] Yes **[A] Yes to All** [N] No [L] No to All [S] Suspend [?] Help
    (default is "N"):
 4.  Copy the command from the portal and run it in Windows PowerShell
    ![eMCC emg13](images/emcc13.png)
-    **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.
+  > <br>
-
+  > <br>Security warning
-    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>
-    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
+  > <br>[D] Do not run **[R] Run once** [S] Suspend [?] Help (default is "D"):
    C:\\Users\\mccinstaller\\Eflow\\installmcc.ps1?
    [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 are creating a new switch.
-    **NOTE:**
+  > [!NOTE]
-
+  > Restarting your computer after creating a switch is recommended. You will notice network delays during installation if the computer has not been restarted.
    Restarting your computer after creating a switch is recommended. You will 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 emg14](images/emcc14.png)
-4.  Re-run the script after the restart. This time, select “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.
    ![eMCC emg15](images/emcc15.png)
 5.  Decide whether you would like to use dynamic or static address for the Eflow VM
    ![eMCC emg16](images/emcc16.png)
  > [!NOTE]
  > Choosing a dynamic IP address might assign a different IP address when the MCC restarts.
- > A static IP address is recommended so you do not have to change this value in your management solution when 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 will 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
+6.  Choose where you would like to download, install, and store the virtual hard disk for EFLOW. You will 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
 7.  Follow the Azure Device Login link and sign into the Azure Portal.
    ![eMCC emg17](images/emcc17.png)
-8.  If this is your first MCC deployment, please select ‘n’ so that we can create a new IoT Hub. If you have already configured MCC before, we want to group your MCCs in the same IoT Hub, select “y”.
+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”**
    ![eMCC emg18](images/emcc18.png)
    ![eMCC emg19](images/emcc19.png)
-9.  Your MCC deployment is now complete
+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
+    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, visit the [Troubleshooting](#troubleshooting) section in this document
+    3.  If you had errors during your deployment, visit the [Troubleshooting](#troubleshooting) section in this article.
 ### Verify proper functioning MCC server
 #### Verify Client Side
-Let’s connect to the EFLOW VM and check if MCC is properly running
+Connect to the EFLOW VM and check if MCC is properly running:
 1.  Open PowerShell as an Administrator
 2.  Enter the following commands:
@ -420,16 +380,18 @@ If you are seeing errors similar to this: “The term ‘Get-Something’ is not
 Connect to the Connected Cache server and check the list of running IoT Edge modules using the following commands:
 ```
 Connect-EflowVm
 sudo iotedge list
-
+```
 ![eMCC emg24](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:
 ```
 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:  
@ -437,7 +399,9 @@ For example, this command will provide the current status of the starting, stopp
 Use this command to check the IoT Edge Journal
 ```
 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.
@ -453,12 +417,12 @@ To run this script:
 2.  Run the following commands:
-    "Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process"
+```
-
+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
+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”)
    “**\<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.
@ -526,20 +490,11 @@ For more information on Azure IoT Edge, please see the [Azure IoT Edge documenta
 ### EFLOW
-[What is Azure IoT Edge for Linux on Windows \| Microsoft
+- [What is Azure IoT Edge for Linux on Windows](/azure/iot-edge/iot-edge-for-linux-on-windows?view=iotedge-2018-06&preserve-view=true)
-Docs](https://docs.microsoft.com/azure/iot-edge/iot-edge-for-linux-on-windows?view=iotedge-2018-06&preserve-view=true)
+- [Install Azure IoT Edge for Linux on Windows](/azure/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric?view=iotedge-2018-06&tabs=azure-portal%2Cpowershell#install-iot-edge)
-
+- [PowerShell functions for Azure IoT Edge for Linux on Windows](https://docs.microsoft.com/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions?view=iotedge-2018-06)
-[Install Azure IoT Edge for Linux on Windows \| Microsoft
+- 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)
-Docs](https://docs.microsoft.com/azure/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric?view=iotedge-2018-06&tabs=azure-portal%2Cpowershell#install-iot-edge)
+- [Now ready for Production: Linux IoT Edge Modules on Windows - YouTube](https://www.youtube.com/watch?v=pgqVCg6cxVU&ab_channel=MicrosoftIoTDevelopers)
 [PowerShell functions for Azure IoT Edge for Linux on Windows \| Microsoft
 Docs](https://docs.microsoft.com/azure/iot-edge/reference-iot-edge-for-linux-on-windows-functions?view=iotedge-2018-06)
 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
@ -552,18 +507,20 @@ There are multiple methods that can be used to apply a policy to PCs that should
 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]
+    [HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization]<br>
    "DOCacheHost"=" "  
-    From an elevated PowerShell or command shell:  
+  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
+    reg add "HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Windows\\DeliveryOptimization" /v DOCacheHost /t REG_SZ /d "10.137.187.38" /f
  ```
 1.  MDM Path in 1809 or higher:
 1.  MDM Path in 1809 or higher-
  .Vendor/MSFT/Policy/Config/DeliveryOptimization/DOCacheHost
-2.  In build 1809 (RS5) and higher 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 by Group Policy setting 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.
    ![eMCC emg26](images/emcc26.png)