Provisioning Services and Daylight Saving Time

book

Article ID: CTX200058

calendar_today

Updated On:

Description

With the release of Citrix Provisioning 2503.1, PVS improves the DST handling by:

  • Capturing the UTC offset from the registry when promoting a vDisk to production or standard mode.
  • Sending the correct local time (that matches the timezone information in the vDisk) to the target at boot.
  • Setting the RTC’s local time to match the vDisk registry during UEFI time, ensuring accurate local time from Windows startup.



Earlier product versions than PVS 2503, may still encounter issues after DST changes and require manual intervention:

  • During a Target Device (TD) boot or reboot, after Daylight Saving Time (DST) but prior to any vDisk maintenance, you might notice that the TD system time is not consistent with the system time of the PVS Server. A user has reported the inability to log on to the domain.
  • Log on with a local user account and you can notice that the system time on the TD is not equal to that of the PVS Server or the Domain Controllers. Variety of system events might be logged in Eventviewr.exe with reference to GPO processing failures, domain trust relationship and Kerberos errors, and Windows time sync events.

 

Cause

The vDisk from which the TDs are streaming have not yet been updated to reflect the correct time. This is causing any new booting TDs or previously running TDs, which were rebooted, to show a system time that is normally skewed by one hour. The TD operating system is being provisioned by a vDisk that had its system time last updated prior to DST.

Resolution

To resolve the issue:

  • Upgrade all PVS components are upgraded to PVS 2503.1 or later
  • Ensure all target devices are UEFI based
    • Support for all BIOS based target device booting has been deprecated since 2025.





On releases older than PVS 2503 or systems running legacy BIOS configuration:
Resolve the issue by updating the vDisk to reflect the correct system time. This can be done either manually in private image mode, or by using vDisk updates. For more information refer to Citrix Documentation - Manually Updating a vDisk Image. 

  • With the vDisk in read/write mode, from a TD command prompt run the following:
    w32tm /resync /nowait

  • If the user cannot log on to the TD because of trust relationship breakage, reset the Machine Account in AD from the PVS console before powering that TD. If the TD is powered off, you can power on by clicking PVS console > right-click Active Directory > Reset Machine Account Password > Power machine on. 

Additional items for consideration:

  • Prevent Targets from rebooting after DST but prior to a system time update for that vDisk; an administrator should find that time should remain consistent so long as a TD never reboots prior to maintenance. If the TD remains running without a reboot, the user experience should not be affected. Booting for the first time or rebooting running targets after DST but prior to the vDisk system time update is where this conflict occurs. 
  • Time skew in general, not just pertaining to DST, will cause the same type of TD failures, GPO processing errors, domain trust relationship and general log on issues. It is up to the systems administrator to maintain consistent time across all hosts in both provisioned and non-provisioned environments.
  • In Windows Domain, there is a critical requirement to keep all hosts system time consistent. This is also a requirement of PVS best practices. In many cases, you can notice Target streaming performance and high availability failures when the system time is skewed.

 

 

 

 

 

Issue/Introduction

Provisioning Services and Daylight Saving Time

Additional Information

PVS 2503 release notes: https://docs.citrix.com/en-us/provisioning/2503-1/whats-new.html#improved-dst-management