Hi,
We can't access vcenter directly (security policy), so we have to establish RDP connection to jump host and than connect to vcenter. But over RDP vmware guest console is unusable, it eats characters some characters are unavailable and so on.
Without vmware tools (clean install) it is totally unusable, after tools it work better but still bad. Is there any workaround or solution for given situation?
Thanks
Dubravko
Hello!
Are you using the Web Console or the VMRC (https://www.vmware.com/go/download-vmrc)? The pure Web Console is not really the best choice -> https://kb.vmware.com/kb/2071245
Robert
Already tried using vmrc, it is better but still not satisfied user. It is not problem only with keyboard it also effects mouse.
Dubravko
If the end user does not have direct remote access to his/her VM through native remote access technologies like RDP or SSH and are therefore forced to use a VM console, then there's really not a whole lot you can do about it if they're forced to do so through a RDP session. User experience can be improved over a PCoIP-based Horizon desktop in some cases, but you're still not going to get performance like you would when accessing VMRC natively.
Hi,
I am a freelance developer and I've many VMs in my homelab. I used to have access to VM Remote Console through VMWare Workstation since you don't need to configure anything on client side just connect to ESXi server, that's it. However, time to time weird keyboard problems occur in remote console. If you're Turkish user like me and frequently switch between US and TR keyboards then you may get into such trouble. That's why I switched to RDP.
However, if you're connecting to customer networks via VPN and VPN does not allow even LAN access then remote console is the only option.
I also experienced KVM (Proxmox in specific) and SPICE client. The user experience is much better imho. I wish ESXi supports RDP like VirtualBox does.
BR
Haldun