fix header

This commit is contained in:
Joey Caparas
2016-05-09 14:53:53 +10:00
parent 795fe9c38f
commit 5f50a3a7b1

View File

@ -18,14 +18,14 @@ author: mjcaparas
You might need to troubleshoot the onboarding process if you encounter issues.
##Endpoints not reporting to the service correctly
## Endpoints not reporting to the service correctly
If you have completed the endpoint onboarding process and don't see endpoints in the [Machines view](investigate-machines-windows-defender-advanced-threat-protection.md) after 20 minutes, it might indicate an endpoint onboarding or a connectivity problem.
### Ensure that the endpoint is onboarded successfully
If the endpoints aren't reporting correctly, you might need to check that the Windows Defender Advanced Threat Protection service was successfully onboarded on the endpoint.
**Check the onboarding state in Registry**
**Check the onboarding state in Registry:**
1. Click **Start**.
@ -41,7 +41,7 @@ If the endpoints aren't reporting correctly, you might need to check that the Wi
If the **OnboardingState** value is not set to **1**, follow the instructions on **Identifying and addressing onboarding issues**.
**Identifying and addressing onboarding errors**
**Identifying and addressing onboarding errors:**
1. Click **Start**.
@ -69,7 +69,7 @@ Event ID | Message | Resolution steps
### Ensure that the Windows Defender ATP service is enabled
If the endpoints aren't reporting correctly, you might need to check that the Windows 10 Windows Defender Advanced Threat Protection service is enabled on the endpoint.
**Check the startup type from the command line**
**Check the startup type from the command line:**
1. Open an elevated command-line prompt on the endpoint:
@ -97,7 +97,7 @@ If the endpoints aren't reporting correctly, you might need to check that the Wi
sc qc sense
```
**Check that the service is running from the command line**
**Check that the service is running from the command line:**
1. Open an elevated command-line prompt on the endpoint:
@ -125,14 +125,14 @@ If the endpoints aren't reporting correctly, you might need to check that the Wi
sc qc sense
```
###Ensure that telemetry and diagnostics service is enabled
### Ensure that telemetry and diagnostics service is enabled
If the endpoints aren't reporting correctly, you might need to check that the Windows 10 telemetry and diagnostics service is enabled on the endpoint. The service may have been disabled by other programs or user configuration changes.
You will need to check the startup type and verify that the service is running.
There are two ways to check the startup type for the service: from the command line or in the services console.
**Check the startup type from the command line**:
**Check the startup type from the command line:**
1. Open an elevated command-line prompt on the endpoint:
@ -201,7 +201,7 @@ ASK ALON HOW SET TO AUTOMATIC IF IT'S NOT SET FROM THE CONSOLE.
sc query diagtrack
```
###Ensure that the Windows Defender ATP endpoint has internet connection**
### Ensure that the Windows Defender ATP endpoint has internet connection
The Window Defender ATP sensor requires Microsoft Windows HTTP (WinHTTP) to be able to report telemetry and communicate with the Windows Defender ATP service.