From b3e4c14a26402e671d625a3f1a85f5db66256a6c Mon Sep 17 00:00:00 2001 From: jcaparas Date: Mon, 9 May 2016 16:28:43 +1000 Subject: [PATCH] Update other-troubleshooting.md --- windows/keep-secure/other-troubleshooting.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/windows/keep-secure/other-troubleshooting.md b/windows/keep-secure/other-troubleshooting.md index 124db33fce..d27dfcbced 100644 --- a/windows/keep-secure/other-troubleshooting.md +++ b/windows/keep-secure/other-troubleshooting.md @@ -102,6 +102,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:** 1. Open an elevated command-line prompt on the endpoint: @@ -125,6 +126,7 @@ 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 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. @@ -161,9 +163,9 @@ There are two ways to check the startup type for the service: from the command l 1. Open the services console: - a. Click **Start** and type **services**. - - b. Press **Enter** to open the console. + a. Click **Start** and type **services**. + + b. Press **Enter** to open the console. 2. Scroll through the list of services until you find **Connected User Experiences and Telemetry**.