Sync your GigaStor with NTP

Context

Microsoft Time is pathetic with keeping time between its upstream NTP time source
- Don’t use the Microsoft Time client for keeping time if possible
  - Use a 3^rd party NTP client like Meinberg (more to come)
- Kerberos requires that local time must be within 5 minutes of the Active Directory server time
- This means that unless time is off by less than 5 minutes the NTP client may not adjust local time
GigaStor must be setup to synchronize
- GigaStor will synchronize only to the local OS & not to any NTP
- GigaStor will only synchronize only once every 24 hours
- There is a setting that will force the local OS time to be changed by the GigaStor at synchronization time
  - This option should be disabled if the OS is being synchronized with an NTP time source

Preferred setup for time synchronization on a GigaStor system

Install a 3^rd party NTP client, such as Meinberg (download HERE)
Installing the Meinberg client will disable the Windows Time client
Virtually all the NTP clients out there, including Meinberg are based on open source code from NTP.ORG
While they are all based on this code, different versions offer different options
Enable Time Synchronization on GigaStor
- Disable the option shown above
- Setup to synchronize daily
- Uncheck box for Apply only if time exceeds X
- Set time for when to sync

The fastest way to get everything synced on your GigaStor after setting up everything is to:

Stop the Observer Expert Probe service (if running as a service)
- Close GigaStor if running in console view
Make sure that Windows Time is disabled and stopped
Restart the Network Time Protocol Daemon
- This will force it to sync the OS time
Start the Observer Expert Probe service
- Open GigaStor if running in console view
- This will force GigaStor to synchronize with the local system time

Doing these steps (mind you we are using a different client) resulted in our test GigaStor systems maintaining a max 3ms time difference.