Re: [ansible-project] Re: Ansible Windows Deployment - 'Connection aborted.', error(104, 'Connection reset by peer')

i dont understand what this mean You need both the hotfix and the registry keys set for the connection to break like this, having one or the other is not enough. A On Sun, Aug 16, 2020 at 5:40 PM Tony Wong wrote: > I have same problem. I enabled winrm over https and i can see it listen to >

[ansible-project] Re: Ansible Windows Deployment - 'Connection aborted.', error(104, 'Connection reset by peer')

I have same problem. I enabled winrm over https and i can see it listen to 5986. but a simple win_ping is not working On Monday, September 17, 2018 at 2:46:26 PM UTC-7 jbor...@gmail.com wrote: > You need both the hotfix and the registry keys set for the connection to > break like this, having

Re: [ansible-project] Re: ansible windows inventory get hostname/user/password ad-hoc from external script

I've managed to write a workaround, by writing a playbook which runs the get-admin-credential command task, with "delegate_to: localhost". >From this I build a dictionary with the parsed values for host/login/password from the command output, and in the ansible inventory file I do a hostvars

[ansible-project] Re: ansible windows inventory get hostname/user/password ad-hoc from external script

Would constructing your own lookup plugin be an option? There seem to be lots of lookup plugins that look things up in various kinds of vaults: https://docs.ansible.com/ansible/latest/plugins/lookup.html#plugin-list Could you create one of your own. If you created an inventory plugin, rather

[ansible-project] Re: ansible windows

If you are wanting to play around with things there's no harm in it. If you are wanting to use it in production I would wait until some of the kinks are ironed out and 2.10 is officially released. That's not to say you can use it side by side and selectively try out various modules in the

[ansible-project] Re: ansible windows

Would it be wise to wait for 2.10? On Friday, March 13, 2020 at 4:03:56 PM UTC-5, Jordan Borean wrote: > > I also forgot to mention that while some components may work in 2.9 this > collection will not be tested against this version and will officially be > designed to work with 2.10 onwards. >

[ansible-project] Re: ansible windows

I also forgot to mention that while some components may work in 2.9 this collection will not be tested against this version and will officially be designed to work with 2.10 onwards. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To

[ansible-project] Re: ansible windows

That is because the ansible.windows collection because the current released versions at https://galaxy.ansible.com/ansible/windows are all beta versions. The ansible-galaxy cli tool does not use any pre-release versions in it's check and the only way to install it is to explicitly set the

[ansible-project] Re: Ansible Windows Custom Modules

Anyone? Please, even if just a brief answer. -- 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+unsubscr...@googlegroups.com. To view this

[ansible-project] Re: Ansible & Windows Management

Thank you for your reply I will check and revert back On Tuesday, April 23, 2019 at 3:55:29 AM UTC+2, Tony Chia wrote: > > To connect to windows from ansible you can use wintm instead of the > default winrm connection type -- You received this message because you are subscribed to the Google

[ansible-project] Re: Ansible Windows Deployment - 'Connection aborted.', error(104, 'Connection reset by peer')

You need both the hotfix and the registry keys set for the connection to break like this, having one or the other is not enough. Another thing to note is that this only applies to Server 2008, the 2008 R2 edition works just fine with TLSv1.2. So if this is the original 2008 version (and not

[ansible-project] Re: Ansible Windows Deployment - 'Connection aborted.', error(104, 'Connection reset by peer')

Hello Jordan Thanks for your response. The target server already has Powershell3.0, I went ahead and installed the hotfix and reinstalled the http and https listeners, but still isn't working. The thing with TLS1.2 is that I have 2 win 2008 servers and they both have exact same registry

[ansible-project] Re: Ansible Windows Deployment - 'Connection aborted.', error(104, 'Connection reset by peer')

Hi The error you are seeing is that because the underlying HTTP stack on Windows is beaking the connection and may or may not be related to WInRM itself. If you are trying to connect to server 2008 then you will need PowerShell v3.0 which has an issue with the memory settings. Make sure that

Re: [ansible-project] Re: [Ansible windows] "kerberos: authGSSClientStep() failed: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Generic error (see e-text)', -176532

arcfour is RC4 which isn't supported, problematic, and a broken encryption standard. You should be using at least AES, a list of encryption types in krb5 can be found here http://web.mit.edu/kerberos/krb5-1.12/doc/admin/enctypes.html#enctype-compatibility. -- You received this message because

Re: [ansible-project] Re: [Ansible windows] "kerberos: authGSSClientStep() failed: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Generic error (see e-text)', -176532

Hello Jordan I moved from https to http I removed the des kerberos options: # default_tgs_enctypes = des-cbc-crc arcfour-hmac-md5 default_tgs_enctypes = arcfour-hmac-md5 # default_tkt_enctypes = arcfour-hmac-md5 des-cbc-crc default_tkt_enctypes = arcfour-hmac-md5 # preferred_preauth_types =

[ansible-project] Re: [Ansible windows] "kerberos: authGSSClientStep() failed: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Generic error (see e-text)', -1765328

Because you are running over https, message encryption is not being run so that post you linked to is technically unrelated. In saying that, I have no idea about your environment setup, but RC4 and DES are effectively broken and you should avoid using in any case. Unless you have set that on

[ansible-project] Re: [Ansible windows] "kerberos: authGSSClientStep() failed: (('Unspecified GSS failure. Minor code may provide more information', 851968), ('Generic error (see e-text)', -1765328

Using an USA domain user instead of a EUR domain user move me to another issue *"kerberos: Bad HTTP response returned from server. Code 400"* I found out this question here : https://groups.google.com/forum/#!topic/ansible-project/WJbhN3VYMmI but nothing could help me. I have to say, my first

[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

[ansible-project] Re: Ansible windows issue about running yml task

Yep, the post above is your problem, you are trying to run a list of tasks under ansible-playbook when you need to structure it like a play. When referring to roles you can just have the tasks but the root playbook must include things like hosts, tasks, roles and so on as the root keys. Thanks

[ansible-project] Re: Ansible windows issue about running yml task

do you have "tasks:" defined before your win_file? try this - hosts: all tasks: - name: Create directory structure win_file: path: C:\Temp\folder\subfolder state: directory On Wednesday, March 14, 2018 at 4:35:40 AM UTC-7, selim sarısu wrote: > > Hi Friends , > > When I tried

[ansible-project] Re: Ansible windows issue about running yml task

This is one of my plays. - name: Make Tools folder win_file: path: C:\Tools state: directory - name: Make build folder win_file: path: C:\build state: directory - name: Make TEMP folder win_file: path: C:\TEMP state: directory

[ansible-project] Re: Ansible windows issue about running yml task

You don't have whitespace right, which Ansible is very finicky about. Try: - name: Create directory structure win_file: path: C:\Temp\folder\subfolder state: directory Don't use "tab" keys, use your space bar. HTH, Larry On Wednesday, March 14, 2018 at 4:35:40 AM UTC-7, selim sarısu

[ansible-project] Re: Ansible Windows MSI

There are no plans to do this, the ConfigureRemotingForAnsible.ps1 script does what we need so far and is only meant to be used for development purposes. When running in a production environment you should have your own process that fulfils your requirements both on a technical and security

[ansible-project] Re: Ansible Windows: Add account to group administrators FR/US

Hello Jordan, Thank you very mutch. I had the same raissonement with a custom script. Yesterday, i created a specifical script to ckeck a groups. function Get-AdministratorsGroupName { $LocalGroup = @('Administrators', 'Administrateurs', 'Domain Admins') foreach ($Group in

[ansible-project] Re: Ansible Windows: Add account to group administrators FR/US

Hey One thing you can do is use the win_region module https://docs.ansible.com/ansible/win_region_module.html to change the region of your hosts to a common value. If this isn't what you can do, you can also run an adhoc command to determine the group name based on the SID. Give the below

[ansible-project] Re: Ansible Windows

A list of authentication options that are available to a Windows host through WinRM are shown here http://docs.ansible.com/ansible/intro_windows.html#authentication-options. In short if you need to authenticate with a domain account Kerberos is recommended as it is the most secure but NTLM and

[ansible-project] Re: Ansible Windows

No you can't do ssh connections to (unmodified) windows machines at the moment, unfortunately. Even if you did set up a third-party ssh server on windows, to use the ansible windows modules, you have to be using 'winrm' transport, and would likely have to go to a lot of trouble to allow

[ansible-project] Re: Ansible Windows become_user per task?

Yeah, docs forthcoming for this stuff, but you need to specify a couple more things to make it work (since the global *nix defaults don't make sense under Windows): First and foremost, you never actually said you want to "become", just "who" you want to become- you need to add "become: yes"

Re: [ansible-project] Re: Ansible windows modules

Hi Stavris, I am not familiar with DISM tool then I have not tried this workaround yet. For example, if the system has already the KB, this task does nothing, on the other hands this system does not have the KB it should be fixed the KB by this task ( it called idempotence ). I would like to run

Re: [ansible-project] Re: Ansible windows modules

Hello Takeshi, what do you actually mean by asking if the workaround has idempotence? That you run this and nothing changes/happens on the target host? If you tried it so far, then you can see if the .Net Framework is installed only by searching the installed Windows updates. There you will

Re: [ansible-project] Re: Ansible windows modules

Hello Stavos, I would like to run the ansible to use your workaround for ms patch. By the way, can your workaround have Idempotence ? BestRegards, Takeshi 2016-02-29 18:36 GMT+09:00 Stavros : > Hi Quang, > > you can also try to extract the x64-Windows8.1-KB2934520-x64.msu,

[ansible-project] Re: ansible windows raw module no response?

An optional configurable timeout would be nice, but I have some tasks that run for over 60 minutes so I would not want a short default. Can you use Remote Desktop to check if your program is well perhaps? On Monday, August 1, 2016 at 2:02:45 PM UTC+1, fcx...@gmail.com wrote: > > Thanks for

[ansible-project] Re: ansible windows raw module no response?

Thanks for your answer.I am not sure whether my program is well.But I think ansible should close the task if the task exec too long. 在 2016年7月28日星期四 UTC+8上午7:34:49，J Hawkesworth写道： > > If it is always running then may be you need to set up whatever the > run.bat does as a windows service. >

[ansible-project] Re: ansible windows raw module no response?

If it is always running then may be you need to set up whatever the run.bat does as a windows service. You can install nssm.exe and use win_nssm module to install programs as services, and then use the win_service module to start and stop them. You can use fetch module against windows

[ansible-project] Re: Ansible Windows Winrm Authentication or permission failure.

I ran into this same problem with ansible 2.1.0.0, correctly configured winrm and powershell. The solution was adding the powershell directory to the PATH on the target machine. The ansible error messages have so far never been related to the actual problem, which is kind of impressive. On

[ansible-project] Re: Ansible windows modules

Actually, when I update with all the latest updates from Windows, I can go through the problem, means, with the latest Windows update, you're good with msu installation. Thank you all! -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To

[ansible-project] Re: Ansible windows modules

Hi Quang, you can also try to extract the x64-Windows8.1-KB2934520-x64.msu, which will give you the Windows8.1-KB2934520-x64.cab. For the installation try this: DISM.exe /Online /Add-Package /PackagePath:C:\Temp\Windows8.1-KB2934520-x64.cab /NoRestart /Quiet You'll have to reboot the server

[ansible-project] Re: Ansible windows modules

I have used the workaround described in the article to install a hotfix. I expanded the .msu and then used raw to run dism.exe to install the expanded file, so I hope the same workaround will work for you. Hope this helps, Jon -- You received this message because you are subscribed to the

[ansible-project] Re: Ansible windows modules

The problem with installing msu file via WinRM (as Ansible uses Py connects to window host via WinRM). I grab this article on the net (http://www.hurryupandwait.io/blog/safely-running-windows-automation-operations-that-typically-fail-over-winrm-or-powershell-remoting) and this one from MS

[ansible-project] Re: Ansible windows modules

Hi Stavros, I think you're right on x64-Windows8.1-KB2934520-x64.msu. I tried to dumb the installation log and found access denied when running the web installation package. I think there is something wrong on my environment setting that cause about security issue, try with another

[ansible-project] Re: Ansible windows modules

Quang, I suggest you try running the installation as a user with Administrative privileges. You may also find you need to temporarily disable UAC prompting for Administrative users only, which on Server 2012 R2 can be achieved by modifying

[ansible-project] Re: Ansible windows modules

I'm using the following code for installing msi's, e.g.: $msi = @('D:\Temp\Pscx-3.2.0.msi', 'D:\Temp\notep.msi') foreach ($msifile in $msi) { Start-Process -FilePath "$env:systemroot\system32\msiexec.exe" -ArgumentList "/i `"$msifile`" /qn /passive" -Wait } Stavros -- You received this

[ansible-project] Re: Ansible windows modules

Jon, I have tried with win_package, as .NET framework 4.5 can not be uninstalled so I just grab a fake product_id (not sure for the other but for me, I'm using ansible 1.9.3 and product_id param should be *productid* without dash) and the results are the same as using raw command. If I use the

[ansible-project] Re: Ansible windows modules

The NDP452-KB2901907-x86-x64-AllOS-ENU.exe package contains the framework for various Windows versions. Have you tried to install it from the cli? E.g. start powershell as admin and try to install it? In my case, I wrote a playbook in order to install it on a W2012R2 using ansible. Here an

[ansible-project] Re: Ansible windows modules

I would recommend trying the win_package module which can take properties and, if you capture the product_id you can use that in your playbook to make sure it only attempts installation once. Hope this helps, Please report back if this works for you so others can learn from your experience.

[ansible-project] Re: Ansible Windows Winrm Authentication or permission failure.

Someone else has posted something simliar as a bug report here - https://github.com/ansible/ansible/issues/14085 Since both you and the bug reporter are experiencing a failure to create a directory in the user's temp folder, I'm wondering if your users' temp folder is actually present? The

[ansible-project] Re: Ansible Windows Winrm Authentication or permission failure.

Hm, that's interesting. It doesn't make sense that raw commands work but not the basic win_ping module. Yes, it does sound like it's something to do with your module or pywinrm setup. My main issue for connection was with kerberos, but that's because the user I'm using to authenticate with is

[ansible-project] Re: Ansible windows kerberos issue

I will give it a try and let you know. Thanks in advance for your help ! On Friday, 22 January 2016 23:51:37 UTC+5:30, Joe Levis wrote: > > Mayur, > > Make sure your Linux Control Machine is bound to the same domain as your > target Windows VM. After much reading and debugging, I realized my

[ansible-project] Re: Ansible Windows Winrm Authentication or permission failure.

Hi Joe, Thanks for getting back to me I did both the items when I setup the control server and windows client. Upon further investigation I can successfully execute raw commands which shows the config is correct, it's just the win_pin that fails for some reason so I presume I can't run

[ansible-project] Re: Ansible windows kerberos issue

Mayur, Make sure your Linux Control Machine is bound to the same domain as your target Windows VM. After much reading and debugging, I realized my Ubuntu server where I was running Ansible was not bound to the Domain. *Another thing...* I had to run the kinit command with the below flags on

[ansible-project] Re: Ansible Windows Winrm Authentication or permission failure.

Hi Dan, I ran into a lot of issues when trying to get Ansible to connect to my remote Windows Server 2012 R2 VM. I finally got it working - maybe my solutions will help you. *A couple questions:* 1. Did you set up your Ansible Control Machine following the official documentation to a

[ansible-project] Re: Ansible windows kerberos issue

Hi Jon, Thanks for your inputs If I manage windows machine using local administrator account then it works. But for AD account following is the error. I can successfully do kinit with domain user and klist displays appropriate ticket ESTABLISH WINRM CONNECTION FOR USER: on PORT 5986 TO

[ansible-project] Re: Ansible windows kerberos issue

Hi Mayur, You usually get that message when kerberos is not configured properly on your ansible controller. Please ensure you have followed the setup instructions here: http://docs.ansible.com/ansible/intro_windows.html#configuring-kerberos Without this, the ansible controller does cannot

[ansible-project] Re: Ansible Windows

Yes, there is a thread on the Ansible Development list detailing progress on this. -- 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

Are there plans on supporting the kerbros authentication so this works in domain environments? On Friday, October 17, 2014 11:02:06 AM UTC-4, Bryan Cochrane wrote: I am trying to setup windows remoting for ansible. I have Ansible version 1.7.2, ee-bryan is Windows 8.1, ee-csg is Windows

Re: [ansible-project] Re: Ansible Windows

I get exactly the same... *☿* |staging:e38026ddcaae ✗| → ansible -i ./provisioning/hosts windows -m win_ping 54.67.74.52 | FAILED = Traceback (most recent call last): File /usr/local/lib/python2.7/site-packages/ansible-1.7.2-py2.7.egg/ansible/runner/__init__.py, line 561, in _executor

Re: [ansible-project] Re: Ansible Windows

I installed ansible from source, and it now works a treat! *☿* |staging:e38026ddcaae ✗| → ansible -i ./provisioning/hosts production -m win_ping 54.67.74.52 | success { changed: false, ping: pong } Thanks for ansible, and for great resources to fix issues. cheers P. On

Re: [ansible-project] Re: Ansible Windows

That IndexError has been fixed in ansible devel. It's not really a pywinrm issue, but an ansible issue in trying to handle the HTTPError from pywinrm. It happens when the HTTPError from urllib2 isn't a file-like object (despite what the docs say in

Re: [ansible-project] Re: Ansible Windows

This is probably a good error to file upstream with winrm, such that on this error it can present something better to the user. We could catch it, but an IndexError is the wrong sort of exception to be catching here. On Sun, Oct 19, 2014 at 2:44 PM, Trond Hindenes tr...@hindenes.com wrote:

[ansible-project] Re: Ansible Windows

Have you prepared your Windows nodes as per documentation? Basically, yuu need to enable WinRM connections over HTTPS, and enable Baisc auth for your WinRm endpoint. Look at the documentation, there's a script that will do those things for you. I've uploaded a newer version of that script here: