This message was deleted.
# citrix-vads
Slackbot
03/03/2023, 10:05 AMThis message was deleted.
n
Nick Panaccio
03/03/2023, 11:32 AMHave you tried running AnalyzeLogonDuration (https://www.controlup.com/script-library-posts/Analyze-Logon-Duration/) yet? That would be my first stop. If you're on FSLogix, I'd also check the container log. At my last place, we ended up having a storage issue that caused similar results to what you're seeing, and it was reflected in that FSL log.
j
James Rankin
03/03/2023, 11:42 AMNot sure I can get a script into this environment, but will have a try
n
Nick Panaccio
03/03/2023, 11:42 AMYou can do it manually... I never use ControlUp for this
Nick Panaccio
03/03/2023, 11:42 AMUnless you mean you can't run a script (needs to be run as an admin)
j
James Rankin
03/03/2023, 11:43 AMIt's a locked-down environment, so probably blocked for admins - will see what I can do with my pentesting knowhow though
n
Nick Panaccio
03/03/2023, 11:44 AMAh, gotcha.
Nick Panaccio
03/03/2023, 11:45 AMFWIW, this is what I do:
1. Copy the script locally to the VDA you want to test on
2. Run the following against that VDA:
Copy code
Invoke-Command -cn Hostname -scriptblock {auditpol /set /subcategory:"Logon" /success:enable}
Invoke-Command -cn Hostname -scriptblock {auditpol /set /subcategory:"Process Creation" /success:enable /failure:enable}
Invoke-Command -cn Hostname -scriptblock {auditpol /set /subcategory:"Process Termination" /success:enable /failure:enable} Copy code
powershell -executionpolicy bypass -file ".\AnalyzeLogonDuration.ps1" domain\username👍 1
Nick Panaccio
03/03/2023, 11:45 AMBam, Bob's your uncle
Nick Panaccio
03/03/2023, 11:45 AMor whatever you guys say now
❤️ 1
😂 1
j
James Rankin
03/03/2023, 12:00 PMDoes that analyze all logons? This is RDSH and I'm interested in a specific user
n
Nick Panaccio
03/03/2023, 12:01 PMI've never run it on XA, but I imagine it would since you need to specify the user to query. It's using that user when querying the events to build the logon times.
j
James Rankin
03/03/2023, 12:09 PMSorry, I didn't see the username bit in the command line, cool
James Rankin
03/03/2023, 12:21 PMWell dammit - the script reports the logon as 38 seconds whereas Director (and the user's own experience) report it as 126 seconds. I'm still 88 seconds missing 😞
n
Nick Panaccio
03/03/2023, 12:35 PMAre you actually seeing the logon take that long? Director being right isn't always an easy pill to swallow...
j
James Rankin
03/03/2023, 12:46 PMAs is usual, the user account I have has no such issues. But when i first came in they were complaining of long logon times (some outliers are 10mins+) and the Director data seems to reflect what they told me
s
Spencer Sun
03/03/2023, 1:54 PMThat makes me ask, are the long logon times all happening in a certain window of time? Could be something environmental that happens at specific time periods,
Spencer Sun
03/03/2023, 1:55 PMIf it is time related, are others outside of the RDSH farm seeing similar delats?
j
James Rankin
03/03/2023, 1:55 PMOnly got a week's worth of data so difficult to say. Also session hosts are experiencing quite a lot of hangs which I am trying to fix. It may be that fixing one issue depends on (or precludes) the other
s
Spencer Sun
03/03/2023, 1:56 PMunderstood
Spencer Sun
03/03/2023, 2:09 PMthe other things I was thinking is, how many users are reporting this? Since the account you ran the script with isn't seeing this issue, maybe it has to do with user config(s). same RDSH hosts? The more data the better to try and find patterns It's never help to just get the anecdotal, "Everyone" says it's "Really" slow....