Closed Jeroenvb3 closed 1 year ago
Thank you for raising issue on community.windows!
We have new windows collections named microsoft.ad
and all of Active Directory related modules are moved into that collection. Also, bugfixes and new features will be implemented for new collection.
If you are still seeing same issue of win_domain_user, could you create new issue on https://github.com/ansible-collections/microsoft.ad ?
Thank you for your understanding.
The win_domain_user
module has been deprecated by https://github.com/ansible-collections/community.windows/pull/516 in favour of microsoft.ad.user. See the migration guide for more info on how to change your code to use the newer module.
In this case microsoft.ad.user
can be used to change any LDAP attributes on the user object, it would look like
- microsoft.ad.user:
name: name
state: present
attributes:
set:
office: anofficevalue
SUMMARY
There is no office field parameter. There is an office field in AD itself.
ISSUE TYPE
COMPONENT NAME
win_domain_user
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
It is on a Debian system.
STEPS TO REPRODUCE
Create a playbook with a win_domain_user task that has the office field.
EXPECTED RESULTS
A user created with an office field in AD.
ACTUAL RESULTS
Office is not a valid parameter.