Windows Server 2022 Support Status (October 2026)
Windows Server 2022 reached the end of mainstream support on 13 October 2026, and remains in extended support until 14 October 2031. This means Microsoft continues to provide security updates, although mainstream support has ended. Administrators can still use Remote Desktop on existing Windows Server 2022 installations, provided they maintain appropriate security controls. For new deployments, Windows Server 2025 is worth considering.
For official support dates, consult the Microsoft Windows Server 2022 Lifecycle documentation .
Why Would You Enable Remote Desktop on Windows Server 2022?
Remote Desktop Protocol (RDP) is a powerful tool for accessing Windows servers from remote locations. It allows administrators to perform system maintenance, deploy applications, and troubleshoot issues without physical access to the server. By default, Remote Desktop is disabled on Windows Server 2022 for security purposes, necessitating deliberate configuration to enable and secure the feature.
RDP also simplifies collaboration by enabling IT teams to work on the same server environment simultaneously. Additionally, businesses with distributed workforces depend on RDP for efficient access to centralised systems, boosting productivity while reducing infrastructure costs.
Planning a New Windows Server Deployment?
Windows Server 2022 remains supported through October 2031, but Windows Server 2025 is the more recent Long-Term Servicing Channel (LTSC) release. For new installations, IT teams should evaluate Windows Server 2025 based on application compatibility, licensing requirements and long-term support planning.
If you are deploying the newer version, follow our guide to enabling Remote Desktop on Windows Server 2025 for the corresponding configuration steps.
What Are The Methods to Enable Remote Desktop?
There are several ways to enable Remote Desktop in Windows Server 2022, depending on your administrative preferences. For standard remote administration, you can enable RDP through Server Manager or PowerShell without installing additional server roles. Remote Desktop Services (RDS) is a separate option for organisations that need to provide multiple users with access to published applications or desktops.
Enabling Remote Desktop via the Server Manager (GUI)
Step 1: Launch Server Manager
The Server Manager is the default interface for managing Windows Server roles and features. Open it by:
- Clicking the Start Menu and selecting Server Manager.
- Alternatively, use the Windows + R key combination, type ServerManager, and press Enter.
Step 2: Access Local Server Settings
Once in Server Manager:
- Navigate to the Local Server tab in the left-hand menu.
- Locate the "Remote Desktop" status, which typically shows "Disabled."
Step 3: Enable Remote Desktop
- Click on "Disabled" to open the System Properties window in the Remote tab.
- Select Allow remote connections to this computer.
- For enhanced security, check the box for Network Level Authentication (NLA), requiring users to authenticate before accessing the server.
Step 4: Configure Firewall Rules
- When prompted, allow Windows Defender Firewall to enable the necessary Remote Desktop rules.
- Verify that RDP traffic is permitted on TCP port 3389 for the appropriate network profiles and trusted source addresses.
- Do not expose port 3389 directly to the public internet. For remote connections outside the local network, use a secure VPN or Remote Desktop Gateway (RD Gateway) instead.
Step 5: Add Authorized Users
- By default, only administrators can connect. Click Select Users... to add non-administrator accounts.
- Use the Add Users or Groups dialog to specify usernames or groups.
Enabling Remote Desktop via PowerShell
Step 1: Open PowerShell as Administrator
- Use the Start Menu to search for PowerShell.
- Right-click and select Run as Administrator.
Step 2: Enable Remote Desktop via Registry
- Run the following command to modify the registry key controlling RDP access:
- Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name "fDenyTSConnections" -Value 0
Step 3: Open the Necessary Firewall Port
- Allow RDP traffic through the firewall with:
- Enable-NetFirewallRule -DisplayGroup "Remote Desktop"
Step 4: Test Connectivity
- Use PowerShell’s built-in networking tools to verify:
-
Test-NetConnection -ComputerName
-Port 3389
When Do You Need Remote Desktop Services (RDS)?
Remote Desktop Services (RDS) is not required for standard administrative RDP connections. Windows Server 2022 allows administrators to enable Remote Desktop directly through Server Manager or PowerShell.
However, organizations that need to deliver Windows applications or shared desktop sessions to multiple users may require an RDS deployment. This involves installing the appropriate RDS roles, configuring Remote Desktop licensing with the required Client Access Licenses (RDS CALs), and managing user access through the relevant RDS components.
For basic server administration, the methods described above are sufficient.
How Can You Secure Remote Desktop Access?
While enabling Remote Desktop Protocol (RDP) On Windows Server 2022 provides convenience, it can also introduce potential security vulnerabilities. Cyber threats like brute-force attacks, unauthorized access, and ransomware often target unsecured RDP setups. This section outlines best practices to secure your RDP configuration and protect your server environment.
Enable Network Level Authentication (NLA)
Network Level Authentication (NLA) is a security feature that requires users to authenticate before a remote session is established.
Why Enable NLA?
- It minimizes exposure by ensuring only authorised users can connect to the server.
- NLA reduces the risk of brute-force attacks by blocking unauthenticated users from consuming server resources.
How to Enable NLA
- In the System Properties window under the Remote tab, check the box for Allow connections only from computers running Remote Desktop with Network Level Authentication.
- Ensure client devices support NLA to avoid compatibility issues.
Restrict User Access
Limiting who can access the server via RDP is a critical step in securing your environment.
Best Practices for User Restrictions
- Remove Default Accounts: Disable or rename the default Administrator account to make it harder for attackers to guess credentials.
- Use the Remote Desktop Users Group: Add specific users or groups to the Remote Desktop Users group. Avoid granting remote access to unnecessary accounts.
- Audit User Permissions: Regularly review which accounts have RDP access and remove outdated or unauthorized entries.
Enforce Strong Password Policies
Passwords are the first line of defence against unauthorised access. Weak passwords can compromise even the most secure systems.
Key Elements of a Strong Password Policy
- Length and Complexity: Require passwords to be at least 12 characters long, including uppercase letters, lowercase letters, numbers, and special characters.
- Password Changes : Require password resets when credentials are compromised or suspected of being exposed, rather than enforcing automatic changes every 60–90 days without a specific security requirement.
- Account Lockout Settings: Implement account lockout after a certain number of failed login attempts to deter brute-force attacks.
How to Configure Policies
-
Use Local Security Policy or Group Policy to enforce password rules:
- Navigate to Computer Configuration > Windows Settings > Security Settings > Account Policies > Password Policy.
- Adjust settings such as minimum password length, complexity requirements, and account lockout thresholds according to your organization's security policies.
Restrict IP Addresses
Restricting RDP access to known IP ranges limits potential attack vectors.
How to Restrict IPs
- Open Windows Defender Firewall with Advanced Security.
-
Create an Inbound Rule for RDP
port 3389
):
- Specify the rule applies only to traffic from trusted IP ranges.
- Block all other inbound traffic to RDP.
Benefits of IP Restrictions
- Drastically reduces exposure to attacks from unknown sources.
- Provides an additional layer of security, especially when combined with VPNs.
Implement Two-Factor Authentication (2FA)
Two-Factor Authentication adds an extra layer of protection by requiring users to verify their identity with something they know (password) and something they have (e.g., a mobile app or hardware token).
Setting Up 2FA for RDP
- Use a dedicated RDP-compatible two-factor authentication solution to add an extra verification step to remote connections.
- For Microsoft-based environments, Microsoft Entra multifactor authentication can be integrated with Remote Desktop Services through RD Gateway, Network Policy Server (NPS), and the NPS extension for Microsoft Entra ID. Microsoft Authenticator can then serve as an authentication method, but it does not enable MFA for standard RDP connections on its own.
Why Use 2FA?
- Even if a password is compromised, 2FA prevents unauthorized access.
- It significantly enhances security without compromising user convenience.
How Can You Test and Use Remote Desktop?
After successfully enabling Remote Desktop Protocol (RDP) on your Windows Server 2022, the next critical step is testing the setup. This ensures connectivity and verifies that the configuration works as expected. Additionally, understanding how to access the server from various devices—regardless of the operating system—is essential for a seamless user experience.
Testing Connectivity
Testing the connection ensures the RDP service is active and accessible over the network.
Step 1: Use the Built-in Remote Desktop Connection Tool
On a Windows machine:
- Open the Remote Desktop Connection tool by pressing Windows + R, typing mstsc, and pressing Enter.
- Enter the server's IP address or hostname in the Computer field.
Step 2: Authenticate
- Input the username and password of an account authorised for remote access.
- If using Network Level Authentication (NLA), ensure the credentials match the required security level.
Step 3: Test the Connection
- Click Connect and verify that the remote desktop session initializes without errors.
- Troubleshoot connectivity issues by checking the firewall, network configurations, or server status.
Accessing from Different Platforms
Once Remote Desktop is enabled on Windows Server 2022, administrators can connect from Windows, macOS, Linux and mobile devices. The appropriate client depends on the operating system.
Windows: Remote Desktop Connection or Windows App
Windows includes the built-in
Remote Desktop Connection
client (
mstsc
), which remains a straightforward option for connecting directly to Windows Server 2022.
-
Press Windows + R, type
mstscTSplus vs RDS - Enter the server's hostname or IP address.
- Select Connect and authenticate using an authorised account.
Microsoft also offers Windows App , which replaces several older Remote Desktop applications. However, Windows App on Windows does not currently support all traditional Remote Desktop Services connection scenarios. The built-in Remote Desktop Connection client remains appropriate for direct administrative RDP access.
macOS: Windows App
Windows App replaces the former Microsoft Remote Desktop application on macOS.
- Download Windows App from the Mac App Store.
- Open the application and select Add PC.
- Enter the Windows Server 2022 hostname or IP address.
- Configure display settings, credentials and other preferences as needed.
- Open the saved connection to access the server.
Linux: RDP Clients Like Remmina
Linux users can continue using RDP-compatible clients such as Remmina.
- Install Remmina through the distribution's package manager.
- Create a connection using the RDP protocol.
- Enter the server's hostname or IP address and authorised credentials.
- Connect to the remote desktop.
Mobile Devices: Windows App for iOS and Android
Microsoft's Windows App is available for iOS, iPadOS and Android, replacing the older Microsoft Remote Desktop applications.
On iOS or iPadOS, install the Windows App from the App Store. On Android, download it from Google Play.
Open the application, add a PC connection, enter the server details and authenticate using an account with Remote Desktop permissions.
Troubleshooting Common Issues
Connectivity Errors
- Check that port 3389 is open in the firewall.
- Confirm the server is accessible via a ping test from the client device.
Authentication Failures
- Verify the username and password are correct.
- Ensure the user account is listed in the Remote Desktop Users group.
Session Performance
- Reduce display resolution or disable resource-intensive features (e.g., visual effects) to improve performance on low-bandwidth connections.
Explore Advanced Remote Access with TSplus
For IT professionals seeking advanced solutions, TSplus Remote Access offers unparalleled functionality. From enabling multiple concurrent connections to seamless application publishing and enhanced security features, TSplus is designed to meet the demands of modern IT environments. Streamline your remote desktop management today by visiting TSplus .
Conclusion
Enabling Remote Desktop on Windows Server 2022 is a critical skill for IT administrators, ensuring efficient remote management and collaboration. This guide has walked you through multiple methods to enable RDP, secure it, and optimise its usage for professional environments. With robust configurations and security practices, Remote Desktop can transform server management by providing accessibility and efficiency.
TSplus Remote Access Free Trial
Ultimate Citrix/RDS alternative for desktop/app access. Secure, cost-effective, on-premises/cloud