Personally I would avoid using the Packer SSH Windows connector as I've seen a few cases where it has been broken in subsequent Ansible releases. Using the default winrm connector guarantees you are running on a supported/tested connection plugin and it shouldn't break on a release. Unfortunately this means you will have to run the Ansible playbook using the shell-local plugin and not through the ansible plugin as Packer doesn't seem to support this configuration yet. I've been able to use the latest version of Ansible to build Windows images from the evaluation ISO and get it working for Ansible, if you are interested in this I've created a blog post that goes into more details here http://www.bloggingforlogging.com/2017/11/23/using-packer-to-create-windows-images/.
Good luck with whatever route you choose to go with. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" 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/packer-tool/702302ba-b119-4376-8bb1-a1d40417aff1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
