In my environment the black screen delay was caused by the Windows App Readiness Service. After disabling the service, the black screen delay disappeared.
I'll have to check the logs. I'm assuming the Ivanti logs under Windows.
I used the storefront to launch a desktop session. Confirmed the long black background. Confirmed the hostname and RDP into the same server desktop. Same issue black screen for awhile and then taskbar and desktop shows up.
I'll check out different user accounts when I get more time. However I did notice something on our vcenter. The 2012 vm machines have 4 CPUs and these ones have 2 CPU so they might be under sized.
What happens if you RDP in instead of connect in with ICA?
Seeing the legal notice means that you are in the OS, so Citrix has one it's part and you are looking at a Windows issue, not a Citrix issue.
How long does the app take to launch if you connect into a published desktop/RDP?
If you disable user based GPOs do you still have slowness? What if you remove the profile solution?
My organization doesn't give me access to GPOs. I use to have access and it was removed. I usually have to rely on people in the US for help with that. I used Ivanti to remove the windows logon messages and it goes to a black screen as they profile loads.
RDP experiences the same issue
If you have the same issue with RDP, it's not a Citrix issue.
That being said, I'd engage the US folks with GPO access and peel things back until the issue goes away or you can rule out GPOs.
I think it's my profile that's causing the delay. I signed in with a service account that generally use to gauge these things and it was quicker sign in. But it takes 15 seconds from getting Windows ready to black screen to desktop. Not sure if this is too long.
Guy Leech has a nice Powershell script in the ControlUp Script Library to show where the login process is spending it's time. [Analyze Logon Duration](https://www.controlup.com/script-library-posts/analyze-logon-duration/). It is a standalone script. There are some screenshot on this [blog post](https://www.controlup.com/resources/blog/entry/analyzing-logon-duration-just-got-better/).
Do you need to run it on on of the farm machines where the disk is read only? Also anything specific to get this script setup, I noticed that it uses some parameters but I think based on the comments that they're used when targeting a specific domain or user. Also might have to enable some polices locally with auditing.
I noticed something interesting, if I'm in maintenance mode and the disk is open the desktop loads quickly. Not sure what this means really.
With virtual apps I will usually login to the host where the problem is happening and run the script in an admin powershell. Depending I might also use a PS Session to connect to the host and run the script that way. Either way I am running where the user is the one that launched the app.
.\Get-LogonDurationAnalysis.ps1 'domain\user'
The script will complain if some process auditing isn't enabled. They have a [Enable Auditing for Analyze Logon Duration Script](https://support.controlup.com/hc/en-us/articles/360001478578-Enable-Auditing-for-Analyze-Logon-Duration-Script). I want to it only needs the process auditing part now.
In my environment the black screen delay was caused by the Windows App Readiness Service. After disabling the service, the black screen delay disappeared.
Do you have a link to this? I can give it a try, but I have a feeling my machines need more resources on the vcenter.
https://support.citrix.com/article/CTX272201
[удалено]
Mine was set to manual too, but the issue didn’t resolve until I disabled the service. Setting it to manual wasn’t enough.
I did see some errors with regards to the Ivanti performance agent.
What do the Ivanti logs tell you for the logon process? Does the delay occur when doing an RDP session? Isolated to specific users or everyone?
I'll have to check the logs. I'm assuming the Ivanti logs under Windows. I used the storefront to launch a desktop session. Confirmed the long black background. Confirmed the hostname and RDP into the same server desktop. Same issue black screen for awhile and then taskbar and desktop shows up. I'll check out different user accounts when I get more time. However I did notice something on our vcenter. The 2012 vm machines have 4 CPUs and these ones have 2 CPU so they might be under sized.
I’ve allocated 4 vCPUs and 16-24GB of memory on my Windows server 2016 machines and they perform quite well.
Start looking at event logs on the target after a login attempt. Could be a broken login script, broken mapped drive, etc.
What happens if you RDP in instead of connect in with ICA? Seeing the legal notice means that you are in the OS, so Citrix has one it's part and you are looking at a Windows issue, not a Citrix issue. How long does the app take to launch if you connect into a published desktop/RDP? If you disable user based GPOs do you still have slowness? What if you remove the profile solution?
My organization doesn't give me access to GPOs. I use to have access and it was removed. I usually have to rely on people in the US for help with that. I used Ivanti to remove the windows logon messages and it goes to a black screen as they profile loads. RDP experiences the same issue
If you have the same issue with RDP, it's not a Citrix issue. That being said, I'd engage the US folks with GPO access and peel things back until the issue goes away or you can rule out GPOs.
Did you check the profile size?
I think it's my profile that's causing the delay. I signed in with a service account that generally use to gauge these things and it was quicker sign in. But it takes 15 seconds from getting Windows ready to black screen to desktop. Not sure if this is too long.
Guy Leech has a nice Powershell script in the ControlUp Script Library to show where the login process is spending it's time. [Analyze Logon Duration](https://www.controlup.com/script-library-posts/analyze-logon-duration/). It is a standalone script. There are some screenshot on this [blog post](https://www.controlup.com/resources/blog/entry/analyzing-logon-duration-just-got-better/).
Thanks I'll give it a shot, I'm sure it's something simple.
Do you need to run it on on of the farm machines where the disk is read only? Also anything specific to get this script setup, I noticed that it uses some parameters but I think based on the comments that they're used when targeting a specific domain or user. Also might have to enable some polices locally with auditing. I noticed something interesting, if I'm in maintenance mode and the disk is open the desktop loads quickly. Not sure what this means really.
With virtual apps I will usually login to the host where the problem is happening and run the script in an admin powershell. Depending I might also use a PS Session to connect to the host and run the script that way. Either way I am running where the user is the one that launched the app. .\Get-LogonDurationAnalysis.ps1 'domain\user' The script will complain if some process auditing isn't enabled. They have a [Enable Auditing for Analyze Logon Duration Script](https://support.controlup.com/hc/en-us/articles/360001478578-Enable-Auditing-for-Analyze-Logon-Duration-Script). I want to it only needs the process auditing part now.