# Merging of "win\_\*" with their non-OS specific siblings?

**URL:** <https://forum.ansible.com/t/merging-of-win-with-their-non-os-specific-siblings/30438>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [May 28, 2019, 2:35pm UTC](https://forum.ansible.com/t/merging-of-win-with-their-non-os-specific-siblings/30438 "2019-05-28T14:35:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dan\_linder](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dan_linder/32/3833_2.png) [@dan\_linder](https://forum.ansible.com/u/dan_linder)\
**Post date:** [May 28, 2019, 2:35pm UTC](https://forum.ansible.com/t/merging-of-win-with-their-non-os-specific-siblings/30438/1 "2019-05-28T14:35:25Z")

</div>

Are there plans to merge the various Windows specific modules into their non-OS specific module twins? I’m thinking more of things like “win\_ping”, “win\_copy”, “win\_command”, “win\_file”, “win\_shell”, “win\_tempfile”, “win\_template”, “win\_uri”, “win\_user”, etc.

There are plenty of Windows specific calls that don’t make sense to merge (e.g. “win\_domain\_controller”, “win\_domain\_computer”, etc) so I get those should stay separate.

---

<div class="post-metadata">

**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:** [May 28, 2019, 7:07pm UTC](https://forum.ansible.com/t/merging-of-win-with-their-non-os-specific-siblings/30438/2 "2019-05-28T19:07:13Z")

</div>

No, doing so would be a documentation nightmare as they are completely separate modules with some options not implemented or applicable on Windows and vice versa.

Thanks

Jordan