VMware Horizon Community
hooshoo
Contributor
Contributor

Windows 7 Desktop does not load (black screen then session disconnects) using PCoIP

I am evaulating Horizon View 5.3.0 build-1427931. I have
a manual desktop pool that consists of 2 vCenter managed Windows 7 Enterprise
desktops. When I attempt to connect to those desktops (Using PCOIP) I get a
blank screen then a short period later the session disconnects. I have tried
several steps that I found in KB articles but they have not corrected the
issue. I'm assuming this is some issue related to Windows 7 as I can connect
successfully to Windows XP.

I know that there are a lot of discussions around this type of issue, some of - like I said - which I have tried and others that do not apply to my environment. If anyone has come across this and has any additional ideas I would be greatful.

Thanks!

Reply
0 Kudos
8 Replies
Linjo
Leadership
Leadership

3 things I would try first: (In that order)

Check the video-ram settings on the desktop, maybe the pool-settings have not taken effect yet. You need a shutdow/startup for the VMX-file to be read proprerly.

Reinstall VMware tools, reboot, reinstall View Agent.

Check firewalls etc and make sure that you can reach the desktop on port 4172 UDP/TCP

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
hooshoo
Contributor
Contributor

Well, the port is open. I can connect to other versions of Windows desktops. I have uninstalled and reinstalled tools and view agent. And for the video ram, I set that on the VM trying several different specs.

Reply
0 Kudos
Linjo
Leadership
Leadership

The video RAM is set on the pool (unless you have specified to control it with vSphere Client), and for it to take effect you need to shutdown the vm completely and then boot it again.

Anything in the logs?

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
hooshoo
Contributor
Contributor

Linjo,

Well, initially it (3D Renderer) was set to Disable. I won't be using any 3D type graphics so I assumed I could just leave that do disabled. My only requrement is to support a max of 4 montiors. And I set that and the max resolution in the pool - on the VM side the video was set to Auto Detect.

However, I have played around with the 3D Renderer and set it to Manage using vSphere, automatic, etc. But so far I have not had any luck. Are there any recommended "basic" settings? Again, my only video requirements will be supporting up to 4 monitors.

Reply
0 Kudos
Linjo
Leadership
Leadership

Whatever you set on the vm itself in vCenter will be overwritten by the pool-setting in View unless you set it to "Manage using vSphere".

The most common problem with "Black Screen" is the 3 I listed in my first reply. Make sure that the correct video-driver etc is installed. (The one the the View Installer comes with)

If this still does not work, attach the view agent logfile here an we can dissect it and find the problem for you.

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
hooshoo
Contributor
Contributor

Linjo,

Attached is the pcoip agent log from one of the Windows 7 clients. Just to add here, I am running View 5.3 in eval mode - not that I expect that to make a difference.

I have also tried to set the max video resolution on the pool to the highest resolution, de-installed the vm tools, rebooted, de-installed view agent, rebooted. Re-installed both in that order. The video driver that is loading is doing so during the tools install and that is the VMware SVGA 3D ver 7.14.1.2021.

Reply
0 Kudos
hooshoo
Contributor
Contributor

Linjo, thanks for the responses. I discovered what was going on.

Since this is in POC mode, our FW guy restricted IPs to specific static addresses - we use dhcp for our desktops - and i totally forgot that. So, when I started spinning up these new VMs (windows 7, 8 ) they had dhcp addresses. ERRR! :smileyangry:

Reply
0 Kudos
Linjo
Leadership
Leadership

Great that you figured it out and thanks for reporting back.

// Linjo

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos