--- title: "Local NTP setup needed for DCM config to work after version 9.0.17 (19162)" slug: "local-ntp-setup-needed-for-dcm-config-to-work-after-version-9017-19162" tags: ["Data Collection Module", "Data collection", "NTP"] updated: 2021-03-29T12:43:54Z published: 2021-03-29T12:43:54Z canonical: "kb.secomea.com/local-ntp-setup-needed-for-dcm-config-to-work-after-version-9017-19162" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.secomea.com/llms.txt > Use this file to discover all available pages before exploring further. # Local NTP setup needed for DCM config to work after version 9.0.17 (19162) Getting "Wait for NTP to synchronize" or "Waiting for NTP to be enabled or configured" error message ? With version 9.0.17 (19162) the timestamp tools has been changed, so in the future you will need to have a NTP pool configured to use the Data Collection module. With version 9.1 (619491006) a new option in DCM config file allows the user to disable the need for a NTP setup. This is done with the config file entry "WaitForNTP": false in the general config file section. See general section example at appendix A below. The below displayed NTP setup is highly recommend when using AWS or Azure as IoT cloud services Example: ![](https://cdn.document360.io/88f49507-a7a0-4636-b297-13c4d0065310/Images/Documentation/image-1617019335574.png) The NTP can be configured in SiteManager GUI > System > Time #### NOTE! Time Zone offset has no effect as all timestamps used are in UTC. Please insert a valid NTP server pool. You can use time.google.com or ntp.secomea.com or you can find links to local NTP pools [here](https://www.pool.ntp.org/zone/@) , However the possibility of being blocked or ignored (NTP KoD) is high when using a public NTP pool without subscription.   ```json { "ConfigName": "Name the entire config", "ConfigDescription": "Describe the entire config", "CheckpointInterval": 600, "AlarmsSaved": 10, "WaitForNTP": false, "Collectors": [ { ```