Does this problem sound familiar to someone?
When I work on a W2k3 client using remote console, suddenly the client hangs. The console just freezes the display. There is no more disk or network activity on the client, but the VMware process on the host now uses 10% of our cpu time. When I use vmware-cmd, the client responses on getstate, getheartbeat.
The only thing to solve this is to kill the vmware client process on the host.
I am trying out if the same happens when I am using windows remote desktop. Somehow I think it is the remote console causing it.
Please respond!
Message was edited by: Hazzebas
I now have experienced the problem using remote desktop, so it's not the console. And only with VM's with Buslogic SCSI adapters.