# Using ansible on Windows through ssh

**URL:** <https://forum.ansible.com/t/using-ansible-on-windows-through-ssh/28766>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [October 11, 2018, 2:03pm UTC](https://forum.ansible.com/t/using-ansible-on-windows-through-ssh/28766 "2018-10-11T14:03:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aaldi](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@aaldi](https://forum.ansible.com/u/aaldi)\
**Post date:** [October 11, 2018, 2:03pm UTC](https://forum.ansible.com/t/using-ansible-on-windows-through-ssh/28766/1 "2018-10-11T14:03:00Z")

</div>

I’ve noticed some posts from a year ago ([here](https://github.com/ansible/ansible/issues/24726), and [here](https://github.com/ansible/ansible/issues/25344)) about using OpenSSH on windows and avoiding WinRM. Are there any updates to this? Has this been implemented yet?

---

<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:** [October 12, 2018, 4:41am UTC](https://forum.ansible.com/t/using-ansible-on-windows-through-ssh/28766/2 "2018-10-12T04:41:37Z")

</div>

It’s still an ongoing plan but nothing concrete has come out of it yet. TBH the only benefits I see with SSH over WInRM is;

- Faster file transfers
- Simpler authentication with private keys  
The Win32-OpenSSH port is still a bit buggy so I wouldn’t trust it in an environment setup right now.

Thanks

Jordan

---

<div class="post-metadata">

**Author:** ![aaldi](https://avatars.discourse-cdn.com/v4/letter/a/4491bb/32.png) [@aaldi](https://forum.ansible.com/u/aaldi)\
**Post date:** [October 12, 2018, 6:10pm UTC](https://forum.ansible.com/t/using-ansible-on-windows-through-ssh/28766/3 "2018-10-12T18:10:28Z")

</div>

Thanks for the update.

I was hoping it would make using ansible with windows as simple or at least similar to using ansible with Linux. I think that would be a huge improvement (instead of needing to learn two ways of doing things).

What I’m most concerned with is the WinRM issues such as running in an interactive session. Currently I do the task scheduling hack to do that, but asynchronous operations like this are hard to follow and debug. Would that help at all?

---

<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:** [October 12, 2018, 8:25pm UTC](https://forum.ansible.com/t/using-ansible-on-windows-through-ssh/28766/4 "2018-10-12T20:25:56Z")

</div>

You should look at using become [https://docs.ansible.com/ansible/latest/user\_guide/become.html#become-and-windows](https://docs.ansible.com/ansible/latest/user_guide/become.html#become-and-windows). What become does on Windows is to change the logon type from a network to an interactive logon. This allows you to bypass certain limitations you have with WinRM and run things like you would locally. This is a lot simpler than using scheduled tasks and can be used with any module except the raw (script was only recently added in devel).

SSH would still have the same limitations as WinRM when it comes to network logons but become should also do the same thing there.

Thanks

Jordan