By default, the Ansible connection backend will first try to use ansiblesshprivatekeyfile and ansibleprivatekeyfile to authenticate, then fall back to the ansibleuser with ansiblesshpass variables (both are required), before finally falling back to your own host&x27;s SSH config. This behavior may be overwritten by specifying either the --ssh-identity-file option or the --ssh-config option.
There is only 3 tasks here because it's a simple example, but sometimes I have to run a lot of tasks sequentially between 2 servers, Frontend-Backend-Frontend-Frontend and so on. So when I run the playbook, I have a lot of Skipping for all non-targetted server due to the when condition. For both the SSH or WinRM methodology, if you are using a non-Admin user, we recommend logging in to the machine with the non-admin user at least once. This should be done following the Windows initialization process. We recommend this because the full profile will be created and it will be possible for Domotz to discover the Applications.