update images

windows/keep-secure/other-troubleshooting.md

@@ -86,15 +86,22 @@ Check the startup type from the command line:
 
   b.  Right-click **Command prompt** and select **Run as administrator**.
 
-2. Enter the following command and press **Enter**: sc qc sense
-
+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
+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:
 
@@ -104,15 +111,22 @@ Check that the service is running from the command line:
 
   b.  Right-click **Command prompt** and select **Run as administrator**.
 
-2. Enter the following command and press **Enter**: sc query sense
-
+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
+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.
@@ -129,16 +143,24 @@ Check the startup type from the command line:
 
   b.  Right-click **Command prompt** and select **Run as administrator**.
 
-2.  Enter the following command and press **Enter**: sc qc diagtrack
-
+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
+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:
@@ -161,15 +183,23 @@ Check that the service is running from the command line:
 
   b.  Right-click **Command prompt** and select **Run as administrator**.
 
-2.  Enter the following command and press **Enter**: sc query diagtrack
-
+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
+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
+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
 

windows/keep-secure/troubleshoot-onboarding-windows-defender-advanced-threat-protection.md

@@ -19,6 +19,132 @@ author: iaanw
 
 You might need to troubleshoot the onboarding process if you encounter issues.
 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
 ## Add users to an Azure Active Directory
 If you don't see any users in the [Azure Management Portal](https://manage.windowsazure.com/) during the service onboarding stage, you might need to add users to the directory first.