Unable to login in VMware View 5

[Ooghavanth]

I recently went through a demonstration test, and was impressed enough to order 10 Samsung NC190 zero customers and a pack of 10 licenses of VMware View Premier. The first 4 users are very happy (I'm sure it would be too much to go from a Gateway Windows 7 to 8 years running on a server). The fifth has a strange trouble. The first time you set your system, I noticed when I entered the Vista client, which would go black, wait about 10 seconds, then return to the login screen. I have connected to your virtual machine through the vSphere console and reboot the system. Then, he connected perfectly and it was working normally for the day. This morning, I had the same trouble. Reboot the virtual machine again, and she was working very well. The only difference between it and the rest of the guinea pig, is that she has two monitors (like many people who hope to turn in the future)

[Diamond!]

Is this the user connects to a dedicated group? If you login from the client console to see how the user on that particular machine, what happens?

[Alfons]

Is this the user connects to a dedicated group? If you login from the client console to see how the user on that particular machine, what happens?

This is a dedicated virtual machine, I have a floating swimming pool (however, at least).I'll have to try the next time it fails, as repeated log outs / ins do not produce a failed login.

[!Shea!]

Could it be that the video drivers have been updated in view of 5 (ie, 3D) and while you are still using ESXi 4.1 something that is not converting correctly? Since it is the only one using multiple monitors, maybe this is a hint?

[DIMINUTIVE!]

Could it be that the video drivers have been updated in view of 5 (ie, 3D) and while you are still using ESXi 4.1 something that is not converting correctly? Since it is the only one using multiple monitors, maybe this is a hint?

That could be the case, but one would think that the issue would happen in each connection and a reboot is not correct.

[Erakna]

I've seen when upgrading from 4.x 5.x ESXi some hardware / driver did not work options (NIC).

It could be an option; restart of the console would be a solution if this is the rare case. And I mean ESXi 5, no view 5

[Go!pee]

The same difficulty happened again this morning. As an experiment, having the user name to your PC via dedicated to vSphere console on my laptop. Connected perfectly. In line out, and he'd try again on the client zero. Connected perfectly. Do not restart the virtual PC.

10/28/2011, 07:59:26.116> LVL:2 RC:   0        MGMT_SYS :SESSION ACTIVE
10/27/2011, 07:59:26.116> LVL:2 RC:   0          COMMON :TERA_PCOIP: SESSION_EVENT=TERA_MGMT_SYS_SESS_EVENT_ACTIVE
10/27/2011, 07:59:26.116> LVL:2 RC:   0          SERVER :server main: cb_notify_session_status called (mask 0x8) with tera_disconnect_cause (0x0)
10/27/2011, 07:59:26.116> LVL:2 RC:   0          SERVER :server main: TERA_MGMT_SYS_SESS_EVENT_ACTIVE.
10/27/2011, 07:59:26.116> LVL:2 RC:   0        MGMT_HDA :AUDIO silence state changed from 1 to 0
10/27/2011, 07:59:26.116> LVL:2 RC:   0        MGMT_HDA :Payload type changes to 71 (audio_enable=1)
10/27/2011, 07:59:26.116> LVL:2 RC:   0        MGMT_HDA :AUDIO enable changed state from 0 to 1
10/27/2011, 07:59:26.118> LVL:2 RC:   0        MGMT_IMG :CODEC: Processing MGMT_IMG_APDU_TYPE_CFG_ACK. [pri = 0]
10/27/2011, 07:59:26.119> LVL:2 RC:   0        MGMT_IMG :Zero client sent preferred topology for display 0: resolution=1280x1024, origin=(0, 0), rotation=0
10/27/2011, 07:59:26.119> LVL:2 RC:   0        MGMT_IMG :Zero client sent preferred topology for display 1: resolution=1024x768, origin=(1280, 0), rotation=0
10/27/2011, 07:59:26.119> LVL:2 RC:   0        MGMT_IMG :is_resolution_supported: pri_num: 0, display: 0, width: 1280, height: 1024,

[JustineBB]

I would also check the video memory allocated to virtual machine within the dual monitor console. If too low, maybe some of his arrest properly and restart a deleted memory.