I'm faced with a weird issue. I have a remote Windows Server 2016 Std Edition and would like to install Hyper-V. The problem I'm facing is that the provider doesn't use DHCP, so the IP is statically assigned by the OS/Machine. During the installation process of the Hyper-V service, I need to create a Virtual Switch to manage the Host and the virtual machines that will be created. The creation of the V-Switch restores the IP settings to DHCP which means that the host machine will never get an IP address, resulting in disconnection of the RDP Session plus never getting access again - unless the company involves into the process. The involvement of the company means there will be an additional cost - which I'd like to avoid.
Would a custom written script, which would run on startup, be a viable idea? Is there another - safe way - to proceed?