You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just tried to build the hyperv for 2012R2 but gets stuck waiting for WinRM to become available
I tried to log to the image IP with Enter-PSSession -ComputerName 169.254.27.232 -UseSSL -Credential $credentials without success. Then I log in the machine and run the winrm quickconfig which said that it was not enabled for remote access. I enable it but still couldn't connect.
As ipconfig in machine showed a IP 169.254.27.232 I installed the Web-Server role and I could connect to it with it but not with the IP from the packer log.
I been investigating a bit more on this issue and it turns out that de default network switch that packer creates in hyper-v is an internal network.
From my understanding then no internet is available thus is not possible to download the provisioning script and install all the required windows updates.
As a workaround I changed it manually to external and now the process is able to move forward.
The nice thing would be to use the NAT feature only available through powershell and create an internal network with internet access.
Hi,
I just tried to build the hyperv for 2012R2 but gets stuck waiting for WinRM to become available
I tried to log to the image IP with
Enter-PSSession -ComputerName 169.254.27.232 -UseSSL -Credential $credentials
without success. Then I log in the machine and run thewinrm quickconfig
which said that it was not enabled for remote access. I enable it but still couldn't connect.As
ipconfig
in machine showed a IP 169.254.27.232 I installed the Web-Server role and I could connect to it with it but not with the IP from the packer log.I followed suggestions from this related repo to test some things.
The text was updated successfully, but these errors were encountered: