From e8412d86a0b2a0c2e6018ddce02c4e083bcbc8ce Mon Sep 17 00:00:00 2001 From: greg-lindsay Date: Fri, 11 Mar 2022 11:52:35 -0800 Subject: [PATCH] add slugs --- windows/deployment/do/TOC.yml | 4 ++- windows/deployment/do/mcc-enterprise.md | 24 ++++++------- windows/deployment/do/mcc-isp.md | 34 +++++++++---------- .../do/waas-microsoft-connected-cache.md | 2 +- 4 files changed, 33 insertions(+), 31 deletions(-) diff --git a/windows/deployment/do/TOC.yml b/windows/deployment/do/TOC.yml index c41c247f33..1bf29210da 100644 --- a/windows/deployment/do/TOC.yml +++ b/windows/deployment/do/TOC.yml @@ -32,9 +32,11 @@ - name: Resources items: + - name: Set up Delivery Optimization for Windows + href: delivery-optimization-setup.md - name: Delivery Optimization reference href: waas-delivery-optimization-reference.md - name: Delivery Optimization client-service communication href: delivery-optimization-workflow.md - name: Using a proxy with Delivery Optimization - href: delivery-optimization-proxy.md \ No newline at end of file + href: delivery-optimization-proxy.md diff --git a/windows/deployment/do/mcc-enterprise.md b/windows/deployment/do/mcc-enterprise.md index 6628dfb70d..86cac31bd1 100644 --- a/windows/deployment/do/mcc-enterprise.md +++ b/windows/deployment/do/mcc-enterprise.md @@ -244,18 +244,18 @@ Files contained in the mccinstaller.zip file: 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] @@ -322,7 +322,7 @@ 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 @@ -336,7 +336,7 @@ You should see MCC, edgeAgent, and edgeHub running. If you see edgeAgent or edge For a validation of properly functioning MCC, execute the following command in the EFLOW VM or any device in the network. Replace \ with the IP address of the cache server. -``` +```powershell wget [http://\/mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com]() ``` @@ -380,7 +380,7 @@ If you're seeing errors similar to this: “The term ‘Get-Something’ isn't r 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​ ``` @@ -389,7 +389,7 @@ 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: -``` +```bash sudo journalctl -u iotedge -f ``` @@ -399,7 +399,7 @@ For example, this command will provide the current status of the starting, stopp Use this command to check the IoT Edge Journal -``` +```bash sudo journalctl -u iotedge –f ``` @@ -417,7 +417,7 @@ To run this script: 2. Run the following commands: -``` +```powershell Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope Process .\collectMccDiagnostics.ps1 ``` @@ -432,11 +432,11 @@ Throughout the private preview phase, we will send you security and feature upda Run the following command with the **arguments** we provided in the email to update your MCC: -``` +```powershell # .\updatemcc.ps1 version="**\**" tenantid="**\**" customerid="**\**" cachenodeid="**\**" 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” ``` @@ -513,7 +513,7 @@ You can either set your MCC IP address or FQDN using: 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 ``` diff --git a/windows/deployment/do/mcc-isp.md b/windows/deployment/do/mcc-isp.md index adcd37f7aa..5a7999d53e 100644 --- a/windows/deployment/do/mcc-isp.md +++ b/windows/deployment/do/mcc-isp.md @@ -277,7 +277,7 @@ Installing MCC on your physical server or VM is a straightforward process. A Bas 4. Open a terminal and change the access permissions to execute on the **installmcc.sh** Bash script file using chmod. - ``` + ```bash sudo chmod +x installmcc.sh ``` @@ -329,7 +329,7 @@ will need to provision a new one. Sign in to the Connected Cache server or ssh and run the following command from a terminal to see the running modules (containers): -``` +```bash sudo iotedge list​ ``` @@ -337,7 +337,7 @@ sudo iotedge list​ If **edgeAgent** and **8edgeHub** containers are listed, but not “MCC”, you may view the status of the IoTEdge security manager using the command: -``` +```bash sudo journalctl -u iotedge -f ``` @@ -351,7 +351,7 @@ It can take a few minutes for the container to deploy. For a validation of properly functioning MCC, run the following command in the terminal of the cache server or any device in the network. Replace \ with the IP address of the cache server. -``` +```bash wget http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com ``` @@ -361,7 +361,7 @@ A successful test result will look like this: Similarly, enter the following URL into a web browser on the network: -``` +```http http:///mscomtest/wuidt.gif?cacheHostOrigin=au.download.windowsupdate.com ``` @@ -374,7 +374,7 @@ If the test fails, see the [common issues](#common-issues) section below for mor Use the following command to check the IoT Edge Journal: -``` +```bash sudo journalctl -u iotedge –f ``` @@ -382,7 +382,7 @@ sudo journalctl -u iotedge –f Run the following IoT Edge setup/install state check: -``` +```bash sudo iotedge check --verbose ``` @@ -394,13 +394,13 @@ Follow the steps below to configure the device to work with your DNS: 1. Use ifconfig to find appropriate NIC adapter name. - ``` + ```bash ifconfig​ ``` 2. Run nmcli device show \ to show you the DNS name for Ethernet adapter. For example to show DNS information for eno1: - ``` + ```bash nmcli device show eno1 ``` @@ -408,24 +408,24 @@ Follow the steps below to configure the device to work with your DNS: 3. Open/create the Docker configuration file used to configure the DNS server - ``` + ```bash sudo nano /etc/docker/daemon.json​ ``` 4. Paste the following into the daemon.json file (In the example above IP4.DNS[1] is used) - ``` + ```bash { "dns": ["x.x.x.x"]} ``` 5. Save the file changes to daemon.json. **Note**: You might need to change permissions on this file. For example: - ``` + ```bash sudo chmod 555 /etc/docker/daemon.json​ ``` 6. Restart Docker (to pick up the new DNS) and restart IoTEdge - ``` + ```bash sudo systemctl restart dockersudo systemctl daemon-reloadsudo restart IoTEdge ``` @@ -441,7 +441,7 @@ To run this script: 2. Run the following commands: - ``` + ```bash sudo chmod +x collectMccDiagnostics.sh sudo ./collectMccDiagnostics.sh ``` @@ -455,14 +455,14 @@ Throughout the private preview phase, we will send you security and feature upda Run the following commands with the **arguments** we provided in the email to update your MCC: -``` +```bash sudo chmod +x updatemcc.sh sudo chmod +x installIoTEdge.sh sudo ./updatemcc.sh version="\<**VERSION**\>" tenantid="\<**TENANTID**\>" customerid="\<**CUSTOMERID**\>" cachenodeid="\<**CACHENODEID**\>" customerkey="\<**CUSTOMERKEY**\>" ``` For example: -``` +```bash sudo ./updatemcc.sh version="msconnectedcacheprod.azurecr.io/mcc/linux/iot/mcc-ubuntu-iot-amd64:1.2.1.981" tenantid="799a999aa-99a1-99aa-99aa-9a9aa099db99" customerid="99a999aa-99a1-99aa-99aa-9aaa9aaa0saa" cachenodeid=" aa99aaaa-999a-9aas-99aa99daaa99 " customerkey="a99d999a-aaaa-aa99-0999aaaa99aa” ``` @@ -481,7 +481,7 @@ The **uninstallmcc.sh** script will remove the following: To run the script, enter the following commands: -``` +```bash sudo chmod +x uninstallmcc.sh sudo ./uninstallmcc.sh ``` diff --git a/windows/deployment/do/waas-microsoft-connected-cache.md b/windows/deployment/do/waas-microsoft-connected-cache.md index 9e3a3d47b1..9126dea4e9 100644 --- a/windows/deployment/do/waas-microsoft-connected-cache.md +++ b/windows/deployment/do/waas-microsoft-connected-cache.md @@ -57,7 +57,7 @@ See the following diagram. ![MCC Overview](images/waas-mcc-diag-overview.png#lightbox) For more information about MCC, see the following articles: -- [Microsoft Connected Cache for Enterprises](mcc-enterprise.md) +- [Microsoft Connected Cache for Enterprise and Education](mcc-enterprise.md) - [Microsoft Connected Cache for ISPs](mcc-isp.md) ## Also see