Merge pull request #212659 from dknappettmsft/avd-troubleshooting-windows-client-logs

AVD added how to collect logs for Windows client

Author: liljack17

articles/virtual-desktop/troubleshoot-client.md

@@ -27,6 +27,51 @@ If that doesn't work, make sure your app group is associated with a workspace.
 
 In this section you'll find troubleshooting guidance for the Remote Desktop client for Windows.
 
+### Access client logs
+
+You might need the client logs when investigating an issue.
+
+To retrieve the client logs:
+
+1. Ensure no sessions are active and the client process isn't running in the background by right-clicking on the **Remote Desktop** icon in the system tray and selecting **Disconnect all sessions**.
+1. Open **File Explorer**.
+1. Navigate to the **%temp%\DiagOutputDir\RdClientAutoTrace** folder.
+
+Below you will find different methods used to read the client logs.
+
+#### Event Viewer
+
+1. Navigate to the Start menu, Control Panel, System and Security, and select **view event logs** under "Windows Tools".
+1. Once the **Event Viewer** is open, click the Action tab at the top and select **Open Saved Log...**.
+1. Navigate to the **%temp%\DiagOutputDir\RdClientAutoTrace** folder and select the log file you want to view.
+1. The **Event Viewer** dialog box will open requesting a response to which it will convert etl format to evtx format. Select **Yes**.
+1. In the **Open Saved Log** dialog box, you have the options to rename the log file and add a description. Select **Ok**.
+1. The **Event Viewer** dialog box will open asking to overwrite the log file. Select **Yes**. This will not overwrite your original etl log file but create a copy in evtx format.
+
+#### Command-line
+
+This method will enable you to convert the log file from etl format to either _csv_ or _xml_ format using the `tracerpt` command. Open the Command Prompt or PowerShell and run the following:
+
+```
+tracerpt "<FilePath>.etl" -o "<OutputFilePath>.extension"
+```
+
+**CSV example:**
+
+```
+tracerpt "C:\Users\admin\AppData\Local\Temp\DiagOutputDir\RdClientAutoTrace\msrdcw_09-07-2022-15-48-44.etl" -o "C:\Users\admin\Desktop\LogFile.csv" -of csv
+```
+
+If the `-of csv` parameter is omitted from the command above, it won't properly convert the file.
+
+**XML example:**
+
+```
+tracerpt "C:\Users\admin\AppData\Local\Temp\DiagOutputDir\RdClientAutoTrace\msrdcw_09-07-2022-15-48-44.etl" -o "C:\Users\admin\Desktop\LogFile.xml"
+```
+
+The `-of xml` parameter is not necessary in this instance as the default output for the conversion is in _xml_ format.
+
 ### Remote Desktop client for Windows stops responding or cannot be opened
 
 If the Remote Desktop client for Windows stops responding or cannot be opened, you may need to reset your client. Starting with version 1.2.790, you can reset the user data from the About page or using a command.
@@ -136,7 +181,7 @@ To resolve this issue, you'll need to either reduce the size of the browser wind
 ## Next steps
 
 - For an overview on troubleshooting Azure Virtual Desktop and the escalation tracks, see [Troubleshooting overview, feedback, and support](troubleshoot-set-up-overview.md).
-- To troubleshoot issues while creating a Azure Virtual Desktop environment and host pool in a Azure Virtual Desktop environment, see [Environment and host pool creation](troubleshoot-set-up-issues.md).
+- To troubleshoot issues while creating an Azure Virtual Desktop environment and host pool in an Azure Virtual Desktop environment, see [Environment and host pool creation](troubleshoot-set-up-issues.md).
 - To troubleshoot issues while configuring a virtual machine (VM) in Azure Virtual Desktop, see [Session host virtual machine configuration](troubleshoot-vm-configuration.md).
 - To troubleshoot issues related to the Azure Virtual Desktop agent or session connectivity, see [Troubleshoot common Azure Virtual Desktop Agent issues](troubleshoot-agent.md).
 - To troubleshoot issues when using PowerShell with Azure Virtual Desktop, see [Azure Virtual Desktop PowerShell](troubleshoot-powershell.md).