Keyboard issue in using console from vSphere Client

[rwolter]

While using a console on a virtual machine using the vSphere Client, I can't use my keyboard on my PC anymore. Everytime I try using my keyboard, it switches back in the console session. The vmware tools are installed in the vm. Can anybody fix this prob.

thx,

Ralf

[AndreTheGiant]

Which kind of VM?

A Linux box?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[rwolter]

Hi Andre,

its a virtuall machine running Windows XP SP3 on a vSphere4 Server.

[kenner]

I saw this too, on one specific XP Pro machine. I thought it was something wierd with that particular machine. I'm glad to see that somebody else is seeing it.

[rwolter]

Hi kenner,

in my case it´s a Windows XP SP3 guest too.

[AndreTheGiant]

The vmware tools are installed in the vm.

Are also up to date?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[rwolter]

VMWaretools are installed and up to date, too

[rbos3]

Hi there,

Maybe a stupid question but are you sure your mouse pointer is outside the console window? When using the VMware Tools you don't need to use CTRL+Alt as you know so maybe your pointer is still inside the console view.

Hope this helps!

[rwolter]

Hi rbos3,

yes, the mousepointer is outside. the switching back in the console occurs also when the console is minimized and trying to work in other applications.

[fedkad]

I have the same problem. The only way to free the keyboad is to press CtrlAltDel, but since this is also captured by the Console it restarts the virtual machine also.

Are we the only ones having this problem????

[rwolter]

Hi fedkad,

since there are that few answers, it may be our fault. So, i switched back to ESX 3.5 and got no probs. I´ll wait for the fixes from VMWare. I hope, that will last not that long. The support from VMWare didn´t answer yet,also.

[kenner]

since there are that few answers, it may be our fault.

I have it too, but only from one machine and not the second. The

configuration of both are identical. There's definitely something wrong.

[rtkirton]

I have this same issue as well. I have not tested it on any other system, but on my laptop here at the office, when I attempt to type anything when a console session is up, it will switch focus to the console session. The only way to get out is either CTRL-ALT-DEL (and that doesn't really help because once you apply focus to the console window, the problem occurs again) or you shut down the console window.

This also happens when you have two or more console windows open. The last console window that was opened will grab the focus from the other console windows.

This behavior is very irritating. I'm going to try reinstalling the vSphere client and see if that fixes the issue. The one I installed was from VMWare's website. I'm going to try the one from ESXi 4.0 system.

[rtkirton]

Okay...it doesn't matter if the VMWare tools are installed or not, same behavior. It's doing it for both Linux and Windows. The moment you click on an object in the console window, the keyboard is locked to that screen. Any attempt to type anywhere else automatically brings the focus back to the console window. The only way to get control of the keyboard is to close the console window. I uninstalled all components of VMware on my machine and installed a fresh copy of vSphere Client...same problem.

Any suggestions would certainly be appreciated.

[rtkirton]

A friend and collegue of mine installed vSphere at home...ended up with the same problem as I did where the keyboard would not release from a console session. He thinks he may have figured out the problem.

He says the process known as sfcbd (which he says is a hardware monitoring process) appears to be the culprit. When he shut down that process, the console started behaving normally. He also mentioned that he was reading this issue also happened in version 3 and that version was patched to fix this.

Someone may want to try that and see if they are able to duplicate the results. I got fed up over that and the system losing VMs that I reverted back to version 3.

[mbell98]

I've been having the same problem on one of my XP machines (a laptop) but do not have the problem on another XP machine. I could not find that process "sfcpd" on either the workstation or server. Where does it normally run?

I never had this problem with 3.5. Pressing CTRL-ALT-DEL does get the client to release the keyboard but has the unwanted affect of sending that key sequence to both the VM and client PC.

[Kryten67]

I spoke with VMWare tech support who guided me through the process of disabling sfcbd -- which was a lot more difficult than simply killing the processes (they would simply respawn). Doing this had no impact on the problem. I installed the vSphere client on my machine running Win2003 Server and use RDP to connect to it, and then run the vSphere client from there.

VMWare refused to investigate the problem (SR# 1450563985 if anyone is interested) further because the only machine exhibiting the problem is running Win7 and that is not supported currently.

[nourish]

Same issue on Windows XP SP3, vSphere Client 4.0.0. Downloaded the latest build (208111), reinstalled the client - exactly the same behaviour. Whenever I leave the Console tab open and switch to another window, keyboard input keeps getting into the virtual machine console in the vSphere Client window. I figured out there are only two things I can do:

• Switch to a turned-off virtual machine before switching to another window

• Press Ctrl-Alt-Del and then Escape to regain the control of the keyboard

Both are crazy things to do being forced to do them a hundred times a day.

What can be done about that?

[bramvermeulen]

I opened a case with vmware and got this response:

Hello Bram, We opened a bug for this case, we were able to reproduce the problem on house, I add your case to the bug and we will move the case to pending state, we will let you know in what patch this problem will be fix

[nourish]

Thanks. I do hope they'll fix this soon, otherwise purchasing vSphere isn't fun for me.

[ElBarbaro]

To retrieve control of the mouse and keyboard press Ctr-Alt

(not Ctr-Alt-Del, just Ctr-Alt)

[kenner]

To retrieve control of the mouse and keyboard press Ctr-Alt

(not Ctr-Alt-Del, just Ctr-Alt)

This thread is about cases where that doesn't work and where focus comes

back to that window after typing anything.

[jonhartwell]

I'm having the same issue here...

After opening a server console session, keyboard and mouwse work

fine within the console window. However; when I leave the console

window (either the usual way facilitated by VM tools or Ctrl/Alt) the

mouse will be usable outside of the console, but ALL keyboard access is

still directed to the VM console .

Until this gets resolved, our organization can't move to ESX4 which I would badly like to do.

Any help please????

[thingy]

I too have come across this issue.

It seems to be affecting only one PC and so it looks like a configuration problem.

Is there any documentation on cleaning up after uninstalling vSphere client on a machine?

[AndreTheGiant]

Is there any documentation on cleaning up after uninstalling vSphere client on a machine?

I think no.

You can simply remove folder and registry keys (if still present).

Andre

[Kryten67]

I am experiencing the same issue.

I suspect that it might be because I am running Win7.

The latest vmware-tools are installed on all guests. Only way to rescue keyboard focus is to close all consoles or hit ctrl-alt-delete.

[bramvermeulen]

One of my co-workers has the same problem with Windows XP SP3 using vSphere Client. Still nobody that knows how to fix this?

Tia

Bram

[skotagiri]

I have WinXP and have same problem on my company Laptop using VSphere 4.0 and ESXi 4.0 (both WInXP Guest and SLES 10 Linux Guest). Opening console disabled my keyboard only to work in Console and not on application on laptop. I have to close console to get back control.

I have same implementation at home and have no problems using my PC WinXP VSphere 4.0 clieny with ESXi 4.0. Not sure what is causing the issue/problem?

[admin]

Hi guys,

Sorry to hear you are running into this. There seem to be a few similar manifestations of keyboard grab issues going around - so could all of you running into the problem please answer a few quick questions to help us narrow this down a bit? There is also a potential work-around to try.

Note that for all of these questions, I'm talking about the client machine running vSphere Client (formerly VI Client).

1) Do you by chance remember what exactly happened to trigger the manifestation of this issue? We need as much detail as you can remember, especially including:

- installations/un-installations of any VMware products on the client machine running vSphere Client

- upgrades of any VMware products on the client machine running vSphere Client

- any preference changes in any VMware product, whether via UI or via manual edit of preference files

- anything else that may have stood out around the time you started seeing the issue

2) Do you currently have the "pref.grabOnKeyPress" preference set in your preferences file? (Check for "preferences.ini" under %USERPROFILE%\Application Data\VMware and under %ALLUSERSPROFILE%\Application Data\VMware)

3) Do you have VMware Workstation or any other VMware product currently co-installed with vSphere Client on the client machine?

4) Did you have VMware Workstation or any other VMware product ever installed on said machine before?

5) Do you by any chance happen to have an old preferences file backup prior to whatever action triggered the manifestation of this issue? If so, could you please check for "pref.grabOnKeyPress" in it? Alternatively, if you used a product such as Workstation, do you remember what your grab preferences were in it - or, if you are familiar with preferences, do you by chance know whether you had pref.grabOnKeyPress set before?

Sorry for so many questions - we are trying to track down at least one potential culprit here

Finally, and most importantly, could you try this work-around?:

- Go find your preferences file (see above).

- In there, make sure that pref.grabOnKeyPress appears exactly once, and that it's set to FALSE, like so:

pref.grabOnKeyPress = "FALSE"

- Does that help?

Thanks!

[fedkad]

+1) Do you by chance remember what exactly happened to trigger the manifestation of this issue? +

Just installed vSphere client product.

2) Do you currently have the "pref.grabOnKeyPress" preference set in your preferences file?

It was "TRUE".

3) Do you have VMware Workstation or any other VMware product currently co-installed with vSphere Client on the client machine?

Yes. VMWare Server Console 1.0.7 was already installed.

4) Did you have VMware Workstation or any other VMware product ever installed on said machine before?

AFA I remember, only VMWare Server Console.

+5) Do you by any chance happen to have an old preferences file backup prior to whatever action triggered the manifestation of this issue? +

I don't think so.

Could you try this work-around?

I tried. And it seems to help! :smileyhappy:

Thank you.

[Bitelxux]

Same issue.

vsphere client 4.0.0 build 208111 running on parallels 4.0.6630 Rev 449744

Console doesnt release focus.

Working workaround:

On focused console, press ctrlaltintro twice. This releases focus.

[scuthber]

Changing pref.grabOnKeyPress = "FALSE" worked for me too. File was in %userprofile%\AppData\Roaming\VMware

Running Vista SP2. Did have old VI client installed and also I have VMware workstation 6.0.4 build 93057 installed

[hsingtsu]

The workaround in creating preferences.ini does nothing. I am not sure what "intro" key is in "ctrlaltintro". But, "ctrl-alt-esc" does it for me.

vsphere client 4.0 build 208111 on windows 7 enterprise x64 guest on parallel desktop 5 for Mac Build 5.0.9344.

[Kryten67]

YAY! The "workaround" fixes the problem!!

[skotagiri]

pref.grabOnKeyPress = "TRUE"

TO

pref.grabOnKeyPress = "FALSE"

FIXED My problem too.

Thanks :smileyhappy:

[admin]

Glad to hear it helped you guys!

Any chance you could answer those questions as well though? :smileyhappy:

It would give us a better idea of setups people who are getting to this state have - and help us narrow down what's causing it.

[Kryten67]

1) Do you by chance remember what exactly happened to trigger the manifestation of this issue?

No. Had problem immediately with vSphere client install.

2) Do you currently have the "pref.grabOnKeyPress" preference set in your preferences file?

It was "TRUE".

3) Do you have VMware Workstation or any other VMware product currently co-installed with vSphere Client on the client machine?

Yes. VMWare Server Console 1.0.4 build-56528 is installed.

4) Did you have VMware Workstation or any other VMware product ever installed on said machine before?

Yes. Also have VMWare Console - 3.2.0 build-14497

5) Do you by any chance happen to have an old preferences file backup prior to whatever action triggered the manifestation of this issue?

Not sure -- where would I find this?

I

[skotagiri]

I did have Vmware 2.0 setup earlier and deinstalled it only after installing VSphere 4.0 Client. I did not have any issues inatalling VSphere Client.

Not sure if that had any thing to do with this keyboard locking issues.

[nourish]

1) Do you by chance remember what exactly happened to trigger the manifestation of this issue? We need as much detail as you can remember, especially including:

installations/un-installations of any VMware products on the client machine running vSphere Client

upgrades of any VMware products on the client machine running vSphere Client

any preference changes in any VMware product, whether via UI or via manual edit of preference files

anything else that may have stood out around the time you started seeing the issue

I think the issue had been in there from the very beginning.

2) Do you currently have the "pref.grabOnKeyPress" preference set in your preferences file? (Check for "preferences.ini" under %USERPROFILE%\Application Data\VMware and under %ALLUSERSPROFILE%\Application Data\VMware)

Yes, in my profile, =TRUE.

3) Do you have VMware Workstation or any other VMware product currently co-installed with vSphere Client on the client machine?

Yes.

4) Did you have VMware Workstation or any other VMware product ever installed on said machine before?

VMware Workstation had been installed prior to the installation of vSphere Client.

5) Do you by any chance happen to have an old preferences file backup prior to whatever action triggered the manifestation of this issue? If so, could you please check for "pref.grabOnKeyPress" in it? Alternatively, if you used a product such as Workstation, do you remember what your grab preferences were in it - or, if you are familiar with preferences, do you by chance know whether you had pref.grabOnKeyPress set before?

No, it's the first time I had to dig into the preferences.

Go find your preferences file (see above).

In there, make sure that pref.grabOnKeyPress appears exactly once, and that it's set to FALSE, like so:

pref.grabOnKeyPress = "FALSE"

Does that help?

Yes, it does. Thank you.

[bramvermeulen]

1. On the system where the problem happened there was nothing that triggered it, the moment vSphere Client was installed the problem was already present.

2. The "pref.grabOnKeyPress" preference did not exist.

3. There were no other VMware products installed.

4. As far as I know there was no VMware Workstation installed on the machine before, just the VMware Remote Console for lower ESX versions.

5. There was no old preferences file since it happened from the start.

6. The work-around worked! My co-worker added the preference and since then the problem was gone. :smileyhappy:

tyvm!

[Perceptum]

1) Do you by chance remember what exactly happened to trigger the manifestation of this issue? We need as much detail as you can remember, especially including:

• Patched ESXi installable 4.0 to build 208167

• Update vSphere client to build 208111

2) Do you currently have the "pref.grabOnKeyPress" preference set in your preferences file? (Check for "preferences.ini" under %USERPROFILE%\Application Data\VMware and under %ALLUSERSPROFILE%\Application Data\VMware)

• I Currently have the "pref.grabOnKeyPress" and it was set to "TRUE"

3) Do you have VMware Workstation or any other VMware product currently co-installed with vSphere Client on the client machine?

• No

4) Did you have VMware Workstation or any other VMware product ever installed on said machine before?

• Yes, I had VMware Workstation installed, but I removed it

5) Do you by any chance happen to have an old preferences file backup prior to whatever action triggered the manifestation of this issue? If so, could you please check for "pref.grabOnKeyPress" in it? Alternatively, if you used a product such as Workstation, do you remember what your grab preferences were in it - or, if you are familiar with preferences, do you by chance know whether you had pref.grabOnKeyPress set before?

• Sorry, but I do not

Sorry for so many questions - we are trying to track down at least one potential culprit here

• How else will you effeciently find the problem?

Finally, and most importantly, could you try this work-around?:

• The work around worked like a charm, and there was only on instance of the preference.

[bramvermeulen]

Ik ben afwezig tot maandag 07/12. Voor dringende problemen kan u steeds de helpdesk informatica contacteren op het nummer 050 452269 of via [e-mail]<mailto:[e-mail]>.