OMG! Guys, thank you SO much!!!
I appreciate your help.
On Tuesday, November 7, 2017 at 3:00:48 PM UTC-5, Jordan Borean wrote:
>
> As Jon is saying you are trying to run the win_feature module on localhost
> and not the newly provisioned EC2 server. Here is a very mock playbook that
> you need
As Jon is saying you are trying to run the win_feature module on localhost
and not the newly provisioned EC2 server. Here is a very mock playbook that
you need to follow to get working. Note this is not tested and some things
could potentially be wrong
---
- name: provision new EC2 server
Hi Jon,
Thank you very much for the reply.
Sincerely,
Akim
On Tuesday, November 7, 2017 at 4:10:50 AM UTC-5, J Hawkesworth wrote:
>
>
> I don't use ec2 but I think having the 'connection: local' for your
> windows hosts is causing you problems, as it appears to be attempting to
> use the
I don't use ec2 but I think having the 'connection: local' for your windows
hosts is causing you problems, as it appears to be attempting to use the
win_feature.py (documentation) instead of the win_feature.ps1 (actual
windows module code).
The connection type for windows hosts, at the moment
I updated the playbook. I added a second play to target the new Windows
host and some further steps after the ec2 module to add the new host to the
inventory.
However, I'm still getting the same error. The task is failing.
*Updated Playbook:*
--- # EC2 MODULE - PROVISIONING EXAMPLE
- hosts:
