After upgrading CVAD to 2507 CU1, MCS provisioned VDAs may incorrectly switch their Windows Time Service configuration from NT5DS to NTP
HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type is overwritten with NTP instead of the expected NT5DS for domain‑joined machines.
As a result the VDA cannot registers successfully
Issue only affects MCS clones
Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
CVAD 2507 CU1 with MCS‑provisioned machines may be configured with the wrong Windows Time Service settings during creation.
A fix is scheduled in future release
Workaround:
Until the permanent fix is applied, enforcing the correct time synchronization mode using one of the following methods:
1.Apply GPO to enforce NT5DS
Configure a Group Policy Object targeting VDA machines: Registry Path: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters Value: Type = NT5DS
2.Scheduled Task on the Master Image
Create a startup scheduled task on the master image to force the correct time configuration after cloning.
Powershell:
$action = New-ScheduledTaskAction -Execute "cmd.exe" -Argument '/c w32tm /config /syncfromflags:DOMHIER /reliable:YES /update && net stop w32time && net start w32time'
$trigger = New-ScheduledTaskTrigger -AtStartup
$principal = New-ScheduledTaskPrincipal -UserId "SYSTEM" -LogonType ServiceAccount -RunLevel Highest
Register-ScheduledTask -TaskName "SyncTimePostBoot" -Action $action -Trigger $trigger -Principal $principal
This forces the VDA to reapply DOMHIER/NT5DS time sync mode immediately after boot.