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

Update other-troubleshooting.md

Browse Source
This commit is contained in:
jcaparas
2016-05-06 17:51:05 +10:00
parent 1a81f7ba9d
commit 7aa2d47a23
1 changed files with 0 additions and 115 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -9,118 +9,3 @@ ms.sitesec: library
author: mjcaparas
---
# Troubleshoot Windows Defender Advanced Threat Protection onboarding issues two
**Applies to:**
- Windows 10 Insider Preview
<span style="color:#ED1C24;">[Some information relates to pre-released product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.]</span>
You might need to troubleshoot the onboarding process if you encounter issues.
## Endpoints not reporting 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), then this might indicate endpoint onboarding or a connectivity issue that you need to address.
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
### Ensure that the Windows Defender ATP service is enabled
### Ensure that the 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:**
1. Open an elevated command-line prompt on the endpoint:
a. Click **Start** and type **cmd**.
b. Right-click **Command prompt** and select **Run as administrator**.
2. Enter the following command and press **Enter**.
```
sc qc diagtrack
```
3. If the service is enabled, it will be set to automatically start. The result should look like the following:
![Result of the sc query command for diagtrack](images/windefatp-sc-qc-diagtrack.png)
4. If the **START_TYPE** is not set to **AUTO_START**, then you'll need to enter the following command and press **Enter**:
```
sc config diagtrack start=auto
```
5. A success message is displayed. Verify the change by entering the following command and press **Enter**:
```
sc qc diagtrack
```
**Check the startup type in the services console:**
1. Open the services console:
a. Click **Start** and type **services**. Press **Enter** to open the console.
2. Scroll through the list of services until you find **Connected User Experiences and Telemetry**.
3. Check the **Startup type** column - the service should be set as **Automatic**.
ASK ALON HOW SET TO AUTOMATIC IF IT'S NOT SET FROM THE CONSOLE.
**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**.
b. Right-click **Command prompt** and select **Run as administrator**.
2. Enter the following command and press **Enter**.
```
sc query diagtrack
```
3. If the service is running, the result should look like the following:
![Result of the sc query command for sc query diagtrack](images/windefatp-sc-query-diagtrack.png)
4. If the service STATE is not set to RUNNING, then you'll need to enter the following command and press **Enter**:
```
sc start diagtrack
```
5. A success message is displayed. Verify the change by entering the following command and press **Enter**:
```
sc query diagtrack
```
### 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.
WinHTTP is independent of the Internet browsing proxy settings and other user context applications and must be able to detect the proxy servers that are available in your particular environment.
To ensure that sensor has service connectivity, follow the steps described in the [Verify client connectivity to Windows Defender ATP service URLs](configure-proxy-internet-windows-defender-advanced-threat-protection.md#
Verify-client-connectivity-to-Windows-Defender-ATP-service-URLs) topic.
If the verification fails and your environment is using a proxy to connect to the internet, then follow the steps described in [Configure proxy and Internet connectivity settings](configure-proxy-internet-windows-defender-advanced-threat-protection.md#) topic.