- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe to Topic
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Unable to connect or remotely access Hyper-V guest VM.
Working with a windows 2016 vm which is a domain controller that for a while has not allowed console logins via Hyper-V nor remote logins.
Using Hyper-V Connect gui shows the locked login screen and clicking on ctrl-alt-delete button flashes the screen but the login prompt does not show. Remotely accessing via RDP, you get prompt for credentials and after entering creds it looks to log you on but then cononection closes out before you actually successfully are logged in.
The VM is a node on a failover cluster with virtual machine version 9. At the inception the vm was part of an older standalone hyper-v host. You can ping it and it appears to be operating normally as one of several on premise domain controllers. Also we have access to it via powershell direct from the hyper-v host. Looking at the event logs does now show anything obvious.
Has anyone seen this behavior and have a solution to resolve logins via the GUI?
Thanks,
Bob
- Labels:
-
Server Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Just to add to this recommended solution: You must run Hyper-V Manager using an account that is in the Administrators group or Hyper-V Administrators group on the HyperV Server. Otherwise, you will NEVER be able to connect to the Hyper-V host. If your management workstation’s administrator account does not have those capabilities, hold down [Shift] while right-clicking the Hyper-V Manager shortcut, and then choose Run as a different user.
Regards,
Rachel Gomez
- Mark as New
- Bookmark
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
The cleanest / simplest / quickest solution is to turn it off, seize roles (if necessary)
then do metada cleanup
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
and stand up a new one for replacement.
