If the user is a member of the Administrators group on the remote host then you shouldn't have to touch the SDDL of the WinRM listener at all. This is only necessary if the user is a limited user and needs access. Also the `Set-PSSessionConfiguration` is touching the session configuration for the Microsoft.PowerShell endpoint which is not what Ansible is using. To configure the SDDL for the actual endpoint Ansible uses you can run;
winrm configSDDL default Administrators should have Full Control, if you wish to add more users they need to have at least Read and Execute permissions. The fact that the winrs command is working indicates something else is going on. The winrs command will use the credentials of the currently running user, if you are trying to verify if that account has access it is simpler to test with explicit credentials like; winrs -r:fcvwsbdt.PIBCHS.ENET -u:[email protected] -p:UnaPassword DIR C:\ If that works then something else is at play. Can you share; - The output of `winrm get winrm/config/service' on your Windows host - The output of 'pip list' on your Ansible controller Thanks Jordan -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/aa5b13be-4449-4d23-abb3-e9967e975cfe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
