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

remove ```

Browse Source
This commit is contained in:
Joey Caparas 2016-05-09 17:06:10 +10:00
parent 5273d5b205
commit 31fcd89097
1 changed files with 54 additions and 53 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -69,9 +69,9 @@ If the endpoints aren't reporting correctly, you might need to check that the Wi
Event ID | Message | Resolution steps
:---|:---|:---
5 | Windows Advanced Threat Protection service failed to connect to the server at _variable_| Ensure that the Windows Defender ATP endpoint has internet access.
5 | Windows Advanced Threat Protection service failed to connect to the server at _variable_ | Ensure that the Windows Defender ATP endpoint has internet access.
6 | Windows Advanced Threat Protection service failed to read the onboarding parameters. Failure code: _variable_ | Run the onboarding script again.
7 | Windows Advanced Threat Protection service failed to read the onboarding parameters. Failure code: _variable_| Ensure that the Windows Defender ATP endpoint has internet access, then run the onboarding script again.
7 | Windows Advanced Threat Protection service failed to read the onboarding parameters. Failure code: _variable_ | Ensure that the Windows Defender ATP endpoint has internet access, then run the onboarding script again.
15 | Windows Advanced Threat Protection cannot start command channel with URL: _variable_ | Ensure that the Windows Defender ATP endpoint has internet access.
### Ensure that the Windows Defender ATP service is enabled
@ -86,20 +86,21 @@ If the endpoints aren't reporting correctly, you might need to check that the Wi
b. Right-click **Command prompt** and select **Run as administrator**.
2. Enter the following command and press **Enter**:
```
sc qc sense
```
sc qc sense
If the the service is running, then the result should look like the following screenshot:
![Result of the sq query sense command](images/sc-query-sense-autostart.png)
3. If the service **START_TYPE** is not set to **AUTO_START**, then you'll need to enter the following command and press **Enter**:
```
sc config sense start=auto
```
sc config sense start=auto
4. A success message is displayed. Verify the change by entering the following command and press **Enter**:
```
sc qc sense
```
sc qc sense
**Check that the service is running from the command line:**
@ -110,20 +111,20 @@ sc qc sense
b. Right-click **Command prompt** and select **Run as administrator**.
2. Enter the following command and press **Enter**.
```
sc query sense
```
sc query sense
If the service is running, the result should look like the following screenshot:
![Result of the sc query sense command](images/sc-query-sense-running.png)
3. If the service **STATE** is not set to **RUNNING**, then you'll need to enter the following command and press **Enter**:
```
sc start sense
```
sc start sense
4. A success message is displayed. Verify the change by entering the following command and press **Enter**:
```
sc qc sense
```
sc qc sense
### 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.
@ -141,20 +142,20 @@ There are two ways to check the startup type for the service: from the command l
b. Right-click **Command prompt** and select **Run as administrator**.
2. Enter the following command and press **Enter**.
```
sc qc diagtrack
```
sc qc diagtrack
If the service is enabled, then the result should look like the following screenshot:
![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
```
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
```
sc qc diagtrack
**Check the startup type in the services console:**
@ -179,16 +180,16 @@ ASK ALON HOW SET TO AUTOMATIC IF IT'S NOT SET FROM THE CONSOLE.
b. Right-click **Command prompt** and select **Run as administrator**.
2. Enter the following command and press **Enter**.
```
sc query diagtrack
```
sc query diagtrack
If the service is running, the result should look like the following screenshot:
![Result of the sc query command for sc query diagtrack](images/windefatp-sc-query-diagtrack.png)
3. If the service **STATE** is not set to **RUNNING**, then you'll need to enter the following command and press **Enter**:
```
sc start diagtrack
```
sc start diagtrack
4. A success message is displayed. Verify the change by entering the following command and press **Enter**:
sc query diagtrack