Hi @Gabo, Thanks for your suggestion and sorry for the late reply. I think you might be right that after joining the domain, Packer failed to run "window-restart" command in the temporary VM. But there is no way log into that temporary VM to check as I don't know the admin credentials which Packer created for the temporary VM, and cannot also use my domain credentials to log in as the VM hasn't been configured for remote access. So what should I do now in terms of troubleshooting, surely feel like this is the packer bug but seems like no one could really figure out what is wrong with it as Packer is supposed to log back to the VM after domain join and run the rest of the template. Regarding the "*Add-WindowsFeature" *that you mentioned in the above post, I believe that wasn't the issue as Packer couldn't reach it if it couldn't pass the windows-restart step which it failed to do so. Do you know the master admin user that Packer created to generate the temporary VM in Azure? I hope you could help? Have been with this issue for a month and not many Packer maintainers could help me out :(
Thanks, -- 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/77fc8e90-d57b-4930-b8c3-3eba6dd808c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
