Hi,
I am in the process of building a PowerShell script that will configure all of the networking requirements. Part of this script is creating the NIC Team and Hyper-V Virtual Switch. I am using converged networking, hiding the vSwitch from the OS and then creating virtual adapters on the vSwitch to be used for common functions (Management, Cluster, Live Migration etc.).
The NIC Team will not have any IP information (and will be used to serve the vSwitch)
However I'm in a chicken and egg situation, in that I won't be able run this script until Hyper-V role is installed, but I've typically always joined computers to AD before installing any Windows Roles and Features. But since I don't have any networking configured yet I can't domain join.
One workaround is to IP a standalone NIC which will allow me to domain join > install Hyper-V. Then I could remove the IP from that standalone NIC and then run the script.
IP computer
Rename computer and reboot
Install Hyper-V
Run script
Script will create a Management vEthernet adapter which will have the IP automatically added (same IP as step 1)
Reboot
Domain join
Or, is it OK to install Hyper-V before IP'ing and domain joining? Never done it this way before so no idea of the outcome! Don't even know if the Add Roles Wizard for Hyper-V changes depending on domain joined vs. not domain joined.
Thanks