Losing mouse via hyper v manager
-
When connecting to vms through hyper v manager, mouse buttons stop working occasionally. If I rdp, it works fine through there. Have to restart vm to get mouse clicks back via hyper v manager. Happen to anyone else? Any fix?
hyper v server 2016, vms are 2008 r2 ( I know, I know)
-
Generally speaking, you should almost never use the console of the VM to gain access. Using RDP is the better option for security and compliance.
-
As for why the cursor disappears, in my experience this has generally been an issue of a lack of video ram applied to the VM.
-
@DustinB3403 said in Losing mouse via hyper v manager:
Generally speaking, you should almost never use the console of the VM to gain access. Using RDP is the better option for security and compliance.
What is that based on? I've never heard that before.
-
@Dashrender said in Losing mouse via hyper v manager:
@DustinB3403 said in Losing mouse via hyper v manager:
Generally speaking, you should almost never use the console of the VM to gain access. Using RDP is the better option for security and compliance.
What is that based on? I've never heard that before.
The same general security practice that you should never use the local console if you have other, more secure options to login to the machine.
RDP is preferred over the console.
The console should only be used, if the other options are not working.
-
@DustinB3403 said in Losing mouse via hyper v manager:
As for why the cursor disappears, in my experience this has generally been an issue of a lack of video ram applied to the VM.
The cursor does not disappear in my case. I can move the mouse around, hovering over items highlights them even. It's just the click doesn't register.
-
@DustinB3403 said in Losing mouse via hyper v manager:
@Dashrender said in Losing mouse via hyper v manager:
@DustinB3403 said in Losing mouse via hyper v manager:
Generally speaking, you should almost never use the console of the VM to gain access. Using RDP is the better option for security and compliance.
What is that based on? I've never heard that before.
The same general security practice that you should never use the local console if you have other, more secure options to login to the machine.
RDP is preferred over the console.
The console should only be used, if the other options are not working.
I don't get it - the console is as secure as you can get - at least in person. of a course a remote console is only as secure as the protocol in use.
What makes you think that MS would be using a less secure protocol for console access than for RDP?
-
@DustinB3403 said in Losing mouse via hyper v manager:
@Dashrender said in Losing mouse via hyper v manager:
@DustinB3403 said in Losing mouse via hyper v manager:
Generally speaking, you should almost never use the console of the VM to gain access. Using RDP is the better option for security and compliance.
What is that based on? I've never heard that before.
The same general security practice that you should never use the local console if you have other, more secure options to login to the machine.
RDP is preferred over the console.
The console should only be used, if the other options are not working.
Enhanced console access in Hyper-V is via RDP.
-
@Obsolesce said in Losing mouse via hyper v manager:
@DustinB3403 said in Losing mouse via hyper v manager:
@Dashrender said in Losing mouse via hyper v manager:
@DustinB3403 said in Losing mouse via hyper v manager:
Generally speaking, you should almost never use the console of the VM to gain access. Using RDP is the better option for security and compliance.
What is that based on? I've never heard that before.
The same general security practice that you should never use the local console if you have other, more secure options to login to the machine.
RDP is preferred over the console.
The console should only be used, if the other options are not working.
Enhanced console access in Hyper-V is via RDP.
I kinda fully expected that to be the case - why would MS use yet another protocol for the console versus whatever you want to call typical RDP access.
-
Anyone can login to the console, as the local admin, and have no additional logging (admin login to console from system-name. . .) for example.
So, there are compliance and logging reasons to not use the console that are general recommendations to "just do".
-
@Obsolesce said in Losing mouse via hyper v manager:
@DustinB3403 said in Losing mouse via hyper v manager:
@Dashrender said in Losing mouse via hyper v manager:
@DustinB3403 said in Losing mouse via hyper v manager:
Generally speaking, you should almost never use the console of the VM to gain access. Using RDP is the better option for security and compliance.
What is that based on? I've never heard that before.
The same general security practice that you should never use the local console if you have other, more secure options to login to the machine.
RDP is preferred over the console.
The console should only be used, if the other options are not working.
Enhanced console access in Hyper-V is via RDP.
Doesn't this have to be enabled though? While a good practice to do, doesn't mean its on.
-
@DustinB3403 said in Losing mouse via hyper v manager:
Anyone can login to the console, as the local admin, and have no additional logging (admin login to console from system-name. . .) for example.
So, there are compliance and logging reasons to not use the console that are general recommendations to "just do".
Anyone can log in with any remote tool with valid credentials also.
Remote or local is no damned different.
-
@DustinB3403 said in Losing mouse via hyper v manager:
Anyone can login to the console, as the local admin, and have no additional logging (admin login to console from system-name. . .) for example.
So, there are compliance and logging reasons to not use the console that are general recommendations to "just do".
What? Who has the administrator account password? Hopefully only the most trusted of all people, a subset of the IT team. So that shouldn't be a real issue.
As for logging - I have no idea what logging in available in Hyper-V itself when the Hyper-V Manager is logged into and accesses a Hyper-V host - but I would assume that connection itself is logged based upon the username/password of that IT member - and if they have the Administrator name/password - well, there you go.
As for the actual console - well, there really isn't a way to access a VM from the physical console on the server, so that's a non issue.
