Restoring original section with variable removed. Formatting changes.

Author: Heidilohr

articles/virtual-desktop/agent-updates-diagnostics.md

@@ -3,7 +3,7 @@ title: Set up diagnostics for monitoring agent updates
 description: How to set up diagnostic reports to monitor agent updates.
 author: Sefriend
 ms.topic: how-to
-ms.date: 01/23/2023
+ms.date: 01/31/2023
 ms.author: sefriend
 manager: rkiran
 ---
@@ -26,6 +26,28 @@ To enable sending diagnostic logs to your Log Analytics workspace:
 > [!NOTE]
 > The log query results only cover the last 30 days of data in your deployment.
 
+## Use diagnostics to see when an update becomes available
+
+To see when agent component updates are available: 
+
+1. Access the logs in your Log Analytics workspace.
+
+2. Select the **+** button to create a new query.
+
+3. Copy and paste the following Kusto query to see if agent component updates are available for the specified session host. Make sure to change the **sessionHostName** parameter to the name of your session host.
+
+    > [!NOTE]
+    > If you haven't enabled the Scheduled Agent Updates feature, you won't see anything in the NewPackagesAvailable field.
+
+    ```kusto
+    WVDAgentHealthStatus 
+    | where TimeGenerated >= ago(30d) 
+    | where SessionHostName == "sessionHostName" 
+    | project TimeGenerated, AgentVersion, SessionHostName, LastUpgradeTimeStamp, UpgradeState, UpgradeErrorMsg
+    | sort by TimeGenerated desc
+    | take 1
+    ```
+
 ## Use diagnostics to see when agent updates are happening
 
 To see when agent updates are happening or to make sure that the Scheduled Agent Updates feature is working: 
@@ -36,14 +58,14 @@ To see when agent updates are happening or to make sure that the Scheduled Agent
 
 3. Copy and paste the following Kusto query to see when the agent has updated for the specified session host. Make sure to change the **sessionHostName** parameter to the name of your session host.
 
-```kusto
-WVDAgentHealthStatus 
-| where TimeGenerated >= ago(30d) 
-| where SessionHostName == "sessionHostName" 
-| project TimeGenerated, AgentVersion, SessionHostName, LastUpgradeTimeStamp, UpgradeState, UpgradeErrorMsg 
-| summarize arg_min(TimeGenerated, *) by AgentVersion 
-| sort by TimeGenerated asc 
-``` 
+    ```kusto
+    WVDAgentHealthStatus 
+    | where TimeGenerated >= ago(30d) 
+    | where SessionHostName == "sessionHostName" 
+    | project TimeGenerated, AgentVersion, SessionHostName, LastUpgradeTimeStamp, UpgradeState, UpgradeErrorMsg 
+    | summarize arg_min(TimeGenerated, *) by AgentVersion 
+    | sort by TimeGenerated asc 
+    ``` 
 
 ## Use diagnostics to check for unsuccessful agent updates
 
@@ -55,14 +77,14 @@ To check if an agent component update was unsuccessful:
 
 3. Copy and paste the following Kusto query to see when the agent has updated for the specified session host. Make sure to change the **sessionHostName** parameter to the name of your session host.
 
-```kusto
-WVDAgentHealthStatus 
-| where TimeGenerated >= ago(30d) 
-| where SessionHostName == "sessionHostName"
-| where MaintenanceWindowMissed == true
-| project TimeGenerated, AgentVersion, SessionHostName, LastUpgradeTimeStamp, UpgradeState, UpgradeErrorMsg, MaintenanceWindowMissed
-| sort by TimeGenerated asc 
-``` 
+    ```kusto
+    WVDAgentHealthStatus 
+    | where TimeGenerated >= ago(30d) 
+    | where SessionHostName == "sessionHostName"
+    | where MaintenanceWindowMissed == true
+    | project TimeGenerated, AgentVersion, SessionHostName, LastUpgradeTimeStamp, UpgradeState, UpgradeErrorMsg, MaintenanceWindowMissed
+    | sort by TimeGenerated asc 
+    ``` 
 
 ## Next steps