Hi, i'm running the exact same provisioner script on both the Azure and 
Hyper-V builders.
After joining the domain the azure script won't reconnect to winrm but the 
Hyper-V script will.  (both scripts build as the same computer name which 
already exists in Active Directory - so they are getting identical same 
group policy)

The Azure builder makes a successful TLS connection to the remote vm in 
Azure but immediately exits and retries periodically until timeout. I can 
RDP to this machine ok.

Any ideas on what could be going on? I know the Hyper-v builder uses a 
winrm_username & winrm_password, whereas the Azure builder just uses a 
winrm_username and then relies on an Azure key vault. 

-- 
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/1848a6a4-a7fb-4223-a7a0-7e972561a591%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to