- something go wrong with the trust, all the links are not fully establish
430
432
- wait several minutes and relaunch the playbook
skipped 4 lines
435
437
failed: [192.168.56.xx] (item={'key': 'DragonsFriends', 'value': ['sevenkingdoms.local\\tyron.lannister', 'essos.local\\daenerys.targaryen']}) => {"ansible_loop_var": "item", "attempts": 3, "changed": false, "item": {"key": "DragonsFriends", "value": ["north.sevenkingdoms.local\\jon.snow", "sevenkingdoms.local\\tyron.lannister", "essos.local\\daenerys.targaryen"]}, "msg": "Unhandled exception while executing module: Either the target name is incorrect or the server has rejected the client credentials."}
436
438
```
437
439
438
-
#### Error Add-Warning
440
+
### Error Add-Warning
439
441
440
442
- You got an "Add-Warning" error during the user installation.
441
443
- Upgrade to community.windows galaxy >= 1.11.0
skipped 6 lines
448
450
"msg": "Unhandled exception while executing module: The term 'Add-Warning' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."}+
449
451
```
450
452
451
-
#### A parameter cannot be found that matches parameter name 'AcceptLicense'
453
+
### A parameter cannot be found that matches parameter name 'AcceptLicense'
452
454
453
455
- If you got this kind of error you got an ansible.windows version >= 1.11.0
454
456
- This version add the parameter AcceptLicense but it is accepted only for PowerShellGet module >= 1.6.0 and this one is not embededded in the vms.
skipped 9 lines
464
466
}
465
467
```
466
468
467
-
#### old Ansible version
469
+
### old Ansible version
468
470
469
471
```bash
470
472
ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
skipped 8 lines
479
481
480
482
solution : upgrade Ansible
481
483
482
-
##### old ansible.windows version
484
+
#### old ansible.windows version
483
485
```bash
484
486
ERROR! couldn't resolve module/action 'win_powershell'. This often indicates a misspelling, missing collection, or incorrect module path.
