# Community.windows compatibility issue with Ansible 2.15 in AWX causing failure in \`unix\_computers\_in\_ad\` role

**URL:** <https://forum.ansible.com/t/community-windows-compatibility-issue-with-ansible-2-15-in-awx-causing-failure-in-unix-computers-in-ad-role/45741>\
**Category:** Get Help\
**Tags:** windows, ansible-project, ubuntu, collections, awx, kubernetes\
**Created:** [April 27, 2026, 1:25pm UTC](https://forum.ansible.com/t/community-windows-compatibility-issue-with-ansible-2-15-in-awx-causing-failure-in-unix-computers-in-ad-role/45741 "2026-04-27T13:25:45Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![noor](https://avatars.discourse-cdn.com/v4/letter/n/c67d28/32.png) [@noor](https://forum.ansible.com/u/noor)\
**Post date:** [April 27, 2026, 1:25pm UTC](https://forum.ansible.com/t/community-windows-compatibility-issue-with-ansible-2-15-in-awx-causing-failure-in-unix-computers-in-ad-role/45741/1 "2026-04-27T13:25:46Z")

</div>

## Title

community.windows compatibility issue with Ansible 2.15 in AWX causing failure in `unix_computers_in_ad` role

* * *

## Description

I am running the `unix_computers_in_ad` role from the `oneidentity.authentication_services` collection in **AWX** , and encountering a failure that appears related to `community.windows` compatibility with my Ansible version.

The playbook targets Ubuntu (Linux) hosts and is expected to query Active Directory and generate a report.

The report is generated successfully, but the role fails during execution with the following generic error:

```auto
The module failed to execute correctly, you probably need to set the interpreter.
See stdout/stderr for the exact error

```

* * *

## Environment

- AWX: running on Kubernetes (k3s)
- Ansible Core: `2.15.13`
- Python: `3.9`
- Execution: AWX Execution Environment (containerized)
- Target hosts: Ubuntu Linux
- AD environment: Windows Domain Controller available

* * *

## Collections (requirements.yml)

```yaml
---
collections:
  - name: oneidentity.authentication_services
  - name: community.windows
    version: "<3.0.0"
  - name: microsoft.ad

```

> Note: I pinned `community.windows` to `<3.0.0` because newer versions require Ansible \>= 2.16.

* * *

## Playbook

```yaml
---
- hosts: all
  gather_facts: false

  vars:
    unix_computers_in_ad_facts_generate: true
    unix_computers_in_ad_reports_generate: true
    unix_computers_in_ad_reports_backup: true

    unix_computers_in_ad_reports_host: report-host

    unix_computers_in_ad_reports:
      - src: unix_computers_in_ad_report.csv.j2
        dest: /home/reports/unix_computers_in_ad_report.csv
      - src: unix_computers_in_ad_report.html.j2
        dest: /home/reports/unix_computers_in_ad_report.html

  roles:
    - oneidentity.authentication_services.unix_computers_in_ad

```

* * *

```yaml
Output

```

```auto
TASK [oneidentity.authentication_services.unix_computers_in_ad : fail] *********
fatal: [UB-Host-1]: FAILED! => {"msg": "The module failed to execute correctly, you probably need to set the interpreter."}
fatal: [UB-Host-2]: FAILED! => {"msg": "The module failed to execute correctly, you probably need to set the interpreter."}

```

However, the report generation step still succeeds:

```auto
ok: [UB-Host-1 -> <report host>]

```

* * *

## Observations

- Reports are generated but appear empty or incomplete.
- The role previously relied on `community.windows.win_domain_object_info`, which is deprecated/removed in newer versions.

* * *

## Questions

1. Is this issue caused by `community.windows` compatibility with Ansible 2.15 in AWX?
2. What is the recommended approach for using this role with newer `community.windows` or `microsoft.ad` collections?

* * *

## Additional Info

- `vastool` is installed and working on target hosts.
- AD connectivity is functional.
- Similar roles (e.g., `local_unix_users`) work correctly in the same environment.

* * *

Any guidance or clarification would be appreciated 🙏