A slow logon process can come from various causes :

 

  • A slow active directory:

The user may take some time to authenticate on the AD. 


  • Logon script:

When a logon script is executing and mapping network ressource, it can take time to perform the task. 


  • Windows services and processes that are launched at logon:

This can be checked in msconfig. You can also open a task manager to monitor precisely which processes are run by each users. Doing so you should be able to narrow down the ones that are responsible for this. 


  • Device drivers:

At each logon the server may look to make a peripheral available for a user, slowing down the logon process. 

You can choose to un-check drives and peripherals that are not needed in the local ressource tab of the client generator.


If you are still experiencing slowness even though Windows and TSplus products are up to date, then please enable "troubleshooting mode" (license menu), reproduce the issue and provide us with an export of logs within a ticket.


Additionally, the following questions could help identify the main factor that is slowing down logins:

  1. Does it occur right after booting, regardless of how many concurrent sessions are hosted on the server?
  2. Does it occur with a brand-new local user?
  3. Does it occur when using the Windows built-in RDP client (mstsc), with all local resource redirection disabled?
  4. When it occurs, what does the Task Manager display (resource usage)?
  5. Are there any startup applications launched at login?
  6. Does it occur when publishing only the 'Floating Panel' & 'Notepad'?
  7. Is there an antivirus operating on the server ? If yes please apply recommendations from this article 

 

https://support.tsplus.net/a/solutions/articles/44002467672?lang=en


We also recommend trying to increase the server's resources and reviewing the Windows Event Viewer for any potentially related events. Here are the sections that could provide more details about the slowness: 


  • Windows logs > System 
  • Windows logs > Application 
  • Application and services logs > Microsoft > Windows > TerminalServices-LocalSessionManager > Operational
  • Application and services logs > Microsoft > Windows > User Profile Service > Operational