Solved

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

Posted on 2011-03-10
7
617 Views
Last Modified: 2012-05-11
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
Comment
Question by:bootneck2222
7 Comments
 
LVL 119
ID: 35094319
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
 
LVL 30

Expert Comment

by:IanTh
ID: 35094707
does it do the same when you remote from vclient
0
 

Author Comment

by:bootneck2222
ID: 35096090
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
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 

Author Comment

by:bootneck2222
ID: 35096146
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
 
LVL 30

Expert Comment

by:IanTh
ID: 35096217
but the link he is using viclient remote control not rdp
0
 

Author Comment

by:bootneck2222
ID: 35096400
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
 
LVL 6

Accepted Solution

by:
JRoyse earned 50 total points
ID: 35111259
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

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
virtualization 6 88
VMWare esxi 5.1 to 6.0 upgrade 15 115
Veeam Synthetic Full Backup 6 71
Powercli + List all VM's Per SCSILUN 15 50
When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

803 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question