This message was deleted.

I've seen that. I typically use the ControlUp logon duration analyzer script to cross reference logon times from Director

Yeah I do the same, was just wondering if there was a config I was missing in our environment that was making director not report correctly.

Could this be an ICA file download and user waited? I just did a test and waited one minute to launch the downloaded ICA file and Director captures the delay at a high level, but I can't find any further details when I drill down.

This used to fix it when adding to VDA. [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize] "StartupDelayInMSec"=dword:00000000

Could be like an environment I'm investigating currently where for some reason there is a 30s gap between the HDX Connection and the Profile load start every logon which shows up in the charts in DaaS monitor now.

@Geert Just double checked and we already have that key being applied to users logging. @Corey Tracey oooo thats interesting, will do some testing to see if I can produce the same but what is odd is 90% of our users will be launching from CWA so wouldnt expect the delay on the ICA file launch.

That one was DaaS but the same view is in 2311 Director as well.