Date time not updating computer
Cleanest way would probably be to have the user test from a workstation that is not on the domain.The protocols used to contact domain controllers (specifically Kerberos) are based on the computer's time.However, sometimes, the clock doesn’t show the accurate time and that could cause some issues. In your computer current server should be ‘time.windows.com’). Click on drop down and the list of servers will appear. It still performs synchronization once in a week as done previously by Windows default server.
The user may have problems getting group policy updates and may have issues authenticating (but that can be fixed with a time reset and reboot) You will have to: If the time is off authentication to Network Resources will fail.This has caught me off-guard on several occasions now, as I would work with an incorrect assumption concerning the time, only to find myself running an hour late to an appointment. The first thing that comes to mind is to switch operating systems.For reasons that extend far beyond wonky time-keeping, I have been wanting to switch to open-source for years.Sure enough, Microsoft has issued an update for Windows XP (Service Pack 2) that “[…] enables your computer to automatically adjust the computer clock on the correct date in 2007 due to revised Daylight Saving Time laws in many countries.Hopefully, this will work, however, if it doesn’t, there are several other ways to “beat the clock,” as it were.