Situatie

In 2025, Microsoft will implement significant changes to its Remote Desktop Protocol (RDP) ecosystem, with a particular focus on the deprecation of the Remote Desktop client (Microsoft Store version) and the transition to other solutions. As RDP plays a crucial role in enterprise IT environments, administrators must prepare for these changes to maintain secure and efficient remote access to critical resources. Below is a comprehensive overview of what administrators need to know, with a technical focus on migrating away from legacy solutions.

End of Support for Remote Desktop App (Microsoft Store Version)

Effective May 27, 2025, Microsoft will officially discontinue the Remote Desktop app from the Microsoft Store. This app, which has served as the main method for Windows clients to connect to remote desktops, will no longer be supported for remote access to services such as Azure Virtual Desktop (AVD), Windows 365, and Microsoft Dev Box.

From a technical standpoint, administrators must ensure that users who rely on this app transition to an alternative solution before support ends. The Remote Desktop app has several limitations, including:

• Dependency on the Microsoft Store and lack of advanced customization capabilities for enterprise use.

• Incompatibility with custom configurations such as custom Group Policies or RDP settings at the enterprise level.

To facilitate a smooth transition, Microsoft recommends moving users to the Windows App for accessing RDP-based services. This solution integrates better into enterprise ecosystems and offers the following advantages:

1. Centralized Management via Microsoft Endpoint Manager (Intune):

   • The Windows App can be centrally managed via Intune, allowing for deployment and policy enforcement at scale.

   • Administrators can configure device redirection policies and enforce RDP security configurations at a granular level using Mobile Device Management (MDM) and Mobile Application Management (MAM).

2. Enhanced Security and Compliance:

   • The Windows App supports Windows Hello for Business authentication and Multi-Factor Authentication (MFA), improving security during remote access sessions.

   • It integrates seamlessly with Azure Active Directory (Azure AD) for seamless user provisioning and identity management.

   • Administrators can apply conditional access policies to ensure only compliant devices can initiate remote desktop sessions.

3. Advanced Networking Features:

   • The Windows App supports automatic VPN detection and direct routing for secure connectivity.

   • It integrates WAN optimization features, improving remote session performance over fluctuating network conditions.

4. Customizable Deployment Options:

   • Windows App supports configurations for custom RDP file settings, allowing for more flexibility in deployment across different user groups or organizational departments.

   • Integration with Azure Virtual Desktop (AVD) and Windows 365 enables simplified session launching, reducing the need for manual configuration of RDP settings.

End of Support for Remote Desktop Client (MSI Version)

In addition to the Microsoft Store version, the standalone Remote Desktop client for Windows (MSI) will be deprecated as of March 27, 2026. While this client is still in use across many enterprises, its eventual obsolescence requires careful planning for a migration strategy. Key technical considerations include:

• Deprecation of Support for Legacy RDP Protocols:

  • Organizations using custom RDP configurations tied to the MSI version must update their deployments to the Windows App or other Microsoft-supported RDP solutions.

  • Any use of custom RDP file configurations will need to be migrated or reconfigured in the new app.

• Compatibility Testing:

  • For organizations that leverage the MSI RDP client with third-party RDP servers or custom load balancing configurations, comprehensive testing is required to ensure full compatibility with the Windows App.

  • Testing should include performance analysis, network load distribution, and failover mechanisms.

Traditional RDP (MSTSC) Support Continues

The legacy Remote Desktop Connection (MSTSC) tool will remain supported beyond 2025 and will continue to be a viable method for connecting to Windows servers or other RDP-enabled systems in environments where more complex configurations are unnecessary. However, MSTSC lacks the management and security benefits that come with the Windows App and Intune integration.

For enterprises relying on on-premises RDP servers or systems that do not yet use cloud-based solutions (such as Azure Virtual Desktop), MSTSC may still be the preferred option for basic RDP connectivity.

Action Steps for Administrators: A Detailed Technical Migration Guide

1. Assess Existing RDP Infrastructure:

   • Identify all systems using the Microsoft Store app and the MSI client for remote access, including server configurations and VPNs.

   • Evaluate the network configurations, authentication requirements, and third-party integrations that will be impacted by the deprecation of the Microsoft Store app.

2. Plan Transition to the Windows App:

   • Roll out the Windows App using Microsoft Endpoint Manager (Intune) for streamlined deployment and policy management.

   • Configure RDP settings, including device redirection, audio/video settings, and resource sharing policies via Intune to ensure compatibility with organizational requirements.

3. Test Compatibility and Performance:

   • Perform pilot migrations with a small group of users, testing network latency, VPN performance, and resource access under real-world conditions.

   • Test compatibility with applications that rely on RDP for remote access, ensuring that custom configurations (such as session broker configurations or multi-session handling) are supported in the new app.

4. Configure Centralized Security Controls:

   • Implement conditional access policies to restrict remote desktop access to compliant devices.

   • Enable Microsoft Defender for Endpoint for device protection and integrate with Microsoft Sentinel for continuous security monitoring of RDP connections.

5. Migrate Users and Monitor Usage:

   • Migrate users in phases to reduce service disruption. Provide training and support resources to ensure a smooth transition.

   • Continuously monitor the performance and security of the migration process using Microsoft 365 Admin Center and Azure AD logs.

6. Decommission Legacy RDP Clients:

   • Once the migration is complete, decommission legacy MSI RDP clients and Microsoft Store app installations.

   • Archive any data associated with legacy RDP solutions for compliance or future auditing requirements.

Solutie

Tip solutie

Permanent