script failed when VPC option is selected

[hardjopranoto]

The latest version of script failed to provision Windows when VPC (currently in Beta) is selected in the networking option.

Furthermore IP address assignment on VPC on Windows VM is not working but there's workaround.

Workaround:

• Deploy Windows with VPC options deselected.
• Wait until the Windows successfully provisioned and then shutdown the VM
• Assign the Windows VM to the VPC. Select static IP addr assignment.
• Go to Linode --> Windows VM --> Configuration tab and edit the Windows disk
• Here you can make modifications to have 1 Ethernet interface instead of 2 Ethernet for example. Assign static IP.
• Boot your Windows VM with the recently modified Windows disk configuration
• Go to Linode --> Windows VM --> Launch Lish Console --> Select Glish
• Login to to Windows in Glish console. You will notice that there's no Internet connectivity. This is because the VPC IP addr assignment does not work under Windows.
• Go to Settings --> Network & Internet --> Select the Ethernet interface that you assign for VPC earlier and assign the same IP addr that you did under VPC.
• Edit IP settings, assign static IP addr and click Save. You should now have Internet connectivity.

[bitonio]

I've got something working and will submit a PR once sufficiently tested. I am bundling this in a clean Terraform Module.

The idea is to start the Winode-Linux-based prep stages with a public IP (as it is today)
And when you clone the config profile and patch it to make it a Windows profile, with VPC settings
Call that same API in GET mode, and you will have the RFC1918 IP address.
Then the trick is to pass IP down to the unattended.xml file and apply the config.

Without any optimization, I got the full Windows 2022 Server with GUI under 10 minutes

Stay tuned!