• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 628
  • Last Modified:

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?
0
bootneck2222
Asked:
bootneck2222
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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?
0
 
IanThCommented:
does it do the same when you remote from vclient
0
 
bootneck2222Author Commented:
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
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
bootneck2222Author Commented:
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.
0
 
IanThCommented:
but the link he is using viclient remote control not rdp
0
 
bootneck2222Author Commented:
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.
0
 
JRoyseCommented:
There are compatibility matrixes on the guest OS and vsphere versions.  There is a ESXi 4.1 update 1 - please try to update esxi4.1 and then if you can reproduce check the host compaitibility .

Also - you may want to post on Vmware's community page since you probably don't have commercial support.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now