Background:
I’ve upgraded my infrastructure hastily and I done this before the correct way but as I sold my original server I had move the VM’s quickly but with consequences.
The correct way would have been to build the server, add to domain whilst it was live on a different Hyper-V host, assign static IP, change server name, installed windows feature e.g. Hyper-V, etc.
I done this before and all worked fine as the DC is a VM which is was always online to authenticate against without issues e.g. AD, DNS, DHCP. however as mentioned I rushed it and now I’m stuck in a workgroup environment on the Hyper-V server 2016 core install.
current Setup:
x1 HP ProLiant ML350 G6, 3 partitions with partition 1 is OS running Hyper-V server 2016 (Core OS), Partition 2 is VMS Datastore (I store all my Virtual machines here) and Partition 3 is ISO and general software and files.
all other Hyper-V servers are offline and unavailable which would not help as DC VM is offline
Currently the Hyper-V server 2016 core is in a workgroup environment
IP address for the server are statically assigned, and I can ping them from w10 workstation
All workstations are on the domain there are no workgroups and I cannot connect to the domain asthe VM is offline
Firewall has been disabled on server and workstations to allow connectivity for ping, etc
routers been configured for DHCP, DG to allow connectively
Dilemma:
How do I import the DC VM into Hyper-V via PowerShell, so I can turn it on, then I can connect the server to the domain after configuring the server IP statically, so the IP & DNS point to the DC VM and all will be good in the world again as I can use Hyper-V manager to connect and import the other VM via Hyper-V manager?
Question:
I have a Hyper-V server 2016 core install and I’m not sure how to import the virtual machine to get them started using PowerShell with VM’s located on a different partition, does anyone know how to do this?
Thank you, God speed