You can actually see kerberos failing within the same play... It will run
various commands then just randomly run into one that it gets the kerberos
error on.
[image: ansible-krb.png]
This is what that play looks like in yaml:
tasks:
- name: Ensure SMBv1 is disabled
win_optional_feature:
name: smb1protocol
state: absent
- name: Initialize Disk 1
win_shell: Initialize-Disk -Number 1
ignore_errors: yes
- name: Wait 15 seconds for disk initilization
pause:
seconds: 15
- name: Partition Disk 1
win_partition:
drive_letter: E
partition_size: -1
disk_number: 1
state: present
ignore_errors: yes
#Ignore errors because this module doesn't handle idempotency well
- name: Format Disk 1 as E drive
win_format:
drive_letter: E
file_system: NTFS
new_label: DATA
ignore_errors: yes
#Ignore errors because this module doesn't handle idempotency well
- name: Ensure SMBv1 is disabled
win_optional_feature:
name: smb1protocol
state: absent
On Sunday, March 1, 2020 at 2:47:01 AM UTC-8, Jordan Borean wrote:
>
> Plaintext means basic auth over http which is rejected by windows because
> it is not encrypted. Basic auth also does not work for domain accounts but
> unfortunately it is the default for backwards compatibility reasons when
> the username specified is not in the UPN format.
>
> If you are connecting to a domain account you can set
> ansible_winrm_transport: ntlm to get you going but I highly recommend you
> get Kerberos auth working for domain accounts.
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/0cf004c8-ee3d-47de-92ec-7b5e160e638a%40googlegroups.com.
