Target Devices may display the incorrect time.  The Device time differs from that of the domain controllers.  The symptoms can vary but include:

1. The inability to login to the Target Device
2. The Device domain Trust Relationship breaks. 
3. VDA registration continues to fail.

 

Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.

 

In vDisk Maintenance mode resync the default configuration to get time from the Domain Controllers.

1.  Be sure the W32Time service is running and set to automatic start.
2.  From an elevated command prompt run> w32tm /config /syncfromflags:domhier /update.
3.  Check the time status > w32tm /query /status
4.   Running w32tm /resync will force and automatic update with the configured time source.

---

Problem Cause

By default a machine who has joined a domain will automatically be configured to sync its time from the domain controller(s) it communicates with.   You can check 'Type' equals Nt5DS in the following registry location to verify that the machine is configured to sync with the domain

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

If the Windows Time Service isn't running the machine will sync its time with CMOS, you can check this by running the following,

>w32tm /query /source.     

This problem is caused by w32tm not running.  It is disabled or failed to start resulting in the Target Device syncing its time with the hypervisor CMOS.  In some cases this is only uncovered after a daylight time change event because the Target Device(s) have been syncing with CMOS the entire time.  CMOS time isn't using DST and skew occurs directly after the time change event.