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.
Alan BatemanDirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Coolie SheppardSystems EngineerCommented:
RDP into the host and when it asks for a authentication, use the .\Administrator account for the login for local access.  

Example:

Login: .\Administrator
Password: [administrator password]
MaheshArchitectCommented:
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
Olgierd UngehojerSenior Network AdministratorCommented:
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.
Rowby Goren Makes an Impact on Screen and Online

Learn about longtime user Rowby Goren and his great contributions to the site. We explore his method for posing questions that are likely to yield a solution, and take a look at how his career transformed from a Hollywood writer to a website entrepreneur.

Alan BatemanDirectorAuthor Commented:
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
Alan BatemanDirectorAuthor Commented:
Ok. After going up many blind alleys and suffering several false starts I have finally fixed this.  In the end I was able to connect to my Hyper-V server with Windows Admin Center (which I'd never used before). This enabled me to reconfigure the VM to ensure that it was booting from the correct volume (That was the first problem - I'd added a new virtual disk and it seemed to have taken priority in the boot order!) .  I also had to adjust the VM's  startup memory because the 'real' machine doesn't really have enough and the VM was failing with a memory problem. Once I'd fixed these problems my VM  booted correctly and finally I had a DC again and things looked a lot better. Once the Hyper-V server could see its DNS server again, the Hyper-V manager problem started to work again. So, if you can't use Hyper-V manager, try Windows Admin Center, it can be a lifesaver.
Thanks to all who provided help and advice.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MaheshArchitectCommented:
Thanks Alan for detailed explanation and better solution
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Powershell

From novice to tech pro — start learning today.