When our IT staff freshly image a PC, we're seeing cases where the time is hours or days off, depending on the hardware. This is causing problems with updates and/or joining the domain.
Once the PC's are added to AD, we're good...as they get time from the DC's. But I'm concerned with getting the time correct prior to that. PC's immediately start pulling updates from our WSUS servers the second they come on the network and as a matter of procedure we like them to be fully updated prior to joining AD. When the time is off by hours, it causes problems with updates. And like I said, large time differences can prevent you from adding the computer to AD.
Anyway, I was thinking of adding a small batch file to the RunOnce of our system image, just so on the first bootup, they perform a time sync to our NTP server. But I don't want these PC's "remembering" this information so that once they get added to AD, they are starting with a default time configuration and behave correctly as domain members and get time from the DC's.
Cool, thanks for that. Since this is a fresh image, I'll need to make sure I deal with the Powershell execution policy since we set that through a GPO in AD. Maybe just specify it on the command line I suppose. I'll try that..thanks again!