Online Help > Support/Resources > Troubleshooting > Microsoft RDP

Automatic Logon Troubleshooting



Sometimes the automatic logon does not function and your credentials are requested by the remote system. Here are some steps to help identify the issue. Support for automatic logon was introduced on Windows 2003/XP, so ensure you are trying to connect to these or later versions. Windows 2000 does not support the automatic login.


RDP Sessions connect successfully when in external mode, but not in embedded mode.


This issue may be caused by a bad authentication negotiation because in some cases Single Sign On (SSO) requires Network Level Authentication (NLA). It can happen when prompting for credentials and when using automatic logon. Please activate Network Level Authentication in the Connection tab of your session. You might also have to check the Public Mode option in the Advanced tab to make it work.


Network Level Authentication

Network Level Authentication


See also : Network Level Authentication, Configure NLA for Remote Desktop Services Connections


The connection was denied because the user account is not authorized for remote login.

We have discovered that enabling the Public Mode option in the Advanced tab resolves the issue.


Public Mode

Public Mode


Ensure credentials are entered properly.


RDM allows for advanced credential management. Depending on your choice of: Default, Credential Repository, Embedded or Inherited ensure the credentials are properly entered. Please see Credentials


Credential entry

Credential entry


Ensure that "Always ask for credentials" is not checked.


Microsoft Remote Desktop - General tab

Microsoft Remote Desktop - General tab


Ensure a system policy defined on the host is not requiring explicit credential entry


The host server can be configured to always require the credentials to be entered in an interactive manner by the user. Ask your system administrator to confirm this is the case.


Choose the instructions depending on the server operating system. Note that there are often multiple ways to configure the host (WMI, Scripting, etc), but the group policies are the preferred method. Therefore the links are for the articles describing group policy solutions when they are available.




Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options.

Windows Server 2008

Group Policy Settings for Terminal Services in Windows Server 2008

Windows Server 2008 R2

Group Policy Settings for Remote Desktop Services in Windows Server 2008 R2

Windows 2012

The settings are on the Session Collection Properties.


More info on the new Remote Desktop Services:

Guide to configure the Quick Deployment:

Test Lab Guide: Remote Desktop Services Session Virtualization Quick Start


Single Sign On works for TS Web Access, however, they cannot be shared across TS Web Access and TS or TS Gateway.


You must adjust a group policy to allow that. Please follow the directions in


Remote Desktop Manager hangs when prompted to enter credentials.


When you are prompted with this credential box, Remote Desktop Manager hangs.


Windows Security

Windows Security


Probable cause

The issue seems to occur with users using a Wacom Bamboo Fun Pen & Touch tablet. Latest drivers are installed.

When users with a Wacom tablet click on a session with an expired password in the private vault, or a non domain joint server, forcing Remote Desktop Manager (or in fact RDP) displaying a credential popup, Remote Desktop Manager freezes.

When the user does the very same action with a regular mouse, everything goes fine.


The problem appears to be in the Wacom settings along with some windows settings to use Windows Ink as handwriting.

When Use Windows Ink was disabled, Remote Desktop Manager didn’t freeze anymore when displaying a credential box.

It did also solve problems with the focus of other applications.