With -DisableBasicAuth set then you can only use the defaults which NTLM
and Kerberos. You can always check by running winrm get
winrm/config/service and look at the values under the Auth section.
Thanks
Jordan
--
You received this message because you are subscribed to the Google Groups
"Ans
thanks much for the example.
Quick question on ConfigureRemotingForAnsible.ps1 -ForceNewSSLCert
-DisableBasicAuth, does this mean we can use any auth protocol as below
expect Basic(not secure), correct? I am more inclined toward kerberos auth.
* Basic
* Certificate (not the same as SSH keys)
* NT
vmware_guest module allows you to run scripts in 'runonce' section, so you
can run the configure for remoting script as part of this, and any other
steps you need.
I use a playbook like the following to create vm from template. Before
using you have to add a hostname to the 'domainmember' gro
do you have any ideas on configuring winrm in the template(vmware)?
On Wed, Mar 28, 2018 at 11:58 AM, Anil wrote:
> Thanks for elaborate information on ansible with windows.
>
> Winrm is disabled by default. Not sure about the security constraints when
> we enable this service.
>
> I will do res
Thanks for elaborate information on ansible with windows.
Winrm is disabled by default. Not sure about the security constraints when we
enable this service.
I will do research on it.
> On Mar 27, 2018, at 9:32 PM, Jordan Borean wrote:
>
> You can currently only use the winrm connection plugi
You can currently only use the winrm connection plugin with Ansible to talk
to Windows hosts. WinRM allows you to connect using both domain and local
accounts and usually you need administrative rights on that host to both
connect and manipulate group membership. WinRM allows you to authenticate
