If you wish to use NTP you should really use it properly and install an NTP daemon. It will try keep your clock in sync using regular clock skew rather than jumping it at arbitrary times.
You can get a good Windows port of the standard NTPD from here.
If you have AD you don't need to do this, so long as the client is properly set up (i.e. no time server is set) it will automatically sync with the doamin hierarchy.
If you don't have AD you need to look at the NET TIME or W32TM commands.
You can use the Net Time command to do this:
This will set your machine to use the external server specified for its time server.
If you wish to set the machine to use an internal time server, you can use this command:
If you wish to use NTP you should really use it properly and install an NTP daemon. It will try keep your clock in sync using regular clock skew rather than jumping it at arbitrary times.
You can get a good Windows port of the standard NTPD from here.
You don't need to use a batch script.
See my answer here for some info on NTP in Windows.
If you have AD you don't need to do this, so long as the client is properly set up (i.e. no time server is set) it will automatically sync with the doamin hierarchy.
If you don't have AD you need to look at the NET TIME or W32TM commands.