Things described in this chapter apply only to Windows Server 2003. It is strongly recommended that users of all editions of that operating system (both 32 and 64-bit versions) read and take note of the information below before running LogonExpert.
If set to perform automatic logon, LogonExpert logs on to an actual console session – just as one does with a display and keyboard when being next to the server. However, by default, Remote Desktop Connection creates another remote session. Those two sessions can run simultaneously and independently sharing the same user name. The number of active sessions and users running them can be checked on the Users tab in Task Manager.
Task Manager showing two sessions run by one user
In view of the above, if a connection to a Windows Server 2003 machine is made remotely, a new session is initiated and, as a result, a standard logon process including the start of applications that are supposed to run on startup can be seen. This can cause some confusion if the user who is being logged on is expected to have already been logged on by LogonExpert. And while in fact they are, the process of logging on to the parallel session is taking place and being seen.
To avoid that and prevent running the second instances of the startup applications, the remote connection should be made to the console session.