I have added some variables in Packer Azure template so that the temporary VM could be added to the Azure virtual network group, so it can reach other servers in our internal network. However, it still could not access the server's resources (it could ping them with IP addresses) even after being added to the domain by the scripting to be run during packer build. I found out that it was probably because the local admin user of that temporary VM was not in the AD and couldn't access other servers to get the resources (technical credentials of AD user will be asked to enter to be able to get access). So, just wondering is there any other ways that we could log Packer as our AD user in the temporary VM during the build to avoid this kind of access permission issues?
Thank you -- 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/33e404f2-3857-486d-ac04-985958d992ad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
