![]() Yes, you can even do this with a VM that has no vNIC connection. This is accomplished regardless of network connections or network access – it’s through the features of the Hypervisor so all the admin requires is network connectivity to the host. This means that the Connect tool can use Remote Desktop connection through the VMBus (via the integration components) and into Remote Desktop Services running in the Windows VM. Remote Desktop access to VMs has been embedded into Hyper-V. What if you are just using Windows 8.1 Client Hyper-V and don’t want to bother with Remote Desktop at all? a multitenant cloud with Hyper-V Network Virtualization. But what if you don’t have Remote Desktop access to the VM, e.g. The best solution was to RDP into the VM. Not only that, but the UI is a little sluggish. Instead you have to use the paste text option via a menu in the Connect window.Now open the Connect window, hit CTRL + V and nothing happens.You copy the key into the buffer of your PC.You browse on MSDN/TechNet to get your key. It comes to the time to enter the product key. ![]() You are building a new VM by hand in a lab.The problem that is being solved is the pain of managing VMs via “KVM”, that is, using the Connect window in Hyper-V Manager. This has come with the addition of Remote Desktop over VMBus. Microsoft has continued to “round the corners” of Hyper-V administration, making it easier to use and operate your services on their enterprise hypervisor. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |