STEPHEN WILSON
asked on
2016 Hyper-V guest VM Domain controller down
Core 2016 Hyper-V with VM DC, network adaptor showing no IP address. The hyper V management console will no longer connect from my workstation. It is the only DC in our network which is just a few computers. I can see the machine is running on the host but the IP address is showing as {}
Is there a way I can set the IP address of the adaptor on the host? All searches on Google say it should be done from the Management console.
Is there a way I can set the IP address of the adaptor on the host? All searches on Google say it should be done from the Management console.
Is the host on the domain as well?
ASKER
Yes is it is
Do you have RSAT (Remote Server Administration Tools) installed on a desktop machine that is compatible with the host OS version?
If yes, then right click on Hyper-V Manager and at the UAC prompt credential with the domain admin account, then Connect to Server, and choose the Hyper-V host. It should connect so long as the domain admin credentials are cached.
If yes, then right click on Hyper-V Manager and at the UAC prompt credential with the domain admin account, then Connect to Server, and choose the Hyper-V host. It should connect so long as the domain admin credentials are cached.
ASKER
it is not on the workstation I am using, I will download it now
On the host in PowerShell:
Get-VM * | FL
Get-VMNetworkAdapter * | FL
Get-VMSwitch * | FL
Get-NetAdapter
Get-NetLbfoTeam
Please post the results, sanitized if need-be, into a CODE Snippet.
ASKER
I will, Boss has asked me to leave until tomorrow morning. Will post the results then.
Thanks for your help
Thanks for your help
You can also install the free version of 5Nine Manager - this can give you console access to the VM. It runs on core as well.
https://www.5nine.com/5nine-cloud-manager-free/
https://www.5nine.com/5nine-cloud-manager-free/
ASKER
Sorry for the delay in getting back to you. I was under pressure to get some resources available to key staff members. I copied of the Virtual hard drive of the DC and added it to a new Hyper-v host installed on a unused desktop machine. It took an hour to install windows updates, but eventually booted ok. It seems to working ok with a few anomaly's. We have a shutdown in a week and that seems like the ideal time to sort out the original problem, if this fix will hold until then.
Is there anything that you can think of that I should be aware of?
Is there anything that you can think of that I should be aware of?
What are the issues with the recovered DC?
Moving it to a different host means there will be some network issues is one that I can think of. Make sure the binding order is correct for Ethernet connections and make sure the "old" NIC (Device Manager "show hidden devices method") is removed from there and the registry (GUID).
Moving it to a different host means there will be some network issues is one that I can think of. Make sure the binding order is correct for Ethernet connections and make sure the "old" NIC (Device Manager "show hidden devices method") is removed from there and the registry (GUID).
ASKER
I am back onsite tomorrow after some illness. It seems that the External virtual switch on the temporary machine is not providing the server with an internet connection.
Although It has network access. I did add a new virtual network adaptor to the server and configured it with the same Static address it had before. And Created a new External switch.
All shares are visible and accessible. and as imentioned, the company is on shutdown next week for 1 week. So will try to sort things out properly then when I won't be inconveniencing any of the staff.
I will post again tomorrow when I reach the site.
Although It has network access. I did add a new virtual network adaptor to the server and configured it with the same Static address it had before. And Created a new External switch.
All shares are visible and accessible. and as imentioned, the company is on shutdown next week for 1 week. So will try to sort things out properly then when I won't be inconveniencing any of the staff.
I will post again tomorrow when I reach the site.
ASKER
I have managed to connect Hyper-V manager to the 2016 core Hyper-V Host and can now see the original DC. Would it be better to disconnect the temporary copy of the DC, running on a temporary host, and boot the original or copy the temporary DC hard-drive back to the original host and use that. As the original DC has been offline for a week will there be any consequences to using it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the advice. On Monday when the company are on shutdown I should have some undisturbed time to do that.
I will let you know how it goes.
I will let you know how it goes.
10-4
I suggest making sure the temp VM is backed up prior to running the process.
I suggest making sure the temp VM is backed up prior to running the process.
ASKER
Hi Philip, I did as you suggested and everything went well. Made the copy first then Moved the DC hard drive back to the original host. I have also now added a second DC to the domain.
Thanks for the none judgemental advice.
Thanks for the none judgemental advice.
You're welcome. :)