How do i fix a virtualized domain controller which won't boot when I've lost remote management connectivity to its host because the 'only' DC is down !!
I have a single domain controller which runs in a virtual machine hosted by Hyper-V server 2019 which is a domain member but only runs server core i.e. command line and powershell. My dc is showing as started though I believe the boot is actually failing. I cannot get any further because I cannot connect Hyper-V manager to the Hyper-V server because domain connectivity is screwed up since my only DC is down - no DNS , no Active Directory, no authentication etc.. How can I fix the boot problem my dc is suffereing from when I do not have any access to it. I WAS in the process of setting up a second dc on another physical machine as part of a migration to Server 2019. Now I'm stuck.
from Hyper-V manager, connect to affected hyper-v host with server local administrator and password and see if you get console 1st and then connect to DC console from hyper-v manager to find out further
If everything fails, then reboot Hyper-V host and then check if you get further
If everything fails, then reboot Hyper-V host and then check if you get further
You can try export this vm, download it to some local test environment and check what is going on. I do not recommend to join host to domain in single DC environment - probably is better to change it. Login as a local administrator.
ASKER
Sincere thanks for your help so far. However, I am still struggling with this. I can log into the Hyper-V server - either as a domain admin with cached credentials or as a local admin as \Administrator. However, this just enables me to run cmd line and powershell. I can start and stop mt DC VM using powershell VM-Start e.g. but my problem is that although it 'starts' it doesn't fully boot up and never becomes available on the network. this is why I am trying to access Hyper-V Server remotely with Hyper-V Manager and this is where I'm stuck. I am trying to Connect to Server and attempting to Connect with Credentials that work for RDC, but I get 'This computer is not configured to allow delegation of user credentials. Do you want to enable delegation? Yes/No'. I have set up Group policy to enable delegation, I have tried adding registry entries, Replying YES to the above dialog box just loops and asks same question again - forever. replying NO gives another error dialog saying the WinRM client cannot process the request. A computer policy does not allow delegation of user credentials to the target computer. Sorry this is so long, but I still need help - unfortunately. Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks Alan for detailed explanation and better solution
Example:
Login: .\Administrator
Password: [administrator password]