Currently experiencing a problem using the vSphere Client console (and Workstation 10 console) to access one particular VM running on ESXi 5.5.0 hypervisor. When clicking within the console, keyboard and mouse input is captured but no action is taken. i.e., after clicking within the console window, the mouse cursor disappears, and if the focus is in an input field, no characters are received when typing with the keyboard. Because this is the initial startup screen it is the Windows logon. Problem only affects one VM, all others work fine and the problem VM can be accessed without issues using Windows RDC.
VM was originally created from a Paragon HDM 14 backup of a Windows 7 Ultimate 64-bit machine using Paragon HDM 14 to create a vmx-9 VM. Opened this using VMware Workstation 10 and had no issues using the console to access the VM. Had to deal with a few hardware problems as original physical machine used fingerprint logon but after sorting these issues out, access via VMware Workstation 10 was smooth.
vCenter Converter Standalone Client was then used to upload to an ESXi instance. Originally showed that VMware tools was not installed although the Workstation 10 version of tools was installed. After starting the VM, ESXi conceded that tools were installed and current. On this initial install was not able to interact with the console but could logon using RDC. Used vSphere Client to reinstall VMware tools and discovered two versions of VMware Tools were installed; 9.6.x from Workstation 10 and 9.4.x from vSphere Client 5.5
Uninstalled both versions of VMware tools and restarted. Still cannot interact with console. Installed only the vSphere Client version (9.4.x), restarted and still no luck.
Using VMware Workstation 10 to access the VM running on ESXi still doesn't allow interaction with the console although when the VM was running on VMware Workstation 10 console interaction was fine.
Have similar issues been noticed before?
Any pointers on how to resolve as there are no obvious error messages. That said I am not that familiar with debugging issues like this and may not be looking in the right places.