I am currently a View 4.6 shop serving up Win7 SP1 desktops. Occassionally, I have a user or two complain about a loss of the mouse within their VDI session. The mouse still works locally and on the VDI toolbar. The more savvy users can use the tab key within VDI to access there desktop icons. A disconnect or a reboot of their VDI VM resolves the issue.
Has any one in the community seen this particular behavior??? If so, what is the remedy?
Thanks in advance...
My users run in to the same issue. Even users on zero clients after unlocking windows will have no mouse. for the zero client users, doing a ctrl-alt-del then escaping brings the mouse back. on the view client that doesnt seem to work. I even ran into this issue on my VM while using the view client last night. I ended up just logging off windows in the view session and back on to finally fix it.
I'm hoping view 5 fixes this issue... will know in a week or two after I upgrade
Not heard about that before, do you have any unsusual USB-devices or keyboards attatched?
Please create an Service Request so we can fix it if it is a bug.
// Linjo
No USB devices attached during the time of the issue. KB is actually PS2 attached...
no wierd usb devices attached to the wyse p20's. just a standard slimlin dell keyboard and dell mouse.
same when it happens w/ view client, i notice it seems to happen on both my laptop and desktop. no usb devices attached to laptop when it happens there.
Hi!
I'm having the same issue. Vmware Ticket: 11096939509
Server: HP Proliant BL 460 G7
Vmware: ESXi 4.1 Update 1, View 4.6
Client: HP T5745 with HP ThinPro
vDesktop: Windows 7 SP1 32bit
Please, let me know if anyone have fixed it!
Att,
Guilherme
Having the same issue.
My users are frustrated with this, and I can undertand them.
Vmware: ESX 4.1 Update 1, View 4.6
Client: Wyse P20 or Wyse V90LE
vDesktop: Windows 7 SP1 32bit
Please work on this, we are deploying a lot of desktops in the comming weeks and it would be nice to have that bug removed..
Regards
Francois
Same issue, variety of clients including the Vmware View Windows Client, Wyse P20, iGel UD3 / UDC.
View 5 / vSphere 5. Also experienced this on View 4.5 and 4.6.
Hope it help you!
Guilherme
That is really great news!! Thanks a lot for these infos... Since we are not planning to migrate to View 5 before a month or two, do you think we could upgrade the view agents inside our Windows 7 VM's to v5 but still continue to use View 4.6 for connection server?
Regards
Francois
Best Regards
Guilherme
Still having this problem. Here is what I tried:
1-I tried switching back to SVGA II driver and that was terrible. I have many freezes and applications that would bot start using this driver, so I do not recommend you use this option.
2-I tried installing the View 5.0 agent inside my Windows 7 VM's and it worked great, but found that I could not linked clone VM's that had the 5.o agent, so I had to go back to the 4.6 agent.
3-I tried using the Mouse trail option, but my users cant stand the graphic effect it makes (and I acan understan them)
4-Tried disabling the Screen saver that locks after 15 minutes, but that did not soleve the problem. The probleme occurs when a user locks his View session and tries to log back in after a few minutes. The mouse is gone..
Vmware, please help on on this one, I am not migrating to View 50 to fix this. There must be a way of fixing this problem...
Regards
Francois
We has two users with SVGA II more than a month with no issues...
If the view 5 agent worked fine to you, you should plan to migrate to vCenter 5 and Composer 2.7, so you can continue to use view agent 5 and composer.
The interoperabilty matrix shows vSphere 5 is compatible with View 4.6.
http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php?
Hi. I've got the same problem.
VMware view and agent: version 4.6
Guest OS: Windows 7 Pro SP1
The issue happens both using a standard PC and a Wyse C50LE thin client as View Client launchers.
Our users have the same problem too, when logging back into the session there is no mouse cursor available for users to put that credentials in.
Has anyone found a solution to this issue?