So I double checked GPOs and nothing was blocking FW or WINRM. I have logged on to the build (prior to the failure as i have a 10m timeout) and I can see though in the event log that the packer account is trying to logon to the domain, rather than a local account. Is there a way to tell packer to do a local logon?
[image: Untitled.png] On Tuesday, 14 April 2020 23:44:55 UTC+1, dragon788 wrote: > > There are a number of potential issues after joining the domain, it could > be group policies that block/disable WinRM or enable the firewall or a > number of other things. Your best bet is to do a run that keeps the input > artifact and doesn't clean up so you can log in yourself and check the > state of the system. you can also do this during the course of Iran by > putting a long sleep and enabling remote desktop or a VNC connection and > connecting to that before the domain join and immediately after the restart > to see what happened. -- 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/3fee0df4-b7ab-4cfd-b6dd-ab7fb6de854c%40googlegroups.com.
