We're looking for the same thing. What'd you end up using?
On Monday, January 27, 2020 at 5:26:08 AM UTC-5 yuda@gmail.com wrote:
> Hi,
> I want to create ansible automation for create IPv4 pools on Windows
> Server 2019 operating system.
>
> This is where I want to add the pool:
>
>
If i recall correctly the win_file module doesn't yet support links (pull
requests welcome).
However, you can probably run this via the ansible win_shell or script
module
https://docs.ansible.com/ansible/latest/modules/script_module.html
Thanks Jon for the Response!
Let me explain it in a detailed way.
we would be performing the below Tasks using Ansible and since this is
WIndows Environment, we are using the Powershell Scripts.
1. Create VM ( Working as Expected)
2. Launch the Application (Here, the application is launched as
I dont understand your answer. Can you explain some more
--
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
I would think the only solution would be for them to access a corporate VPN
when they are on anything outside the internal corporate network.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving
Simon-Pierre Diamond
Sent: August 23, 2019 2:44 PM
To: ansible-project@googlegroups.com
Subject: Re: [EXTERNAL] [ansible-project] Re: Ansible and Windows Project
Thank you very much Yarno for your insights.
I will look at Powershell and GPO. In theory, I would like something that can
be version contr
: [EXTERNAL] [ansible-project] Re: Ansible and Windows Project
Hi Simon-Pierre,
GPO's can be managed using PowerShell. Registry based GPO settings
(administrative templates) can be updated through PS as well. Ansible can be
used to execute these PS commands. This will help to get you started
Hi Simon-Pierre,
GPO's can be managed using PowerShell. Registry based GPO settings
(administrative templates) can be updated through PS as well. Ansible can
be used to execute these PS commands. This will help to get you started:
Good to know there's a workaround
I think if you used Kerberos for authentication, and configure your
inventory/group_vars for credential delegation, your ansibles modules will
connect to the shares as the same user that ansible connected as, meaning
you shouldn't have to setup anonymous
Hi
ansible_connection should be 'winrm' and you can set the auth mode using
ansible_transport. So ultimately your vars should be;
ansible_user: Administrator
> ansible_password: RandomePassword
> ansible_port: 5985
> ansible_winrm_scheme: http
> ansible_connection: winrm
>
thank you Hawkesworth, that worked.
On Friday, July 7, 2017 at 12:02:21 PM UTC+2, J Hawkesworth wrote:
>
> Possibly a second hop issue. Try setting ansible_winrm_kerberos_delegation:
> true
> in your windows inventory (documented at the end of this section of the
> documentation page:
>
Maybe you need to use runonce to run the powershell script to enable
remoting:
https://docs.ansible.com/ansible/vmware_guest_module.html
Be aware that unpatched Windows Server 2008 R2 has a bug in WMF 3.0 which
stops winrm from being able to do anything useful. You need to
install
Possibly a second hop issue. Try setting ansible_winrm_kerberos_delegation:
true
in your windows inventory (documented at the end of this section of the
documentation page:
http://docs.ansible.com/ansible/intro_windows.html#inventory
Hope this helps,
Jon
On Wednesday, July 5, 2017 at
Do you have kerberos delegation? This seems like the classic second hop
authentication problem.
On Wednesday, July 5, 2017 at 5:53:13 PM UTC+2, anil kumar wrote:
>
> I am trying to invoke AD commands( I put this into powershellscript) from
> ansible server. I am using Kerberos in the ansible
There is currently a Windows Domain user module on PR, perhaps this fits
your need https://github.com/ansible/ansible/pull/24075 ?
On Wednesday, July 5, 2017 at 5:53:13 PM UTC+2, anil kumar wrote:
>
> I am trying to invoke AD commands( I put this into powershellscript) from
> ansible server. I
Hi Matt,
thanks for the suggestion. I've added
ansible_winrm_operation_timeout_sec: 100 and
ansible_winrm_read_timeout_sec: 120
to my settings and now it works!!
Mike
On Friday, March 17, 2017 at 11:17:19 AM UTC+1, Michele Viviani wrote:
>
> Hi,
> I do have some problems using Ansible with
The only time I've ever seen that behavior is on the first request to a
brand-new Windows AWS instance. For some reason, the shell creation can
take up to 30s, much longer than our default operation timeout of ~5s.
You can try increasing the operation and read timeouts by adjusting the
Also worth checking your /etc/krb5.conf to make sure that the domain
controllers you are pointing at are aware of management.company.corp domain
?
On Friday, March 10, 2017 at 7:10:33 PM UTC, cupcake wrote:
>
> Is the second domain "setup" either in AD as an alternate UPN suffix or
> via a
Is the second domain "setup" either in AD as an alternate UPN suffix or via
a trust relationship with the forest? If it was, it would likely work.
Also, what auth are you using; local acct, domain acct; ntlm, kerberos, etc.
-cupcake
On Thursday, March 9, 2017 at 3:01:10 AM UTC-5, MKPhil
You have to grant the non-admin user/group "Shut down the system"
privileges on the machine(s) in question- default setting only allows that
for Administrators and Backup Operators.
On Sunday, March 5, 2017 at 2:36:08 PM UTC-8, Zubair Saeed wrote:
>
> Hi,
>
> I've added my non-admin user to
Hi,
I've added my non-admin user to *winrm configSDDL default* and when I
win_ping my windows host, I can get a reply. But when I run win_reboot
command, it gives me access denied error.
Do any one have any idea on this?
Regards,
Zubair
On Tuesday, 7 June 2016 12:30:50 UTC+5,
On Thursday, February 23, 2017 at 8:57:13 AM UTC-8, Frank Mehlhop wrote:
>
> Hi,
>
> I work with Windows.
> I would like to use Vagrant on with gitolite my machine and therefore I
> need Ansible.
> Is it a piece of Software to download and install?
> Where do I get it?
> Or how do I get Ansible
That did the trick, thanks!
On Thursday, 8 September 2016 17:49:34 UTC+2, Matt Davis wrote:
>
> (typical cases only need the "read" and "execute" permission)
>
> On Thursday, September 8, 2016 at 8:47:45 AM UTC-7, Matt Davis wrote:
>>
>> Yes, it's absolutely possible. Usually the limiting factor
(typical cases only need the "read" and "execute" permission)
On Thursday, September 8, 2016 at 8:47:45 AM UTC-7, Matt Davis wrote:
>
> Yes, it's absolutely possible. Usually the limiting factor on a default
> install is the WinRM listener ACL- you can see/alter this via:
>
> winrm configSDDL
Yes, it's absolutely possible. Usually the limiting factor on a default
install is the WinRM listener ACL- you can see/alter this via:
winrm configSDDL default
and add the necessary users/groups (or add the existing Windows Remote
Management group).
On Wednesday, September 7, 2016 at 1:33:54
The default WinRM ACL (at least on 2012R2- only thing I have booted to look
at right now) only includes the local Administrators group (and
INTERACTIVE, but not in a usable way). If you do a
winrm configSDDL default
on the host in question, you can add any user you want to that ACL (they
only
Hello,
Just to share my tests, I face exactly the same issues with the same
configuration (same user on a windows box can run remote Powershell
commands even when not in administrators group).
I tried with local user and basic auth and domain user with Kerberos. As
soon as the user is member of
Yes you are right. I tried running ConfigureRemotingForAnsible.ps1 but it
failed. I'm sorry I don't have the error message.
I have little experience of Powershell, but I managed to work through the
script and run the individuals settings manually. Of course I could have
missed something,
Thanks for this.
Since ansible and pywinrm are behaving the same, it occurs to me that the winrm
configuration might not suit pywinrm.
>From the above it appears you have created specific configuration for winrm,
>rather than using the settings that are applied if you run the
Thank you for your help.
*win_ping module verbose, without local admin on remote windows hosts:*
[@ winRM]$ ansible windows -i inventory/dev/hosts -m
win_ping -
<> ESTABLISH WINRM CONNECTION FOR USER: test_user on PORT 5986
TO
<> WINRM CONNECT: transport=plaintext
could you try running playbook with -vv
this should show a bit more information about how ansible is connecting
also check the event log on the windows host to see if the login request is
a success.
Something else you could try is to run the python pywinrm example here
against your host:
I managed to find the root/CIMV2 namespace, and I set the security
permissions of "Execute Methods" and "Remote Enable" and restarted the WMI
and WinRM services. Unfortunately I still receive the same error.
As I mentioned, I can use WinRM from another Windows server via Powershell
session,
I have since tried win_ping and raw, but I haven't had time to test "allow
on Execute Methods and Remote enable" on the windows server.
Both modules work fine when I'm a local admin on the windows server.
Both fail at the "Gather Facts" when I'm not a local admin.
ansible windows -i
I was using the win_ping module. I will try the raw module as suggested.
I will also play around with "allow on Execute Methods and Remote enable" once
I work out what and where they are set.
Thanks guys. I will report back soon.
--
You received this message because you are subscribed to
Interesting. My guess would be that this works, as Ansible doesn't do
anything outside the logged-on user's profile (until you start pushing
tasks that require admin access, of course). What is the exact error you're
getting? Can you use the "raw" module to do something simple like list the
>From here it looks like this is possible, although you would have to tweak
user rights:
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/60de5fcd-33e0-479b-9668-fcf683678a2f/winrm-for-nonadministrative-users?forum=ITCG
I get the impression that the intention for WinRM is for
The IndexError traceback was fixed by
https://github.com/ansible/ansible/commit/07f12539eee2faac5fe831cd31f1f0a5d3e7e661,
and I just pushed a fix for running windows modules from playbooks (
https://github.com/ansible/ansible/commit/57dee4545b3c34d1e66943def8d5e45ee95d66bd
).
The winrm
uninstalling pywinrm installing old version do the trick. problem solved.
Thanks.
On Friday, August 22, 2014 11:05:39 PM UTC+8, Joe G wrote:
I found this issue started happening to me after this update of pywinrm:
I found this issue started happening to me after this update of pywinrm:
https://github.com/diyan/pywinrm/tree/7ab74a4b8fbeb2af707c5628703c485f8d14238d
So, I started using an earlier version:
pip install
https://github.com/diyan/pywinrm/archive/df049454a9309280866e0156805ccda12d71c93a.zip
Joe
Any thoughts on this Chris?
On Fri, Aug 22, 2014 at 11:05 AM, Joe G joe.gard...@ni.com wrote:
I found this issue started happening to me after this update of pywinrm:
https://github.com/diyan/pywinrm/tree/7ab74a4b8fbeb2af707c5628703c485f8d14238d
So, I started using an earlier version:
Just FYI, it's also possible to run Ansible without any install on a
Windows host.
Send commands through WinRM (pywinrm as Python implemention) en send files
over SMB to administrative shares. Just make sure you only allow the
ansible host on it through the firewall.
The only downside is the
Hi guys,
Please don't bump old threads :)
And no, it's not guaranteed that Ansible will continue to run on a Windows
host, we reserve the right to use native Linux services (even /dev/random)
so you will need to run Ansible from a Linux/Unix/OSX control host.
Managing Windows remote hosts is
42 matches
Mail list logo
