XenDesktop Logon Failure: Desktop Viewer Pops up and Closes

Know this problem? You try to start a XenDesktop session, Desktop Viewer opens … and closes. Then nothing.

When you look at the machine in Desktop Studio you find that everything looks good: it is registered with the DDC and it is not in maintenance mode. However, you find an event with the following properties in the application event log:

Source:        Citrix ICA Service
Event ID:      1260
Type:          Warning
Description:   ICA connection is cancelled because auto-logon is enforced and auto-logon failed.
               For more information, see 


Clicking the URL given in the event does not help much:

Citrix eDocs 404


As always, the solution is simple – once you know what it is: the user right allow log on locally was missing. This can be configured through Group Policy here: Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment.

By default the following users & groups are granted the right to log on locally on Windows 7 and 8:

  • Guest
  • Administrators
  • Users
  • Backup Operators

, ,

5 Responses to XenDesktop Logon Failure: Desktop Viewer Pops up and Closes

  1. Amar Honnungar July 5, 2013 at 06:58 #

    I am still not able to get the desktop after adding the reqd group policy. Would you be able to share the ICA launch file that you used?

  2. Vasilev September 19, 2013 at 13:28 #

    Hello Amar,
    Check the authentication settings in your web interface. Look for the domain if it’s netbios added. If so, change it to the FQDN of the domain. Or try to disjoin/join the machine. Hope it helps.

  3. rz April 30, 2014 at 14:46 #

    was with a citrix support engineer on the line, and Helge Klein on the other room, first response in google was this page. serendipity…
    in our case the solution was to add a regentry
    create a new DWORD value called ‘EnforceAutoLogon’ in HKLM\Software\Policies\Citrix, and set it to 0.

    • Sathananthan January 8, 2015 at 15:58 #

      Hi RZ,

      Thanks a lot. Adding the registry key and a restart worked perfectly.

Leave a Reply