You may have to log on locally or reboot the host to be able to log in. The following steps assume that your system is running Windows 10, but they will vary slightly for other Windows versions. The exact steps required to fix this problem vary widely depending on the version of Windows that the target system is running. 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. 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. As such, there is no universal quick fix for the problem. Unfortunately, there are a variety of problems that can cause errors which will result in Microsoft remote desktops' connection being stuck configuring remote sessions. 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. The problem can occur regardless of whether Microsoft Terminal Server is in use.
Finally, close the Local Group Policy Editor and restart your system.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.Do the same for the following policies as well: Allow delegating default credentialsĪllow delegating saved credentials with NTLM-only server authentication.Double-click under Value, type in TERMSRV/* and then click OK.
Type in ‘ gpedit.msc’ to open the Local Group Policy Editor.Basically what you will have to do is give a set of Credential Delegation policies a specific value which will most likely fix your issue. If the above-mentioned solutions do not work out for you, you can try to isolate the issue by modifying a few Local Group Policies.
0 kommentar(er)
