Recently, I have observed an annoying issue with Teradici Zero Clients (Wyse and Samsung) while users are logging into the device. After authentication, the virtual desktop display starts rapid "black/white screen" on the display while waiting to finalize login. I tracked the problem down to the windows 7 PCoIP video driver trying to adjust to the resolution of the monitor attached to the Zero Client. Although this does not impact the overall connection most customers just live with the "screen blinking", personally I don't like it! The Windows, Mac and Smartphone clients work just fine, but with the resolution changes recommended the connections seem to be much quicker at startup.
So, through much testing with zero clients, thin clients, ThinLaunch (which rocks BTW) and end user connection validations to VMWare View environments, I believe I found a easy work around for this issue.
Resolution
The issue is with the base image configuration for VMWare View deployments. By Default, a virtual machine in vSphere 5.0 is not set to "Auto Detect" video settings. Secondly, the default screen resolution is commonly changed on the base image for console access from 800x600 to something larger for better console display. The base image is used as the golden image so all desktops inherit VM settings. In certain situations with Thin and Zero clients, the embedded agent does not react well with display changes from default settings and the view agent needs to utilize the Auto Detect VM settings rather than adjusted settings.
Note: 3D Rendering with VMWare View is still on my Radar Screen and so far, working AWESOME!!!!! However, I need to validate infrastructure impact to reference architectures.
So, in conjunction to the standard base image customization, please perform the following additional adjustments:
1) Set the default base image to Auto Detect on the Video Settings when the VM is powered off:
2) Set the default resolution on the base image to 800x600:
After these settings are performed the image resolution and login to the Zero Clients from Teradici will perform much better without the blinking screen.
Please feel free to comment.
Enjoy!!!
Great Post When I get to % this wil be helpful. On 4.6 now. question. Have you had users that have need to set resolution differently on teradici zero clients? The options are not available for my users. Thoughts?
ReplyDeleteYes...The issue is with the base image settings and vSPhere 5.0...I have several deployments on View 5.0, and vSphere 4.1..Just ensure the "auto detect" is set and low resolution after the View agent is installed...Good luck and let me know how it goes...
ReplyDeleteAlso, review this thread. You can use GPO's and registry settings
ReplyDeletehttp://forums.techarena.in/windows-software/1429289.htm
We are having a similar problem with zero clients and View 5.0. The issue we have is when the windows guest times out and locks the screen (no screen saver set). If you "wake the screen" the resolution is set extremely low or to an unsupported resolution and sometimes the 2nd monitor doesn't come back on. The only way to fix this is to reset the zero client. We are using Dell 20" wide screen monitors. I have tried the fix you recommended with no luck. Anyone else have this problem?
ReplyDeleteCheck out the latest updates on teradici web site. Seems to have a few issues that are resolved with 3.51
ReplyDeleteRecommended Workarounds for Reported Display Issues when Connecting to VMware View 5.0 virtual desktops (15134-806)
ReplyDeleteIf you are planning to move to View 5.0 or have already updated your environment to View 5.0, note that there have been some reported display issues when connecting to PCoIP Zero Clients. Some of the issues may also occur when using VMware View 5.0 software clients.
Please use the following recommended workarounds for View 5.0 deployments with PCoIP Zero Clients:
Disable display power savings mode in the Windows virtual desktop when using dual displays
Ensure that the primary DVI port is used for PCoIP Zero clients when using a single display
Do not disconnect the primary display DVI cable during a session
Disable 3D screen savers per VMware Recommendations
Ensure that the proper SVGA driver is installed
Configure VMX file to adjust the MKS polling rate
For more information, please review the following Knowledge Base articles which contain detailed information on known issues and workarounds.
Cannot Connect a PCoIP Zero Client to a VMware View 5.0 Desktop (15134-785)
Cannot connect a PCoIP Zero Client to VMware View 5.0 due to Display Power Savings Configuration (15134-792)
Second Display Blank Connecting a PCoIP Zero Client to VMware View 5.0 (15134-793)
3D Screen Saver Causes Display Blanking and Moves Screen Icons (15134-871)
Why do I have dual display issues after I upgrade to View 5.0? (15134-911)
Poor performance moving windows between multiple displays in a VMware View 5.0 session (15134-982)
Teradici is working with VMware to investigate workarounds and potential resolutions in View 5.0. Teradici will update the Knowledge Base with the latest information on issues observed and reported by customers. Subscribe to this KB to receive updates.
If you encounter one of these above issues, or experience other problematic behavior with VMware View 5.0 with PCoIP Zero Clients, please contact Teradici Support for assistance.
Thanks...It is one of the best post from other. It is a useful and charming post.It is extremely helpful for me.
ReplyDeleteThin Clients & Zero Client
This is really helps for my search and amazingly it was on my searching criteria.Thanks
ReplyDeleteThin Client Software & RDP Thin Client
Clients can include photographs, recordings or shading solids to their smash impact. Basically drag the media into the timetable and afterward apply it to the generator. Once the media is inside the generator, clients can uncheck the perceivability box of the first media layer. Motion Effects
ReplyDelete