asked on

ESXi 4.1 host problems when using remote control on a guest Operating System

I have an ESXi 4.1 host with a Windows 2008 R2 Standard guest running Remote Desktop Services.

When using Remote Control to connect to a users session within the Windows Server guest, the CPU usage on the ESXi host goes through the roof. The ESXi host has needed to be rebooted whenever we have done this.

Can anyone help?

Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)

Could you give the experts some more details about the host?

cpu, memory, disk, how much memory in host and virtual machine?

what is the server?

IanTh

does it do the same when you remote from vclient

bootneck2222

ASKER

2 x Identical hosts in a cluster:
HP Proliant DL380 G6
2 x Intel Xeon X5560 @ 2.8GHz, 20GB RAM
ESXi 4.1.0, 260247

Guest Details:
VM Version 7
1 vCPU
20GB RAM
Windows 2008 R2 Standard
80GB Thick Provisioned Hard Disk

Datastore Details:
Openfiler SAN using iSCSI

bootneck2222

ASKER

Just to confirm, this happens when connecting to the server via an RDP session and selecting 'Remote Control' in the Remote Desktop Services Manager.

I haven't tried it from the vSphere Client console.

IanTh

but the link he is using viclient remote control not rdp

bootneck2222

ASKER

No, the issue arises when doing a Windows Remote Control of a users terminal session. This action is on the virtual Windows Server that is being hosted by VMware. The vSphere Client is not involved.

ASKER CERTIFIED SOLUTION

JRoyse

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial