Gavin001
Thanks for that post. Finally figured out what it was. In that HKLMSystemCurrentControlSetW32TimeParameters key, there’s a value called Type and this was set to NoSync. Did a bit of digging round on the web and found an MS article which explained:
Type : REG_SZ
Used to control how a computer synchronizes.
Nt5DS = synchronize to domain hierarchy [default]
NTP = synchronize to manually configured source
NoSync = do not synchronize time
For some reason the default on these terminals is NoSync and not Nt5DS. Once I changed the setting to Nt5DS and rebooted the terminal, it’s now picking up the correct date and time.
Thanks for your help.
CG
Our time servers are our DC’s, so I was under the impression that the terminals would pick up the correct date and time once they’d joined the domain? Would the write filter being enabled cause any problems with this?
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |