(also edit the location of the desired logfile, here c:\temp\rdp.log) Function sessionNumberĭim oShell, oExec, sOutput, iUserPos, iUserLen, iStatePos Now create a VBScript-file (for example called c:\temp\log.vbs): Now check the Success box (failed attempts will not be logged this way).now navigate to Local Policy > Audit PolicyĪnd right click the Audit account logon events policy option and choose Properties.The Local Security Policy window will be displayed Click Start and type secpol.msc then hit enter.
I found this is needed because the other events triggered too early to get the hostname. The winlogon notification subscriber took 90 second(s) to handle the notification event (Logon).Well, here it goes. The winlogon notification subscriber is taking long time to handle the notification event (Logon). The application event log captures the following Warnings: This happens over both ICA and RDP and both if you are an Admin or User on the box. Searching online I do not match symptoms with other users the lsm.exe process doesn't hog memory and just hovers around 10-15Mb.Īfter the 40second (approx) wait the server does log you on eventually. This only happens on around half the servers in the farm, but to every user who logs onto these servers.Īll servers have the same patch level, Citrix hotfixes and are up to date on all MS updates. When users connect to an application (we use Seemless Pulished Apps via XenApp 5.0) it goes through the logon process as expected please wait for your user profile, applying users settings, applying policy (registry, file etc.), then is pauses on 'Please wait for the Local Session Manager.' for approx 40 seconds, before then moving on to 'Preparing you desktop briefly'. I've come into a weird problem with our Server 2008 Terminal Services farm which appears to have happened over the weekend.
0 kommentar(er)
