# Need an Intro section for "become" for Windows

**URL:** <https://forum.ansible.com/t/need-an-intro-section-for-become-for-windows/25250>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [August 14, 2017, 5:23pm UTC](https://forum.ansible.com/t/need-an-intro-section-for-become-for-windows/25250 "2017-08-14T17:23:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marvin\_Greenberg](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@Marvin\_Greenberg](https://forum.ansible.com/u/Marvin_Greenberg)\
**Post date:** [August 14, 2017, 5:23pm UTC](https://forum.ansible.com/t/need-an-intro-section-for-become-for-windows/25250/1 "2017-08-14T17:23:45Z")

</div>

How “become” works on windows is confusing in general, and with limited and evolving support (doesn’t work for Kerberos, for example?), a documentation section describing how it works for Windows is important.

Further, the current situation is somewhat limited because of the different variables.

I’ll ignore the deprecated vars. So there is, from inventory:  
ansible\_user, ansible\_pass  
ansible\_become\_user, ansible\_become\_pass, ansible\_become\_method

Then in the playbook,  
remote\_user (\*\*\* which seems to be a noop on windows \*\*\*)  
become\_user, become\_method

And the task  
become\_user, become\_method

Note that for the playbook (play?) and task, there is no equivalent for “ansible\_become\_pass”.

So a playbook like this (with some “password” vars defined in a vault somewhere) cannot work.

---

<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:** [August 14, 2017, 8:46pm UTC](https://forum.ansible.com/t/need-an-intro-section-for-become-for-windows/25250/2 "2017-08-14T20:46:33Z")

</div>

Become support for Windows is currently in an experimental state and because of some of the existing limitations like only working over Basic and CredSSP may change once it is bedded down. I believe because the way it works may change in the future we are trying to hold off on documenting it in case it does change but feel free to raise a PR on the existing docs and we can go from there 🙂

---

<div class="post-metadata">

**Author:** ![Marvin\_Greenberg](https://avatars.discourse-cdn.com/v4/letter/m/51bf81/32.png) [@Marvin\_Greenberg](https://forum.ansible.com/u/Marvin_Greenberg)\
**Post date:** [August 15, 2017, 1:37pm UTC](https://forum.ansible.com/t/need-an-intro-section-for-become-for-windows/25250/3 "2017-08-15T13:37:45Z")

</div>

Fair enough. I think the bigger issues are the current issues with the implementation, which, as you say, is likely to change.