Just change the username and password to that domain account. Typically the
user is either in the Netlogon 'DOMAIN\user' form or the UPN
'u...@domain.com' form. The latter is preferred as it's what is required
for Kerberos auth which should be used for domain logons.
--
You received this
Thanks I changed the auth to ntlm and works now
another question how do I use a domain account instead of a local
administrator?
On Sat, Apr 25, 2020 at 3:28 PM Jordan Borean wrote:
> You WinRM service has been set to reject Basic auth. You need to change
> the auth to something like kerberos
You WinRM service has been set to reject Basic auth. You need to change the
auth to something like kerberos (for domain auth) or ntlm using the
ansible_winrm_transport var.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe
It's best to move to an Agent-Based configuration management Tool Such as
SaltStack for Windows if your Machines are been managed by GPO which is
preventing Ansible to Connect.
Or else configure everything before the machine joins the Domain
--
You received this message because you are
I am getting same issue. I cannot allow unencrypted winrm as thats set up
gpo.
this is from my windows client
PS C:\scripts> winrm get winrm/config
Config
MaxEnvelopeSizekb = 500
MaxTimeoutms = 6
MaxBatchItems = 32000
MaxProviderRequests = 4294967295
Client
There are multiple reasons why Windows will reject the credentials from
Ansible which could be;
- The user is not part of the local administrator group
- As per your post this doesn't seem to be the case
- You are running over http and basic auth doesn't support message
