# Proposal for new windows modules **URL:** \ **Category:** Project Discussions\ **Tags:** community, windows, awx\ **Created:** [April 28, 2026, 9:57am UTC](https://forum.ansible.com/t/proposal-for-new-windows-modules/45746 "2026-04-28T09:57:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![lutin-malin](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/lutin-malin/32/4162_2.png) [@lutin-malin](https://forum.ansible.com/u/lutin-malin)\ **Post date:** [April 28, 2026, 9:57am UTC](https://forum.ansible.com/t/proposal-for-new-windows-modules/45746/1 "2026-04-28T09:57:35Z")
Hi Community, Let me introduce myself. I’m working for the company named Giesecke+Devrient. After (long…) discussion internally we’ve finally open outbound contribution to OSS projects. On my side, I’m using Ansible since 2018, mainly targeting windows hosts and orchestrating via AWX. I’m really grateful to the awesome big project of ansible and would like to expose our internal plugins/modules to the community. We’ve created quite some over years. My initial intent is to add them to the [community.windows](https://github.com/ansible-collections/community.windows?tab=readme-ov-file#contributing-to-this-collection) collection. Looking at the contribution guidelines, seems that scope is now fixed and can’t be extended… I’m attaching **in next post** the existing modules documentation that we have, hoping it would retain your attention. Actually I’m seeking for your guidance if/how our modules would be beneficial by any mean, or if I simply keep it only public in our entreprise github space. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [April 28, 2026, 10:00am UTC](https://forum.ansible.com/t/proposal-for-new-windows-modules/45746/2 "2026-04-28T10:00:16Z")
@lutin-malin Welcome to the Ansible Forum! The `community.` Ansible collections are exactly for this type of community collaboration. > [@lutin-malin](#): > > I’m attaching the existing modules documentation that we have, hoping it would retain your attention. Can please include the list, thank you. ---
**Author:** ![lutin-malin](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/lutin-malin/32/4162_2.png) [@lutin-malin](https://forum.ansible.com/u/lutin-malin)\ **Post date:** [April 28, 2026, 7:07pm UTC](https://forum.ansible.com/t/proposal-for-new-windows-modules/45746/3 "2026-04-28T19:07:50Z")
I indeed forgot to include the documentation. I made a [public repo](https://github.com/gieseckedevrient/gi_de-system-collection) where you can find them, open sourced 😃 . I initially inteded to upload the automatically generated documentation of these modules, but i can’t upload documents here. I paste only the headlines below. These are 48 modules, maybe not all could be interesting for the community ? Let me know your thoughts about this content. I’d be happy to submit any PR to get them included in the relevant collection(s). > **headline of documentation** > > - [win\_adfs\_all\_application\_permission module](#scroll-bookmark-27) – Create-Remove AllRegisteredClients permission for a web api application in ADFS. > - [win\_adfs\_application\_group module](#scroll-bookmark-28) – Create/Remove an application group in ADFS. > - [win\_adfs\_application\_permission module](#scroll-bookmark-29) – Create-Remove a permission between a client application and web api application in ADFS. > - [win\_adfs\_native\_client\_application module](#scroll-bookmark-30) – Create/Remove a native client application in ADFS. > - [win\_adfs\_response\_headers module](#scroll-bookmark-31) – Configure CORS trusted origins from ADFS. > - [win\_adfs\_server\_application module](#scroll-bookmark-32) – Create/Remove a server application in ADFS. > - [win\_adfs\_web\_api\_application module](#scroll-bookmark-33) – Create/Remove a web api application in ADFS. > - [win\_adfs\_web\_api\_application\_info module](#scroll-bookmark-34) – Get web api application identifier in ADFS. > - [win\_cdrom\_facts module](#scroll-bookmark-35) – get fact about optical drive > - [win\_certificate\_acl module](#scroll-bookmark-36) – Update access list on X.509 certificates private key stored in the local certificate store. > - [win\_certificate\_facts module](#scroll-bookmark-37) – Provide information on X.509 certificates available in the local certificate store. > - [win\_certificate\_generate module](#scroll-bookmark-38) – Creates a new self-signed certificate for testing purposes. > - [win\_complus module](#scroll-bookmark-40) – Configure Component services COM+ applications > - [win\_disk module](#scroll-bookmark-41) – The win\_disk module can enable, initialize a disk > - [win\_disk\_label module](#scroll-bookmark-42) – Set disk label > - [win\_domain\_acl module](#scroll-bookmark-43) – Add/Remove access rule on Active Directory object. > - [win\_domain\_kds module](#scroll-bookmark-44) – Create the Key Distribution Services KDS Root Key > - [win\_domain\_msa module](#scroll-bookmark-45) – Manages Windows Active Directory Managed Service Accounts > - [win\_domain\_object\_info module](#scroll-bookmark-46) – Gather information an Active Directory object > - [win\_domain\_organizationalunit module](#scroll-bookmark-47) – Manage domain oarganization unit > - [win\_driver\_printer module](#scroll-bookmark-48) – Install printer driver > - [win\_driver\_store module](#scroll-bookmark-49) – Add driver package to windows driver store > - [win\_driver\_store\_info module](#scroll-bookmark-50) – Get info about installed drivers > - [win\_eventlog\_entry\_info module](#scroll-bookmark-51) – read event logs entries > - [win\_httpurl\_permission module](#scroll-bookmark-52) – Grant a user permission to bind to an HTTP URL > - [win\_json module](#scroll-bookmark-53) – Create, update or delete keys/values in a json file. > - [win\_knownfolders module](#scroll-bookmark-54) – Get the location of a known folder > - [win\_msmq\_certificate module](#scroll-bookmark-55) – Generate MSMQ internal certificate > - [win\_nlb\_cluster module](#scroll-bookmark-56) – Creates/Update/Remove a NLB cluster on the specified interface that is defined by the network adapter name. > - [win\_nlb\_node module](#scroll-bookmark-57) – Creates/Update/Remove a node from NLB cluster on the specified interface that is defined by the network adapter name. > - [win\_nuget module](#scroll-bookmark-58) – download a nuget package from registered source. > - [win\_nuget\_provider module](#scroll-bookmark-59) – Register sources to pull nuget packages > - [win\_package\_facts module](#scroll-bookmark-60) – get Data about msi state on target host. > - [win\_perfmoncounters module](#scroll-bookmark-61) – Create Performance monitoring counters and/or delete them > - [win\_printer module](#scroll-bookmark-62) – Manage printer > - [win\_printer\_config module](#scroll-bookmark-63) – configure printer settings > - [win\_printer\_facts module](#scroll-bookmark-64) – get details about installed printers. > - [win\_rdmsg module](#scroll-bookmark-65) – Send message to remote desktop logged in users > - [win\_rdsessions module](#scroll-bookmark-66) – Disconnect all remote desctop session on running host, excluding console session > - [win\_scmanager\_acl module](#scroll-bookmark-67) – Update access list on Service Manager, to allow read access for remote user. > - [win\_service\_acl module](#scroll-bookmark-68) – Grant specific identities permissions to manage a specific service. > - [win\_smb\_closefile module](#scroll-bookmark-69) – Close any SMB connection to given file > - [win\_system\_eventlog module](#scroll-bookmark-70) – Enable/Disable windows system event log. > - [win\_uiculture\_facts module](#scroll-bookmark-71) – Provide ui culture information > - [win\_wellknownsid\_info module](#scroll-bookmark-72) – Get a wellknown SID details > - [win\_wsfc\_group module](#scroll-bookmark-73) – Manage clustered roles (resource groups) in a failover cluster. > - [win\_wsfc\_group\_info module](#scroll-bookmark-74) – Query clustered roles (resource groups) in a failover cluster. > - [win\_xml module](#scroll-bookmark-75) – Manages XML file content on Windows hosts ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [April 29, 2026, 3:59pm UTC](https://forum.ansible.com/t/proposal-for-new-windows-modules/45746/4 "2026-04-29T15:59:55Z")
@jborean Which of these Windows modules might be good to get into `community.windows` ---
**Author:** ![lutin-malin](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/lutin-malin/32/4162_2.png) [@lutin-malin](https://forum.ansible.com/u/lutin-malin)\ **Post date:** [August 18, 2026, 2:19pm UTC](https://forum.ansible.com/t/proposal-for-new-windows-modules/45746/5 "2026-08-18T14:19:14Z")
I’m wondering if i need to prepare any of the module for proper PR to any of the community collections. @jborean any opinion on this ? Or if is should simply leave it open for anyone interested, and close the contribution aspect of it… ☹