From bda376105fbc756081dafe82d18f37bc78770f2e Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Fri, 31 May 2024 17:02:54 -0700 Subject: [PATCH 1/3] Acrolinx: Correctness --- windows/deployment/do/mcc-enterprise-deploy.md | 2 +- windows/deployment/do/waas-delivery-optimization-reference.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/do/mcc-enterprise-deploy.md b/windows/deployment/do/mcc-enterprise-deploy.md index 3d6b94c78f..6b09effa10 100644 --- a/windows/deployment/do/mcc-enterprise-deploy.md +++ b/windows/deployment/do/mcc-enterprise-deploy.md @@ -228,7 +228,7 @@ Installing MCC on your Windows device is a simple process. A PowerShell script p 1. 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 how many cores you would like to allocate for the VM. For this example, we chose the default values for download path, install path, and virtual hard disk path. :::image type="content" source="./images/installation-info-4.png" alt-text="Screenshot of multiple installer questions about memory and storage for EFLOW." lightbox="./images/installation-info-4.png"::: - For more information, see [Sizing Recommendations](mcc-enterprise-prerequisites.md#sizing-recommendations) for memory, virtual storage, and CPU cores. For this example we chose the recommend values for a Branch Office/Small Enterprise deployment. + For more information, see [Sizing Recommendations](mcc-enterprise-prerequisites.md#sizing-recommendations) for memory, virtual storage, and CPU cores. For this example we chose the recommended values for a Branch Office/Small Enterprise deployment. :::image type="content" source="./images/memory-storage-5.png" alt-text="Screenshot of multiple installer questions about memory and storage." lightbox="./images/memory-storage-5.png"::: :::image type="content" source="./images/external-switch-1.jpg" alt-text="Screenshot of a sample output of ipconfig command showing example of subnet mask." lightbox="./images/external-switch-1.jpg"::: + :::image type="content" source="./images/assigning-ip-2.png" alt-text="Screenshot of multiple installer questions about ipv4 address for Eflow." lightbox="./images/assigning-ip-2.png"::: If you would like to use your own DNS server instead of Google DNS 8.8.8.8, select **n** and set your own DNS server IP. + :::image type="content" source="./images/use-custom-dns-3.png" alt-text="Screenshot of multiple installer questions about setting an alternate DNS server." lightbox="./images/use-custom-dns-3.png"::: + If you use a dynamic IP address, the DHCP server will automatically configure the IP address and DNS settings. 1. 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 how many cores you would like to allocate for the VM. For this example, we chose the default values for download path, install path, and virtual hard disk path. + :::image type="content" source="./images/installation-info-4.png" alt-text="Screenshot of multiple installer questions about memory and storage for EFLOW." lightbox="./images/installation-info-4.png"::: + For more information, see [Sizing Recommendations](mcc-enterprise-prerequisites.md#sizing-recommendations) for memory, virtual storage, and CPU cores. For this example we chose the recommended values for a Branch Office/Small Enterprise deployment. + :::image type="content" source="./images/memory-storage-5.png" alt-text="Screenshot of multiple installer questions about memory and storage." lightbox="./images/memory-storage-5.png"::: 1. When the installation is complete, you should see the following output (the values below will be your own) - :::image type="content" source="./images/ent-mcc-script-complete.png" alt-text="Screenshot of the installer script displaying the completion summary in PowerShell." lightbox="./images/ent-mcc-script-complete.png"::: + + :::image type="content" source="./images/ent-mcc-script-complete.png" alt-text="Screenshot of the installer script displaying the completion summary in PowerShell." lightbox="./images/ent-mcc-script-complete.png"::: + :::image type="content" source="./images/installation-complete-7.png" alt-text="Screenshot of expected output when installation is complete." lightbox="./images/installation-complete-7.png"::: 1. Your MCC deployment is now complete. + If you don't see any errors, continue to the next section to validate your MCC deployment. Your VM will not appear in Hyper-V Manager as it is an EFLOW VM. - After validating your MCC is properly functional, 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. - If you had errors during your deployment, see the [Common Issues](#common-issues) section in this article. @@ -286,7 +297,7 @@ A successful test result will display a status code of 200 along with additional :::image type="content" source="./images/ent-mcc-verify-server-ssh.png" alt-text="Screenshot of a successful wget with an SSH client." lightbox="./images/ent-mcc-verify-server-ssh.png"::: - :::image type="content" source="./images/ent-mcc-verify-server-powershell.png" alt-text="Screenshot of a successful wget using PowerShell." lightbox="./images/ent-mcc-verify-server-powershell.png"::: +:::image type="content" source="./images/ent-mcc-verify-server-powershell.png" alt-text="Screenshot of a successful wget using PowerShell." lightbox="./images/ent-mcc-verify-server-powershell.png"::: Similarly, enter the following URL from a browser in the network: @@ -312,9 +323,9 @@ If you're seeing errors similar to this error: `The term Get- isn't r 1. 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 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) + **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 @@ -339,7 +350,7 @@ This command will provide the current status of the starting, stopping of a cont > [!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've listed a few issues that we encountered during our internal validation. -> + ### DNS needs to be configured @@ -355,48 +366,48 @@ To configure the device to work with your DNS, use the following steps: 1. Use `ifconfig` to find the appropriate NIC adapter name. - ```bash - ifconfig - ``` + ```bash + ifconfig + ``` 1. Run `nmcli device show ` to show the DNS name for the ethernet adapter. For example, to show DNS information for **eno1**: - ```bash - nmcli device show eno1 - ``` + ```bash + nmcli device show eno1 + ``` - :::image type="content" source="images/mcc-isp-nmcli.png" alt-text="Screenshot of a sample output of nmcli command to show network adapter information." lightbox="./images/mcc-isp-nmcli.png"::: + :::image type="content" source="images/mcc-isp-nmcli.png" alt-text="Screenshot of a sample output of nmcli command to show network adapter information." lightbox="./images/mcc-isp-nmcli.png"::: 1. Open or create the Docker configuration file used to configure the DNS server. - ```bash - sudo nano /etc/docker/daemon.json - ``` + ```bash + sudo nano /etc/docker/daemon.json + ``` 1. Paste the following string into the **daemon.json** file, and include the appropriate DNS server address. For example, in the previous screenshot, `IP4.DNS[1]` is `10.50.10.50`. - ```bash - { "dns": ["x.x.x.x"]} - ``` + ```bash + { "dns": ["x.x.x.x"]} + ``` 1. Save the changes to daemon.json. If you need to change permissions on this file, use the following command: - ```bash - sudo chmod 555 /etc/docker/daemon.json - ``` + ```bash + sudo chmod 555 /etc/docker/daemon.json + ``` 1. Restart Docker to pick up the new DNS setting. Then restart IoT Edge. - ```bash - sudo systemctl restart docker - sudo systemctl daemon-reload - sudo restart IoTEdge - ``` + ```bash + sudo systemctl restart docker + sudo systemctl daemon-reload + sudo restart IoTEdge + ``` ### Resolve DNS issues Follow these steps if you see a DNS error when trying to resolve hostnames during the provisioning or download of container: -Run ``` Get-EflowVmEndpoint ``` to get interface name +Run `Get-EflowVmEndpoint` to get interface name Once you get the name: