We are testing VMware View as a possible solution in our hospital. We have log login times that make most devices unacceptable to our physician group. VMWare View, when run from a laptop or a new WYSE R90L (Wireless N) makes a connection and brings up a desktop in approximately 10 seconds or less. The V90L machines (1200 Eden, 2 GB Flash and 1 GB RAM) take 25 to 30 seconds to make this same connection wired or wireless.
Looking at the application event viewer it seems that after the "Windows client started" event there is a long delay (20-30 seconds) until the next entry "Tunnel Unnamed: connected to server'xxx.xxx.xxx' start tunnel protocol. The logon screen for VMView remains on the screen during this gap, once the connection is established the display of the new desktop is very quick.
We never show any memomry spikes and wswc.exe causes a few very brief blips when looking in task manager during the process.
Any idea how to get the login and presentation of the virtual desktop to equal the R90L would be greatly appreciated. I have 50+ of the V90L and need to get them up to speed.
Thanks
Added the DNS suffix to my TCP\IP settings and the thing simply flies. Problem seems resolved.
Looking at the application event viewer it seems that after the "Windows client started" event there is a long delay (20-30 seconds) until the next entry "Tunnel Unnamed: connected to server'xxx.xxx.xxx' start tunnel protocol. The logon screen for VMView remains on the screen during this gap, once the connection is established the display of the new desktop is very quick.
We never show any memomry spikes and wswc.exe causes a few very brief blips when looking in task manager during the process.
Any idea how to get the login and presentation of the virtual desktop to equal the R90L would be greatly appreciated. I have 50+ of the V90L and need to get them up to speed.
Thanks
Added the DNS suffix to my TCP\IP settings and the thing simply flies. Problem seems resolved.
Tags:
performance,
wyse,
v90l,
connection