Unable to connect desktop after view 5 upgrade

[Kazmierz]

I upgraded from the view from 4.6 to 5 this weekend. I updated my virtual desktops by improving tools and hardware VMware virtual v8 and after uninstalling the old agent and reinstall the new agent v5. Then reassembled my desktop. Now nobody can connect to desktop computers. When using RDP the error is "Connection to remote computer" and when used PCoIP the error is "Connection to remote computer". I try by means of a view of client and client 4.6 in Vista 5. This is a thin client (Wyse R90L7). Ideas?

[Hipolit]

The agent should always be installed last.Have you purchased the remaining components, View and View Composer Brokers? What SVGA driver version you have now?

[HiSpeed]

They present themselves as "available" in the View Manager.ESXi servers, Virtual Center, View Manager and View Composer has been updated.The driver says VMware SVGA 3D SVGA (Microsoft Corporation - WDDM), date 29/08/11, version 7.14.1.1061

[Connect_Me]

During troubleshooting, I realized that some desktops are connected very well and others do not connect. If you open that do not connect with the VI Client, virtual machine is on the screen CTRL + ALT + DEL, and cannot move the mouse or type. However, the operating system is the answer, because you can use "guest Restart" option, which uses a standard OS locking / rebooting. I think that the operating system is there and until (at least most), but not just take the keyboard or mouse. Once the virtual machine reboots, keyboard and mouse function again in the VI client. If the client attempts to connect to Vista, which may or may not connect to (if given the same desktop). If not connected, then you find that the mouse and keyboard are dead once again on the client VI.

I have rebuilt a Windows 7 desktop VM from scratch, and so far it looks good. However, I really do not want to have to rebuild things every time an update of Vista comes out.

It seems that this may be some kind of mistake for the reason that they are seeing the same thing. VMware engineer who has been "helping" me has not called me back over 2 days. I'm very happy with the hold up of VMware now. By the way, if a person observe this and VMware would like to lend a hand me more than the average person in my case, I have a pool with a virtual machine that exibit this problem. There is a DMP file wsnm in the virtual machine, and no records. Maybe that helps someone to find out what VMware is in the gong.

[Potawatomi]

As support for VMware (and all other desks I call hold up), I keep calling them every day in its place of waiting for a reply.

[Farrah]

Win7 also included a new 32-bit-VM from scratch, but this did not solve my problem. VM has the same black screen problem when using PCoIP.

It turned out that my desktop client is still beta. So after installing the client on the desktop and reboot, I got the new working structure W7 image, but the old image still having problems