From c9b986200b5176a40852eab306a86a0cb7acbd0e Mon Sep 17 00:00:00 2001 From: Nidhi Doshi <77081571+doshnid@users.noreply.github.com> Date: Tue, 6 Feb 2024 14:00:58 -0800 Subject: [PATCH 1/5] Update mcc-isp-support.md added resign up and network connectivity issues --- windows/deployment/do/mcc-isp-support.md | 57 ++++++++++++++++++++++-- 1 file changed, 53 insertions(+), 4 deletions(-) diff --git a/windows/deployment/do/mcc-isp-support.md b/windows/deployment/do/mcc-isp-support.md index f3a9c45418..a9ee4b173d 100644 --- a/windows/deployment/do/mcc-isp-support.md +++ b/windows/deployment/do/mcc-isp-support.md @@ -34,14 +34,63 @@ During sign-up, we verify the information you provide against what is present in During sign-up, a verification code is sent to your NOC email address present in [Peering DB](https://www.peeringdb.com/). This code expires in 24 hours. If it's expired, you'll need to request a new verification code to complete the sign-up. +#### Unable to re-sign up + +Please delete any MCC resource that you are using before you resign up for the service. Deleting any existing MCC resource will unlock your ASN which will allow you to successfully sign up. + + + ### Cache Node Errors -#### Cannot find my cache node +#### Network connectivity issues + + Updating Docker’s DNS can help resolve some connectivity issues. + Please try the following Docker DNS updates until one solves your connectivity problem. + Once connectivity is established, there is no need to continue updating Docker’s DNS. + +##### Update Docker’s DNS to use the Google DNS resolver + + nano /etc/docker/daemon.json + + Update the contents of this file to match (below) which includes the public Google DNS resolver + + + + + "log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":["8.8.8.8", "8.8.4.4"] + + +Save and close using the command CTRL-X and then Y(es) to save + +Restart Docker for this change to take effect + + systemctl restart docker + +Rerun the IoT Edge Check command to validate proper connectivity + + iotedge check –verbose + + +##### Update Docker’s DNS to use your company’s DNS resolver + + nano /etc/docker/daemon.json + +Update the contents of this file to match (below) which includes the public Google DNS resolver + + "log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":["”] + + +Save and close using the command CTRL-X and then Y(es) to save + +Restart Docker for this change to take effect + + systemctl restart docker + +Rerun the IoT Edge Check command to validate proper connectivity + + iotedge check –verbose -Did you previously had access to your cache nodes but it's now no longer accessible? If so, it may be because you had a trial subscription, and its trial period ended. To resolve this issue, complete the following two steps: -1. Create a new Azure Pay-As-You-Go subscription -1. Recreate the cache nodes using the new subscription ## Diagnose and Solve Problems From 504a0b3991724e19e954d68632946bb3aa5ce99b Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Wed, 7 Feb 2024 09:18:54 -0800 Subject: [PATCH 2/5] Updated What's new, planned maintenance --- .../whats-new/windows-autopatch-whats-new-2024.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md index b49d11732b..dfd1c2ec2f 100644 --- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md +++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md @@ -1,7 +1,7 @@ --- title: What's new 2024 description: This article lists the 2024 feature releases and any corresponding Message center post numbers. -ms.date: 01/22/2024 +ms.date: 02/07/2024 ms.service: windows-client ms.subservice: itpro-updates ms.topic: whats-new @@ -21,6 +21,12 @@ This article lists new and updated feature releases, and service releases, with Minor corrections such as typos, style, or formatting issues aren't listed. +## February 2024 + +| Message center post number | Description | +| ----- | ----- | +| [MC713365](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Planned Maintenance: Service Improvements | + ## January 2024 ### January feature releases or updates From 203c55e2bcf8c5efdb2b8e7fe618eab0d26c1246 Mon Sep 17 00:00:00 2001 From: tiaraquan Date: Wed, 7 Feb 2024 09:20:44 -0800 Subject: [PATCH 3/5] Forgot subheading --- .../whats-new/windows-autopatch-whats-new-2024.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md index dfd1c2ec2f..e450ef2a41 100644 --- a/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md +++ b/windows/deployment/windows-autopatch/whats-new/windows-autopatch-whats-new-2024.md @@ -23,6 +23,8 @@ Minor corrections such as typos, style, or formatting issues aren't listed. ## February 2024 +## February service releases + | Message center post number | Description | | ----- | ----- | | [MC713365](https://admin.microsoft.com/adminportal/home#/MessageCenter) | Planned Maintenance: Service Improvements | From de0cf9bccf7c06fcfba983e5136fd68ebb6ef5c5 Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 7 Feb 2024 09:31:35 -0800 Subject: [PATCH 4/5] style edits and fix syntax warnings --- windows/deployment/do/mcc-isp-support.md | 101 ++++++++++++----------- 1 file changed, 55 insertions(+), 46 deletions(-) diff --git a/windows/deployment/do/mcc-isp-support.md b/windows/deployment/do/mcc-isp-support.md index a9ee4b173d..0342ee74cc 100644 --- a/windows/deployment/do/mcc-isp-support.md +++ b/windows/deployment/do/mcc-isp-support.md @@ -13,7 +13,7 @@ appliesto: - ✅ Windows 11 - ✅ Windows 10 - ✅ Microsoft Connected Cache for ISPs -ms.date: 12/31/2017 +ms.date: 02/07/2024 --- # Support and troubleshooting @@ -22,7 +22,7 @@ This article provides information on how to troubleshoot common issues with Micr ## Common issues -This section details a few common issues that customers face during the sign up process. +This section details a few common issues that customers face during the sign-up process. ### Sign up errors @@ -36,65 +36,74 @@ During sign-up, a verification code is sent to your NOC email address present in #### Unable to re-sign up -Please delete any MCC resource that you are using before you resign up for the service. Deleting any existing MCC resource will unlock your ASN which will allow you to successfully sign up. +Delete any MCC resource that you're using before you resign up for the service. Deleting any existing MCC resource unlocks your ASN, which allows you to successfully sign up. ### Cache Node Errors #### Network connectivity issues - - Updating Docker’s DNS can help resolve some connectivity issues. - Please try the following Docker DNS updates until one solves your connectivity problem. - Once connectivity is established, there is no need to continue updating Docker’s DNS. - -##### Update Docker’s DNS to use the Google DNS resolver - - nano /etc/docker/daemon.json - - Update the contents of this file to match (below) which includes the public Google DNS resolver - - - - - "log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":["8.8.8.8", "8.8.4.4"] - - + + Updating Docker's DNS can help resolve some connectivity issues. + Try the following Docker DNS updates until one solves your connectivity problem. + Once connectivity is established, there's no need to continue updating Docker's DNS. + +##### Update Docker's DNS to use the Google DNS resolver + +``` +nano /etc/docker/daemon.json +``` + +Update the contents of this file to match the following example, which includes the public Google DNS resolver: + +``` +"log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":["8.8.8.8", "8.8.4.4"] +``` + Save and close using the command CTRL-X and then Y(es) to save -Restart Docker for this change to take effect - - systemctl restart docker - -Rerun the IoT Edge Check command to validate proper connectivity - - iotedge check –verbose +Restart Docker for this change to take effect: + +``` +systemctl restart docker +``` + +Rerun the IoT Edge Check command to validate proper connectivity: + +``` +iotedge check -verbose +``` -##### Update Docker’s DNS to use your company’s DNS resolver - - nano /etc/docker/daemon.json - -Update the contents of this file to match (below) which includes the public Google DNS resolver - - "log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":["”] +##### Update Docker's DNS to use your company's DNS resolver - -Save and close using the command CTRL-X and then Y(es) to save - -Restart Docker for this change to take effect - - systemctl restart docker - -Rerun the IoT Edge Check command to validate proper connectivity - - iotedge check –verbose +``` +nano /etc/docker/daemon.json +``` +Update the contents of this file to match the following example, which includes the public Google DNS resolver: +``` +"log-driver": "json-file", "log-opts": {"max-size": "10m","max-file": "3"},"dns":[""] +``` + +Save and close using the command CTRL-X and then Y(es) to save. + +Restart Docker for this change to take effect: + +``` +systemctl restart docker +``` + +Rerun the IoT Edge Check command to validate proper connectivity: + +``` +iotedge check -verbose +``` ## Diagnose and Solve Problems -If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your MCC resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users may face as they onboard. +If this article isn't resolving the issue you're facing with your cache node, you can use the **Diagnose and solve problems** functionality within your MCC resource to continue troubleshooting. **Diagnose and solve problems** contains solutions to most common problems that users might face as they onboard. You can find **Diagnose and solve problems** on the left pane within your MCC resource. @@ -106,7 +115,7 @@ Within **Diagnose and solve problems**, select **Troubleshoot** under the type o ## Steps to obtain an Azure subscription ID -To onboard onto Microsoft Connected Cache, you will need an Azure subscription ID. Follow the steps below to obtain your subscription ID: +To onboard onto Microsoft Connected Cache, you'll need an Azure subscription ID. Use the following steps to obtain your subscription ID: [!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)] From f6c53f663716e7f3e74c24c08a0a59a2b90cec1c Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Wed, 7 Feb 2024 09:33:41 -0800 Subject: [PATCH 5/5] edit --- windows/deployment/do/mcc-isp-support.md | 1 - 1 file changed, 1 deletion(-) diff --git a/windows/deployment/do/mcc-isp-support.md b/windows/deployment/do/mcc-isp-support.md index 0342ee74cc..83f96cb12e 100644 --- a/windows/deployment/do/mcc-isp-support.md +++ b/windows/deployment/do/mcc-isp-support.md @@ -39,7 +39,6 @@ During sign-up, a verification code is sent to your NOC email address present in Delete any MCC resource that you're using before you resign up for the service. Deleting any existing MCC resource unlocks your ASN, which allows you to successfully sign up. - ### Cache Node Errors #### Network connectivity issues