Hyper V remote desktop connection

  • It seems to me that on the normal workstation you are connected to the host that is doing the RDP.

    When you are connecting to the Hyper-V it sounds to me like someone is RDP'd into the Hyper-V and you are trying to "LogMeIn" to the server itself.

    RDP is not VNC where it will show what is going on on the local screen, it actually creates its own session. Thus when you try to login to the same user [or different user depending on if it is actually a server/Multiuser OS] it kicks the user connected to RDP

  • Nubirdz wrote:

    It seems to me that on the normal workstation you are connected to the host that is doing the RDP.

    When you are connecting to the Hyper-V it sounds to me like someone is RDP'd into the Hyper-V and you are trying to "LogMeIn" to the server itself.

    RDP is not VNC where it will show what is going on on the local screen, it actually creates its own session. Thus when you try to login to the same user [or different user depending on if it is actually a server/Multiuser OS] it kicks the user connected to RDP

    No, the client is using RDP at their home to connect to their workstation at work, which is a virtual Hyper-V windows computer. 

    We are trying to assist them by us, the admin, using LogMeIn to see the virtual Hyper-V machine. 

    Does this help?

  • So they're logging into a VM, or are you trying to interact with Hyper-V manager?

    I really hope your client is on a VPN and RDP isn't exposed to the internet, but that's another discussion.

    How are they launching the LMI connection? on the host[aka client's desktop] or the VM they're trying to connect you to?

  • dancrane wrote:

    So they're logging into a VM, or are you trying to interact with Hyper-V manager?

    I really hope your client is on a VPN and RDP isn't exposed to the internet, but that's another discussion.

    How are they launching the LMI connection? on the host[aka client's desktop] or the VM they're trying to connect you to?


    LogMeIn is already installed through an MSI on the VM, which is what were trying to connect to using LogMeIn. 

    The client is logging into a Hyper-V VM using RDP.

    We're trying to assist them by US logging into LogMeIn while they're logged in with RDP.

  • You won't be able to screen share that way. The LMI session is going to require you to log in, and if they RDP it will lock the OS or open a different session if it's a server OS.

    In this case you'll want to be remoted into their desktop, or have them join your LMI session with other screen-sharing software.

  • dancrane wrote:

    You won't be able to screen share that way. The LMI session is going to require you to log in, and if they RDP it will lock the OS or open a different session if it's a server OS.

    In this case you'll want to be remoted into their desktop, or have them join your LMI session with other screen-sharing software.

    No it's not a server OS; but for some reason you're wrong by saying you can't RDP and use LMI at the same time. 

    Myself and another tech have shared sessions by using RDP to log into a server and LogMeIn before in order to figure out a server side issue. 

    I was curious if maybe this workstation because it's a Hyper-V VM if there was a restriction of any sort through Hyper-V? Possibly a setting?


  • Guys, I was able to figure it out. In LogMeIn on the session toolbar at the top, all the way to the left, you can select "Terminal Server" while at the workstations lock screen, and you can switch it to the correct computer/user without being kicked out. 

    Thanks for the help

The Hyper-V page allows you to setup your connection as a Hyper-V host to display the Hyper-V management in the Dashboard and optionally allows you to configure a target instance you want to connect to by default.

Hyper-V Mode

Specifies whether or not the remote host is a Hyper-V mode host.

This is a standard RDP connection [Default]
The Sessions dashboard pane is shown in the Dashboard panel but not the Hyper-V dashboard pane.

This is a Hyper-V host, show VM instances in dashboard
The Sessions dashboard pane and the Hyper-V dashboard pane is shown in the Dashboard panel.
 

TIP

Use the Connect [Ad Hoc] button in the Hyper-V dashboard pane toolbar to connect directly to the console of a selected instance. There's no need to have any Hyper-V tools or vmconnect.exe as Royal TS seamlessly integrates Hyper-V remote control.

This is a Hyper-V host, connect to a specific instance
The Hyper-V dashboard pane is shown in the Dashboard panel for the configured instance.

Port

The Hyper-V proxy port. By default, Hyper-V hosts listen to port 2179.

Instance

Enter an instance ID [GUID] or click on the browse button [...] on the right to show the Hyper-V instance picker.

NOTE

Instance browsing relies on WMI. Ensure that all the necessary firewall ports for WMI are open and that the user account running Royal TS [beware of UAC] or the credentials set in the Remote Desktop connection have local administrative rights on the remote Hyper-V host computer.

Enhanced Session Mode

Local resources, like audio, printers, clipboard, drives, USB devices, etc. can be redirected.

WARNING

Enhanced session mode requires a supported guest operating system, and may require additional configuration inside the virtual machine. Royal TS may not be able to establish a connection when this setting is enabled for an unsupported server or guest operating system.

For more information, visit: //technet.microsoft.com/en-us/library/dn282274.aspx

  1. I have a Hyper-V VM created with a Windows OS running in it. Is there a way I can connect to the VM via Remote Desktop from a computer other than the host computer? Thanks!

    John

  2. So I started to figure out how to get remote access. Now I get this error:

    I can remote desktop into the host computer just fine.

  3. Remote desktop connection to virtual machines works exactly the same way than connection to physical machines. In screenshot, I am remoting to a Hyper-V VM on another computer just now:

    Notice that if VM is using Default Switch for network connection [virtual NIC], it puts the VM behind NAT and remote desktop connection does not work. To remote to a VM, it must use a user created External Switch for networking.

    Kari


  4. Thank you! I would also like very much to remotely connect to the Hyper-V manager itself, though. I think I can now iron out connecting to the VM session itself.


  5. I would also like very much to remotely connect to the Hyper-V manager itself, though.

    You have two options:

    1.] Remote connect to another PC and open its Hyper-V Manager in remote session

    -- OR --

    2.] Add the second PC to your Hyper-V Manager. Right click Hyper-V Manager on left pane, select Connect to Server, enter remote computer's NetBIOS name or IP:

    Notice that some prerequisites must be done on both machines before you can add another Hyper-V host. See this tutorial, its Part One, the prerequisites are the same: Windows Admin Center - Centrally manage all your Windows 10 PCs | Tutorials

    Kari


  6. I'll look at that, thank you!

  7. Hi there another follow on question to this Can a remote Windows 10 HOME connect directly to HYPER-V as per option 2 or do you have to do it only via option 1- I know you have to have PRO to run HYPER-V but can you access the HYPER-V console from a remote W10 HOME laptop. BTW for Linux users if you install something like FREERDP then option 1 works from Linux as well to access windows via RDP.

    Cheers

    jimbo

    Last edited by jimbo45; 03 Apr 2019 at 04:41.


  8. Can a remote Windows 10 HOME connect directly to HYPER-V as per option 2 or do you have to do it only via option 1?

    I have never even installed Windows 10 HOME, so I have never tested it. Logically thinking, because as far as I know, HOME does not have Hyper-V Manager, Option 2 is not available in HOME. But, as I said, I do not know HOME edition and can't be sure about this.

    Kari

  9. Hi there

    Thanks again @Kari

    I don't have HOME either but a work colleague was interested. I tested the Linux link so even from a Linux VM you can access Windows remotely via an "RDP" equivalent -- ignore certificate errors and it works just fine Actually it's better than using Windows -->Windows RDP since you - assuming decent CPU 's -- can minimize the data traffic over the network via compress type options in the xfreerdp command. I think standard Windows to Windows RDP just sends the whole screen again every time rather than the changed bits. I added a screenshot to my post above -- just the minimal command line with default options. You can of course set Window resolution etc etc. Cheers

    jimbo


  10. I can get Windows Admin Center to work just fine. All of that functions properly including remote management of the VM. But I still can't add the remote computer to Hyper-V Manager on the client computer. I'm still getting the error in post #2. So it seems like it is a configure problem with Hyper-V Manager on my client computer. If it was the remote computer, I would think that Windows Admin Center would be having problems too.

Video liên quan

Chủ Đề