olly - Fotolia

Tip

How to troubleshoot an RDP remote session stuck at configuring

Admins forced to troubleshoot a Microsoft RDP session getting stuck at configuration must understand these key steps to fix their issue and be able to adapt these steps to their environment.

One problem that virtual desktop administrators often encounter is that the Microsoft remote desktop protocol is stuck at configuring a remote Windows session.

This problem can occur in Windows versions dating back to Windows 7 and Windows Server 2008, but it can also occur in newer Windows versions, including Windows 10 and Windows Server 2019. The problem can occur regardless of whether Microsoft Terminal Server is in use.

The main symptom of the problem is that it's impossible to establish a remote desktop connection to a Windows server, terminal server or virtual desktop session.

Unfortunately, there are a variety of problems that can cause errors which will result in Microsoft remote desktops' connection being stuck configuring remote sessions. As such, there is no universal quick fix for the problem. As a virtual desktop admin, you typically have to use trial and error to resolve the issue, so you should use some of the following methods to determine what the cause of their issue is.

1. Address memory shortages

One potential cause of errors when Microsoft remote desktop protocol (RDP) is stuck configuring remote sessions is that the target server or virtual desktop is running low on memory. The exact steps required to fix this problem vary widely depending on the version of Windows that the target system is running.

The following steps assume that your system is running Windows 10, but they will vary slightly for other Windows versions.

  1. Log on to the remote system. You may have to log on locally or reboot the host to be able to log in.
  2. Press Ctrl + Alt+ Delete to open the Task Manager
  3. Select the Performance tab
  4. Click on the Memory option
  5. Check to see how much memory is available. Ideally, at least 20% of the machine's memory should be available for use (Figure 1)
Windows memory status
A Windows system that has plenty of memory available

If you find that the remote system has insufficient memory, you will need to allocate additional memory to it. Sometimes the best option will be to enable virtual memory. To do so, follow these steps:

  1. Go to Settings
  2. Click on About
  3. Click Advanced System Settings
  4. Click the Settings button found in the Performance section (Figure 2)
System performance settings
The Settings button found in the Performance section
  1. Click on the Advanced tab
  2. Click the Change button
  3. Select the automatically manage paging file size for all drives check box
  4. Click OK (Figure 3)
Automatic virtual memory management
The automatically manage paging file size for all drives section with the box checked

2. Check the self-assigned remote desktop certificate

Some remote desktop connection problems stem from an invalid or corrupt certificate. This certificate is a local resource, and it resides on the PC that you use to establish the remote desktop connection to the remote machine. To correct this problem, you should follow these steps:

  1. Open File Explorer and navigate to C:\ProgramData\Microsoft\Crypto\RSA
  2. Rename the MachineKeys folder to MachineKeys-Backup. Renaming the folder rather than deleting it gives you a way to retrieve your keys later on if it becomes necessary to do so (Figure 4)
MachineKeys folder
The MachineKeys folder that you should rename to MachineKeys-Backup
  1. Launch the Service Control Manager by entering the Services.msc command at the Run prompt
  2. Restart the Remote Desktop Configuration service
Remote Desktop Configuration service restart
The Microsoft Remote Desktop Configuration service, with the option to stop or restart
  1. Open File Explorer and navigate to C:\ProgramData\Microsoft\Crypto\RSA
  1. Verify that a new certificate was created
  2. Verify that the TSUserEnabled Registry Key is set

If you are working in a Terminal Server environment, then the RDP connectivity problems can also occur if the TSUserEnabled Registry Key is set to 0 instead of 1 on the client. Keep in mind that editing the Windows Registry is dangerous, so it's important to take the appropriate precautions in case anything goes wrong. You can check this Registry key by following these steps:

  1. Open the Registry Editor
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\
  3. Make sure that the value of TSUserEnabled is set to 1 (Figure 6)
Windows Registry value
The Windows Registry Editor's Terminal Server values with the TSUserEnabled value set to 0 -- it should be 1

3. Recreate the user profile

As a last resort, you can try recreating the user profile on the machine that is unable to establish a Microsoft RDP connection. This technique can cause data loss, so it is extremely important to create a backup before attempting this technique.

To recreate the user profile, complete the following steps:

  1. Open the Registry Editor
  2. Navigate to the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList (Figure 7)
Windows Registry Editor user entries
This Registry Editor's entries correspond to user profiles
  1. Right-click on the user profile that you want to recreate -- the ProfileImagePath key will tell you who the profile belongs to
  2. Select the Delete command from the shortcut menu to delete the profile
  3. Reboot the machine and log in as the user whose profile was deleted

Dig Deeper on Terminal Services and Remote Desktop Services

SearchEnterpriseDesktop
SearchServerVirtualization
SearchCloudComputing
SearchVMware
Close