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
{{ message }}
This repository has been archived by the owner on Mar 8, 2023. It is now read-only.
I am facing an issue where packer ends up picking wrong IP during a windows server deployment. It ends up picking the IP before the IP settles down. I am disabling IPv6 and assigning static IPv4 but before IPv4 is assigned using netsh command, WinRM ends up picking default IP (169....). I read about a similar issue and recommendation of using "ip_settle_timeout" but not sure if this has been released yet.
Could someone please help me to figure out what should i change in my unattend.xml file meanwhile the new version gets released?
@VladRassokhin - Any ETA on when the 2.4 version would be released? Really appreciate all the hard work everyone's putting together to make this work.
The text was updated successfully, but these errors were encountered:
Hello Team
I am facing an issue where packer ends up picking wrong IP during a windows server deployment. It ends up picking the IP before the IP settles down. I am disabling IPv6 and assigning static IPv4 but before IPv4 is assigned using netsh command, WinRM ends up picking default IP (169....). I read about a similar issue and recommendation of using "ip_settle_timeout" but not sure if this has been released yet.
Could someone please help me to figure out what should i change in my unattend.xml file meanwhile the new version gets released?
@VladRassokhin - Any ETA on when the 2.4 version would be released? Really appreciate all the hard work everyone's putting together to make this work.
The text was updated successfully, but these errors were encountered: