From 7c76c570c7af9b9990fd86384763bb201dcb6413 Mon Sep 17 00:00:00 2001 From: jcaparas Date: Mon, 9 May 2016 16:34:58 +1000 Subject: [PATCH] Update other-troubleshooting.md --- windows/keep-secure/other-troubleshooting.md | 50 ++++++++++---------- 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/windows/keep-secure/other-troubleshooting.md b/windows/keep-secure/other-troubleshooting.md index d27dfcbced..fadf6fb93d 100644 --- a/windows/keep-secure/other-troubleshooting.md +++ b/windows/keep-secure/other-troubleshooting.md @@ -86,22 +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 - ``` + 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 - ``` + 4. A success message is displayed. Verify the change by entering the following command and press **Enter**: - - ``` + sc qc sense - ``` + **Check that the service is running from the command line:** @@ -112,20 +111,20 @@ 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 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 - ``` + 4. A success message is displayed. Verify the change by entering the following command and press **Enter**: - ``` + 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. @@ -143,21 +142,21 @@ 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 - ``` + 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 - ``` + 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:** @@ -182,21 +181,22 @@ 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 - ``` + 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 - ``` + 4. 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