I have not had the same issue as you but I found I had to add the domain
user I was using into the remote management group that is created on the
windows hosts at the time that you run Trond's setup script. I'm away from
the machine right now so can't remember the exact name of the group but it
Jon,
If you can find the correct group for accessing with a domain account,
please let us know.
Using trond's script, I'm able to connect using an admin account local to
the box, but the domain account (which is also in the local Administrator's
account) always fails to authenticate.
Thanks!
Dam
Hi,
I think you may have hit this
issue: https://github.com/ansible/ansible/issues/8588
The name of the group I mentioned in previous post is WinRMRemoteWMIUsers__
on the windows host you want to manage, you need to run the following:
net localgroup WinRMRemoteWMIUsers__ /add DOMAINNAME\domain
There are two things that come into play here:
1. Kerberos. By default, you're not able to perform double-hop using
Kerberos. So, if you have setup Ansible using kinit and the kerberos
changes that are in a PR, you're basically connecting from the control node
to the managed windows node using K
Hi Damon,
We seem to have started a separate thread here.
As posted to the previous thread:
Hi,
I think you may have hit this issue:
https://github.com/ansible/ansible/issues/8588
The name of the group I mentioned in previous post is WinRMRemoteWMIUsers__
on the windows host you want to man
