We are experiencing issues with GPO-triggered logo...
# _generald
Dennis Hirsch
07/02/2026, 12:50 PMWe are experiencing issues with GPO-triggered logon scripts in a customer's Citrix CVAD environment. The affected GPOs are applied correctly. We can see them in both gpresult and the Event Viewer, but the configured logon scripts are not executed. We have not been able to narrow the issue down to a specific GPO, as it appears to occur randomly within the GPOs containing scripts.
The GPOs with the logon scripts are linked at different OUs levels, including one at the domain root level with "enforced" enabled. (this is the most important one and seems to never work)
It seems that the issue only occurs on Windows Server 2022 VDAs (2507 CU1) that publish a full desktop. Published application silos are not affected.
The same scripts work without issue when deployed through Citrix WEM.
We are currently investigating ways to gather more information, including adding logging to the scripts and creating dummy files in %TEMP% using Group Policy Preferences within the same GPO. So far, however, we have not identified any clear pattern.
We have also tested different processing modes, including disabling "Run logon scripts synchronously" and disabling asynchronous Group Policy processing, but neither made a difference.
What's particularly strange is that the previous VDAs running Windows Server 2016 behave as expected and do not show this behaviour.
Has anyone encountered similar behavior on Windows Server 2022 VDAs specifically, or has any suggestions on where to continue troubleshooting?
j
James Rankin
07/02/2026, 12:52 PMHave you got Logon Script Delay set to 0? Otherwise they go five minutes after logon
James Rankin
07/02/2026, 12:53 PMPolicy
Configure Logon Script Delay
Category Path
Computer Configuration\Administrative Templates\System\Group Policy\
Supported On
At least Windows Server 2012 R2, Windows 8.1 Preview or Windows RT 8.1 Preview
Registry Key
HKLM\Software\Policies\Microsoft\Windows\System
Value
AsyncScriptDelay
Admx
GroupPolicy.admx
Explanation
Enter “0” to disable Logon Script Delay.
This policy setting allows you to configure how long the Group Policy client waits after logon before running scripts.
By default, the Group Policy client waits five minutes before running logon scripts. This helps create a responsive desktop environment by preventing disk contention.
If you enable this policy setting, Group Policy will wait for the specified amount of time before running logon scripts.
If you disable this policy setting, Group Policy will run scripts immediately after logon.
If you do not configure this policy setting, Group Policy will wait five minutes before running logon scripts.
d
Dennis Hirsch
07/02/2026, 3:33 PMWill try that. Thank you.
c
c4rm0
07/02/2026, 4:24 PMany wmi or security filtering on the GPO ?
d
Dennis Hirsch
07/03/2026, 12:44 PMNo filtering @c4rm0
Dennis Hirsch
07/07/2026, 11:35 AM@James Rankin Logon Script Delay set to 0 does not make any difference
j
James Rankin
07/07/2026, 12:51 PMVery odd. You got any loopback funkiness going on?
d
Dennis Hirsch
07/07/2026, 1:03 PMAccording to my customer, Logon Script Delay set to 1 seems to be the sweet spot with good results. I have no idea why
j
James Rankin
07/07/2026, 1:19 PMBizarre. Meaning they are set to run one minute after logon. Maybe something else running is interfering with the scripts if they try to start straight away?
j
Jeremy Saunders
07/10/2026, 1:14 PMDo the scripts actually exist in the Group Policy containers in the SYSVOL of all Domain Controllers? There could be that one DC is missing the actual files. Assuming that they are embedded in the actual GPO.
11 Views