New
#31
Hi,
Thanks to everyone who helped me think this through.
The solution uses a combination of changing local security policy suggested here (Date and Time - Allow or Prevent Users and Groups from Changing) and the very full-featured and free-for-home-use time-sync program Dimension 4 (Thinking Man Software - Dimension 4 v5.3). Changing local security policy does prevent the user from changing the time, but it also prevents WIndows Time service from running, so over time the system clock can drift too far off course. Dimension4 runs as a service, runs hidden, and has profuse configuration options and keeps the time synced despite the user's not having time-change permission. As a final option I set the Windows Time service to manual.