I have the same issues as well, twice a year. Computer GPOs not applying when the user logs on.
It started in 2012 with Windows XP on a older version of View.
We then moved on to Windows 7 on View 6.2.0 (still up and running to this day) and we are still experiencing issues. We managed to find a way to bypass this issue by installing the latest Windows updates and recomposing the pools a couple days before the time change.
We also have another environment on View 7.3.2 with Windows 7 and Windows 10 linked-clones pools.
We never had an issue with Windows 7 machines running on 7.3.2 for some reason, never had to recompose after DST.
But we seem to have this issue running Windows 10 (1607) on this same Horizon View environment 7.3.2. We have these pools up and running for the last 4 months.
I noticed this error in the event logs of these machines, Security-Kerberos Event id 5:
KERBEVT_KRB_AP_ERR_TKT_NYV
The Kerberos client received a KRB_AP_ERR_TKT_NYV error from the server %1. This indicates that the ticket used against that server is not yet valid (in relation to that server time). Contact your system administrator to make sure the client and server times are in sync, and that the KDC in realm %2 is in sync with the KDC in the client realm.
By the time the user logs in to the machine, the time has already been updated. But from what I can see, the Computer GPOs are trying to apply before the service has time to synchronize with the DC in the domain.
I wish I knew what made our Windows 7 running on Horizon 7.3.2, not have this issue at all, whether we update it or not after DST. All our templates are configured in a workgroup. These VMs are then joined to the domain with Quickprep (linked-clones). We used Fling to optimize our templates.
For Instant clones, we had too many issues at the time with AppVolumes and our antivirus solution, that we reverted back to Linked-Clones. We never had the chance to test it out after DST.
