deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 05:47:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

style edits and fix syntax warnings

Browse Source
This commit is contained in:
Meghan Stewart 2024-02-07 09:31:35 -08:00
parent 6784ea6a72
commit de0cf9bccf
1 changed files with 55 additions and 46 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

101
windows/deployment/do/mcc-isp-support.md
View File

@ -13,7 +13,7 @@ appliesto:
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 11</a>
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
- ✅ <a href=https://learn.microsoft.com/windows/deployment/do/waas-microsoft-connected-cache target=_blank>Microsoft Connected Cache for ISPs</a>
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":["<Your companies DNS Resolver IP Address>”]
##### 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":["<Your companies DNS Resolver IP Address>"]
```
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:
<!--Using include file, get-azure-subscription.md, for shared content-->
[!INCLUDE [Get Azure subscription](includes/get-azure-subscription.md)]