10 Replies Latest reply on Jan 12, 2019 10:38 AM by nettech1

    Troubleshooting slow logins.

    lansti Enthusiast

      I'm looking into our logons, where users experience logon time beween 60 to 90 seconds, which i meen is too slow logon.

       

      When i have a look at the vmware logon monitor i see that my user often end up with a logon  around 60 seconds:

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] ****************** Session Summary (User: DOAMIN\user, Session: 1) *****************

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Logon Time: 61.32 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Logon Start To Hive Loaded Time: 0.00 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Logon Start To Classes Hive Loaded Time: 3.73 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Profile Sync Time: 3.19 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Windows Folder Redirection Apply Time: 0.00 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Shell Load Time: 6.60 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Total Logon Script Time: 0.00 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] User Policy Apply Time: 49 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Machine Policy Apply Time: 0 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Group Policy Software Install Time: 0.23 seconds

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] Free Disk Space Available To User: 56 GB

      2019-01-04T09:27:38.242 INFO (09f0-1220) [LogonMonitor::LogSummary] ***********************************************************************************

       

      is it possible to point out where the seconds are running from vmlm.txt log or vmlm__CLIENTNAME_USERNAME_date.txt log?

       

      I see this is my vmlm__CLIENTNAME_USERNAME_date.txt log, 15 seconds running away..:

      2019-01-04T10:11:16.995 TRACE (0b3c-130c) [LogonMonitor::ProcessGroupPolicyEvent] Event Id: 4016, ActivityID: {D589478B-B6C6-49AF-887C-DECCFB5C0398}, Account: , Session: 1

      2019-01-04T10:11:31.995 TRACE (0b3c-082c) [LogonMonitor::ProcessGroupPolicyEvent] Event Id: 4016, ActivityID: {D589478B-B6C6-49AF-887C-DECCFB5C0398}, Account: , Session: 1

       

      And from the vmlm.txt log:

      about 6 seconds here:

      2019-01-04T09:26:36.978 DEBUG (09f0-044c) [WinlogonNotifyLogEnd] WinlogonNotify completed OnLogon, pLogonData: 0000000001DEE9A0, Duration (ms): 113

      2019-01-04T09:26:42.341 TRACE (09f0-0b14) [LogonMonitor::ProcessGroupPolicyEvent] Failed to find Session for User PolicyEvent Id: 5326, ActivityID: {2AEE89DF-BACA-42DE-895F-6C618CE405AF}, Account:

       

      10 seconds here:

      2019-01-04T09:26:47.349 TRACE (09f0-0a0c) [MailslotServer::ProcessMessage] Begin event: Product: UEM Agent, Component: FlexEngine, Event: Import, Event Type: EVENT_BEGIN, Process Id: 288, Timestamp: 2019-01-04T09:26:47.349, Session: 1

      2019-01-04T09:26:57.095 TRACE (09f0-0a0c) [MailslotServer::ProcessMessage] End event: Product: UEM Agent, Component: FlexEngine, Event: Import, Event Type: EVENT_END, Process Id: 288, Timestamp: 2019-01-04T09:26:57.095, Session: 1

       

      12 seconds here:

      2019-01-04T09:26:57.095 TRACE (09f0-0a0c) [MailslotServer::ProcessMessage] Begin event: Product: UEM Agent, Component: FlexEngine, Event: Post-import, Event Type: EVENT_BEGIN, Process Id: 288, Timestamp: 2019-01-04T09:26:57.095, Session: 1

      2019-01-04T09:27:09.963 TRACE (09f0-0a0c) [MailslotServer::ProcessMessage] End event: Product: UEM Agent, Component: FlexEngine, Event: Post-import, Event Type: EVENT_END, Process Id: 288, Timestamp: 2019-01-04T09:27:09.963, Session: 1

       

      15 seconds:

      2019-01-04T09:27:15.771 TRACE (09f0-0a0c) [MailslotServer::ProcessMessage] End event: Product: UEM Agent, Component: FlexEngine, Event: Async, Event Type: EVENT_END, Process Id: 4792, Timestamp: 2019-01-04T09:27:15.771, Session: 1

      2019-01-04T09:27:30.529 TRACE (09f0-0a0c) [MailslotServer::ProcessMessage] End event: Product: AppVolumes, Component: svservice, Event: Login, Event Type: EVENT_END, Process Id: 932, Timestamp: 2019-01-04T09:27:30.529, Session: 0