DST Changes Not Reflecting in MCS Created Machines
book
Article ID: CTX218718
calendar_today
Updated On:
Description
After DST changes are implemented, the MCS machines do not register and policies do not apply to these machines.
Environment
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.
Resolution
Follow the following steps to get the correct time on the MCS Desktops:
- Login to the master Image.
- Run the command "w32tm /resync /nowait" in the command prompt or update the time manually in the master image.
- Update the catalog.
Problem Cause
If the Windows time service kicks in before the group policy Client, everything works fine as the time is updated before any communication with Active Directory happens but when the group policy client loads first, the authentication fails because of the incorrect time which corrupts the Kerberos handshake, and leaves the machine in an unregistered state.
Issue/Introduction
After DST changes are implemented the MCS machines do not register and policies do not apply to these machines
Was this article helpful?
thumb_up
Yes
thumb_down
No