Merge pull request #251424 from dknappettmsft/patch-1

AVD Agent troubleshooting add EXPIRED_MACHINE_TOKEN

Author: prmerger-automator[bot]

articles/virtual-desktop/troubleshoot-agent.md

@@ -42,11 +42,11 @@ To resolve this issue, start the RDAgent boot loader:
 
 1. Select **Refresh**.
 
-1. If the service stops after you started and refreshed it, you may have a registration failure. For more information, see [INVALID_REGISTRATION_TOKEN](#error-invalid_registration_token).
+1. If the service stops after you started and refreshed it, you may have a registration failure. For more information, see [INVALID_REGISTRATION_TOKEN or EXPIRED_MACHINE_TOKEN](#error-invalid_registration_token-or-expired_machine_token).
 
-## Error: INVALID_REGISTRATION_TOKEN
+## Error: INVALID_REGISTRATION_TOKEN or EXPIRED_MACHINE_TOKEN
 
-On your session host VM, go to **Event Viewer** > **Windows Logs** > **Application**. If you see an event with ID 3277 with **INVALID_REGISTRATION_TOKEN** in the description, the registration token that has been used isn't recognized as valid.
+On your session host VM, go to **Event Viewer** > **Windows Logs** > **Application**. If you see an event with ID 3277 with **INVALID_REGISTRATION_TOKEN** or **EXPIRED_MACHINE_TOKEN** in the description, the registration token that has been used isn't recognized as valid.
 
 To resolve this issue, create a valid registration token:
 
@@ -157,7 +157,7 @@ To resolve this issue:
 
 1. Make sure [the agent can connect to the broker](#error-agent-cannot-connect-to-broker-with-invalid_form).
 
-1. Make sure [your VM has a valid registration token](#error-invalid_registration_token).
+1. Make sure [your VM has a valid registration token](#error-invalid_registration_token-or-expired_machine_token).
 
 1. Make sure [the VM registration token hasn't expired](./faq.yml).