# Ansible win\_ntp Module in community.windows **URL:** \ **Category:** Collection Development\ **Tags:** windows\ **Created:** [August 25, 2025, 4:25pm UTC](https://forum.ansible.com/t/ansible-win-ntp-module-in-community-windows/44368 "2025-08-25T16:25:00Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![GHDEV00](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/ghdev00/32/9321_2.png) [@GHDEV00](https://forum.ansible.com/u/GHDEV00)\ **Post date:** [August 25, 2025, 4:25pm UTC](https://forum.ansible.com/t/ansible-win-ntp-module-in-community-windows/44368/1 "2025-08-25T16:25:00Z")
One common tasks when provisioning Windows servers is configuring time synchronization. Accurate timekeeping is critical for logs, authentication, and distributed systems — yet, surprisingly, there’s currently no dedicated NTP module available for Windows in Ansible. When reviewing the Ansible community.windows collection, I came across an existing pull request that would introduce exactly this functionality (see PR #150). Unfortunately, it was never merged. Our team has tried to help move this forward: - We reached out in the original PR discussion to ask if it could be reconsidered. - We contacted the maintainer directly via email. - We even offered to take on maintenance of the module ourselves, since this is a feature our company — and likely many others — relies on. So far, we haven’t been able to get a response. That brings me to this post: We’d like to ask again — would it be possible to add this module to the community.windows collection? Configuring NTP is a standard provisioning step for Windows servers, and having an official Ansible way to handle it would be extremely valuable for the wider community. If others are also interested in this, please let us know. Thanks in advance Please see PR #150: > > > \##### SUMMARY > > Manage Windows NTP Server. > Users can perform the following tas…ks: > \- can change the time zone > \- pass the multiple peers to the NTP server. > \- for NT5DS, can set cross\_site\_sync\_flag > \- enable/disable the NTP client in time service > \- can select which peers to accept synchronization from > \- can synchronize the clock > \- can change the settings to default > > > Fix #114 > \##### ISSUE TYPE > > \- New Module Pull Request > \##### COMPONENT NAME > > ansible.windows.win\_ntp > \##### ADDITIONAL INFORMATION > > > > \- name: Enable npt service with multiple peers to get sync from > community.windows.win\_ntp: > enabled: true > peerlist: > - time.google.com > - time.yahoo.com > - time.apple.com > type: NTP > sync\_clock: true > > \`\`\`paste below > > \`\`\` ---
**Author:** ![mikemorency](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mikemorency/32/2672_2.png) [@mikemorency](https://forum.ansible.com/u/mikemorency)\ **Post date:** [November 25, 2025, 8:53pm UTC](https://forum.ansible.com/t/ansible-win-ntp-module-in-community-windows/44368/2 "2025-11-25T20:53:20Z")
In the PR, the maintainer says > Closing due to the age of the PR. If someone wishes to continue with the work they can submit a new PR with the changes requested added in. Have you tried opening a new PR? @jborean is on the forum and seems active in the collection. I’m sure if you opened a PR you would get some feedback. ---
**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\ **Post date:** [November 28, 2025, 12:31am UTC](https://forum.ansible.com/t/ansible-win-ntp-module-in-community-windows/44368/3 "2025-11-28T00:31:04Z")
Right now I would love to accept new PRs but nothing has really changed from a maintenance perspective. The `community.windows` collection mostly just sits there and while I do go through PRs that are submitted for bugfixes or features for existing modules I do not have the capacity to work on any reported issues. Any new module there just adds even more burdens on maintaining it as it expands the scope, potentially more people raise issues that don’t get anywhere leading to more frustration. It also expands the test suite leading to more resources having to be spent to run CI and spin up Windows hosts. Another problem with testing is when we add new features like PowerShell 7, it takes a long time to validate each module and fix up the various tests for changes in between the versions. I really do sympathise and maybe sometime in the future we can revisit this once things are stabilised or there’s a push for more community involvement but if we were to accept new features the collection just continues to grow and grow and become even more unmanageable for myself.