Literally set `ansible_shell_type=powershell` for your Windows hosts. It's 
what's in the docs you were linked to.
On Thursday, June 29, 2023 at 1:40:51 AM UTC+10 gonzalo diaz larenas wrote:

> I already did the generation of the public key, then I copied it to the 
> host that has Windows Pro, I did all these steps to the letter, in the 
> inventory.yml file I also made the corresponding changes, based on the help 
> of ansible- doc, but now it throws me a totally different error, I don't 
> really know what it is, I am attaching the corresponding files, I would 
> appreciate your help.
>
>
>
> El lun, 26 jun 2023 a las 9:45, Prady A (<[email protected]>) escribió:
>
>> Hi
>>
>> Login to your control machine with the user you control.
>> 1 . Generate the ssh key using ssh keygen. 
>>  # ssh keygen
>> 2. Copy the pub key to the same user where you created the key.
>> Ex : #ssh-copy-id admistrator@<ip of managed node>
>> 3. Try the adhoc command 
>>  Ex: #ansible -i inventory -m ping
>>
>> Read the ansible doc carefully again.
>>
>>
>>
>> On Mon, Jun 26, 2023 at 22:06, gonzalo diaz larenas <
>> [email protected]> wrote:
>>
>>> Dear, thank you for answering, I already did all those steps, and it 
>>> keeps throwing me the same error.
>>> Using the ssh command [email protected] I can connect directly 
>>> without any problem, I have it configured so that it does not ask me for a 
>>> password when making the ssh connection, the problem happens when I apply 
>>> any ansible ad-hoc command For example ansible -i inventory -m ping all, or 
>>> when I apply a playbook, I attach a file with the ssh connection directly 
>>> to the Windows 10 machine from a centralized Debian server, I would 
>>> appreciate your guidance.
>>>
>>>
>>> El jue, 22 jun 2023 a las 18:34, Brian Coca (<[email protected]>) 
>>> escribió:
>>>
>>>> Did you follow 
>>>> https://docs.ansible.com/ansible/latest/os_guide/windows_setup.html#windows-ssh-setup
>>>>  
>>>> ?
>>>>
>>>>
>>>> -- 
>>>> ----------
>>>> Brian Coca
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Ansible Project" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/ansible-project/CACVha7dqnVE%3DYod5aujn8eTN4AEV25-T-EEqG6J%2Bkc-sVHP-qg%40mail.gmail.com
>>>>  
>>>> <https://groups.google.com/d/msgid/ansible-project/CACVha7dqnVE%3DYod5aujn8eTN4AEV25-T-EEqG6J%2Bkc-sVHP-qg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Ansible Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ansible-project/CAF-YWcbCkbuMChQNxSPQ7zq%2BLB4TUF9M97ggKQtjAxtRKn4vzw%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/ansible-project/CAF-YWcbCkbuMChQNxSPQ7zq%2BLB4TUF9M97ggKQtjAxtRKn4vzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Ansible Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/CAEuB3AqfzuyCkb74ra24%3DiKm585bj2t3VfBUZ1pr3%2BMAeoGYZA%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/ansible-project/CAEuB3AqfzuyCkb74ra24%3DiKm585bj2t3VfBUZ1pr3%2BMAeoGYZA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/560d59d2-5bb1-4f07-a014-13fe75561ed0n%40googlegroups.com.

Reply via email to