[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

I know I had enabled winrm on the machine 206, thats the reason it pinged back. I know winrm service is running on other machines but I believe i will have to change execution policy and run the ConfigureRemotingForAnsible.ps1 on each of them to enable it to listen for remoting. Is there a way

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

Ok that makes it clearer. I also work with multiple Windows domains, with a single CentOS control node. For your use case ntlm would work as Kerberos adds extra config and also has its own issues. -- You received this message because you are subscribed to the Google Groups "Ansible Project"

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

To revise what I am trying is: I am working in an environment where there are 5 domains that run Windows and Linux systems. The network operators spend weeks and months patching these windows and linux system an it is a pain. I want to automate this patching task. Refering Ansible for Windows

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

Some success here. As per Mike suggested I made changed the vars. Hosts vars as below: [win:vars] ansible_user: ansible.dep...@abc.lcl ansible_password: xxx ansible_connection=winrm ansible_winrm_transport: ntlm ansible_winrm_server_cert_validation: ignore *Output:* vabcs012.aritst.lcl

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

> > plaintext: the specified credentials were rejected by the server You are running over HTTP with Basic auth which doesn't work by default. I recommend you using a HTTPS listener or use an auth setup that supports message encryption over HTTP like NTLM/Kerberos/CredSSP. plaintext:

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

http://docs.ansible.com/ansible/latest/user_guide/windows_winrm.html . What does the entry in the hosts inventory look like? kerberos is generally used when you are using a domain account and need second hop capabilities. The example below uses NTLM which is older but does also work quite well.

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

Now I am getting new error: My first error was: VATCS028.ARITST.LCL | UNREACHABLE! => { "changed": false, "msg": "plaintext: the specified credentials were rejected by the server", "unreachable": true } vabcs012.aritst.lcl | UNREACHABLE! => { "changed": false, "msg":

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

When using an ini inventory you have to define cars like key=value not key: value. Change all your vars to that format and the inventory will be parsable. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

Update: Further I went ahead and created a hosts file in my "ansible-virtualenv" and passed the path in the global ansible.cfg file. Ran the following command in virtualenv and now I have following issue *ansible win -i hosts -m win_ping* [WARNING]: * Failed to parse

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

There seems to a problem in the formatting of your hosts inventory file. I would recommend reading through http://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html . -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

Hi Jordan, Assist me further as I am not able to find content relating to my problem. I installed a virtualenv. Did: - - - Package Version - - - - ansible 2.5.3 (/root/ansible-virtualenvs/ansible-virtualenv/bin/ansible) - asn1crypto

Re: [ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

I have installed and created Virtualenv. Installed pywinrm and this time with no errors. I will get back over this to report how things worked ahead later. I feel blessed reaching out here! On Thu, May 24, 2018 at 3:20 PM Jordan Borean wrote: > There is a conflict between

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

There is a conflict between a system package and pip trying to install another package which in Pip 10 it doesn't handle properly. You can do either of the following - Use a virtualenv and run Ansible from there

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

after i ran the "pip install pywinrm" i am getting following error: Installing collected packages: requests, ntlm-auth, pycparser, cffi, enum34, asn1crypto, cryptography, requests-ntlm, pywinrm Found existing installation: requests 2.6.0 Cannot uninstall 'requests'. It is a distutils installed

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

pywinrm is not installed on the controller, run "pip install pywinrm" on the Ansible host to install that. -- 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

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

- Removed ansible_connection = local - Corrected to ansible_port=5985 Following error occured abc012.abctst.lcl | FAILED! => { "msg": "winrm or requests is not installed: No module named winrm" } But if i check on windows machine (abc012.abctst.lcl) run command "winrm

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

Hey Here are some brief notes - Your host inventory defined ansible_connection twice, once as ansible_connection=local and the other as ansible_connection=winrm. Use local if you want to run things on the Ansible controller and use winrm when you want to run something on the

[ansible-project] Re: Ansible windows patch trouble: Need help for Win Patch Automation using Ansible

Any help on this post please. On