Prepare for Remote Desktop Client for Windows End of Support

This notification is critical if you are using Azure Virtual Desktop with the Remote Desktop client for Windows. In September 2024, Microsoft announced the phase-out of the Remote Desktop client for Windows, and now we have an official end-of-support date: the 27th March 2026. To avoid disruptions, you’ll need to migrate users to the Windows App. For additional insights, check out our previous blog post from September 2024: Preparing for Moving to the Windows App.

What’s Changing

On the 27th of March 2026, the Remote Desktop client for Windows will no longer be available for download, nor will it receive any security or feature updates. Microsoft will continue to provide security updates until then. To ensure continuity for your users, you need to migrate them to the Windows App before this end-of-support date.

The Windows App will provide a seamless experience with:

  • Unified access: Access multiple Windows services (Windows 365, Azure Virtual Desktop, and Microsoft Dev Box) from a single, streamlined interface.
  • Enhanced features: Customizable home screens, multi-monitor support, and dynamic display resolutions.
  • Improved remote work experiences: Features such as device redirection, Microsoft Teams optimizations, and easy account switching.

What’s Not Changing

The Remote Desktop Connection (also known as Microsoft Terminal Services Client aka the good old one) will not be affected. Therefore, no action is required for users utilizing this service.

Recommended Actions

To avoid disruptions in accessing remote resources, take the following steps:

  1. Inform users or customers of the change: Notify all your users or if you are a CSP, your customers, about the end-of-support for the Remote Desktop client for Windows.
  2. Use Azure Virtual Desktop Insights: Identify which clients are currently connecting with AVD to manage the transition effectively.
  3. Move to the new Windows App: Ensure you migrate every client until the 27th March 2026.

Detailed Migration Steps

Step 1: Inform Users

Communicate the upcoming changes when migrating to the Windows App. For detailed information, refer to our previous blog post from September 2024: Preparing for Moving to the Windows App.

Step 2: Monitoring And Managing Client Versions Of AVD Users

To effectively monitor, manage and know which client versions are in use, ensure you have the following prerequisites:

  • An existing AVD host pool with session hosts.
  • A log analytics workspace configured to use Azure Virtual Desktop Insights.
  • Active sessions over a period of time to gather data.

To now monitor those client versions, follow these steps:

  1. Sign in to Azure Virtual Desktop Insights: Access the Azure portal at Azure Virtual Desktop Insights.
  2. Select parameters: Choose subscriptions, resource groups, host pools, and a time range; then navigate to the Clients tab.
  3. Review outdated Clients: Look at the summary table to see the highest and oldest version levels of each client found in your environment.

In the example below, the newest version of the Microsoft Remote Desktop Client for Windows (short MSRDC) is 1.2.4487.0, but 993 users are using older versions. Within this table you can see the counts of connections and how many days behind the current version the outdated clients are.

  1. Identify users: Expand a client for detailed information on which users are using outdated versions, their versions, and the date they were last seen connecting with that version. Use the export feature to manage communication with users or to track update propagation.

Regular Review And Updates

Periodically review the client versions to ensure users are up-to-date or already using the Windows App. Note that some clients, such as the Windows App on iOS/iPadOS and Android, are listed with their build number in the report. You can match this build number to the version number in the About section of Windows App settings.

Step 3: Migrate

Follow these steps to migrate users to the Windows App:

  1. Download Windows App: Direct users to download the Windows App from the Microsoft Store or your organization’s software distribution platform (Config Manager or Intune).
  2. Install Windows App: Users should install the application on their devices.
  3. Configure the app: Guide users in configuring the Windows App settings to access their Azure Virtual Desktop and other necessary resources.
  4. Test the setup: Before the final migration, test the new setup to ensure all features work as expected.

Conclusion

Preparing for the end of support for the Remote Desktop client for Windows by the 27th of March 2026 is critical for the continuity and security of your Azure Virtual Desktop services. Migrating to the Windows App not only ensures uninterrupted access but also provides enhanced features and improved remote work experiences.

Additional Resources

For more information and support, refer to the following resources:

You might also like