deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

edit spacing

Browse Source
This commit is contained in:
Joey Caparas
2016-05-09 14:50:10 +10:00
parent 486134f784
commit 795fe9c38f
1 changed files with 6 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
windows/keep-secure/other-troubleshooting.md
View File

@ -22,13 +22,6 @@ You might need to troubleshoot the onboarding process if you encounter issues.
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.
Go through the following verification topics to address this issue:
- [Ensure that the endpoint is onboarded successfully](#Ensure-that-the-endpoint-is-onboarded-successfully)
- [Ensure that the Windows Defender ATP service is enabled](#Ensure-that-the-Windows-Defender-ATP-service-is-enabled)
- [Ensure that the telemetry and diagnostics service is enabled](#Ensure-that-the-telemetry-and-diagnostics-service-is-enabled)
- [Ensure that the Windows Defender ATP endpoint has internet connection](#Ensure-that-the-Windows-Defender-ATP-endpoint-has-internet-connection)
### 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.
@ -44,7 +37,7 @@ If the endpoints aren't reporting correctly, you might need to check that the Wi
5. Check that the **OnboardingState** value is set to **1**.
![Image of OnboardingState status in Registry Editor](images/onbaordingstate.png)
![Image of OnboardingState status in Registry Editor](images/onboardingstate.png)
If the **OnboardingState** value is not set to **1**, follow the instructions on **Identifying and addressing onboarding issues**.
@ -77,6 +70,7 @@ Event ID | Message | Resolution steps
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**
1. Open an elevated command-line prompt on the endpoint:
a. Click **Start** and type **cmd**.
@ -104,6 +98,7 @@ If the endpoints aren't reporting correctly, you might need to check that the Wi
```
**Check that the service is running from the command line**
1. Open an elevated command-line prompt on the endpoint:
a. Click **Start** and type **cmd**.