It also works if the PVE host does not share any ip network with the guest and that is exactly the point why it does not make any sense to integrate other options there that are for everyone or rely on special circumstances and will result in more use cases or forum posts why the RDP button is not working. This ALWAYS works and therefore it is integrated in PVE. The console menu are settings that directly access the lxc console or the qemu virtual graphics card, without any guest feature requirements. I'll look at SPICE as well, but my gut tells me that Guacamole would be how I'd be doing this on my lab because it draws all of the remote technology types together so the one gateway covers RDP, SSH etc. Currently I have one host nested inside ESXi and one hardware host and don't see anything yet that could persuade me to go back. I'm in the throws of migrating my home lab with ESXi to PROXMOX and am loving virtually all of the functionality and features. The other option is to install windows RDP proxy features, which can give a tidy RDP experience but works best when fronting a Windows domain. Guacamole works very nicely, but incurs the overhead of another VM, or jumpbox. It could be coded into the VM Options tab and controlled with a binary switch to display the link or not. My interpretation of OP's question is more a web GUI tweak to recognise that the underlying VM is running Windows and to display an rdp://ip.address or rdp://vm.guest.FQDN that can be clicked to launch an RDP session with RDP config and options being handled by the actual target VM - as opposed to making the hypervisor also be an RDP gateway.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |