Comments on: How to get PCoIP with View 4 to work every time! http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/ Virtualization at a glance Mon, 06 Feb 2012 23:55:00 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Christoph Harding http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/comment-page-1/#comment-260 Christoph Harding Thu, 13 Jan 2011 21:34:00 +0000 http://www.thatsmyview.net/?p=317#comment-260 You can setup that when you add a new desktop. You can setup that when you add a new desktop.

]]> By: Unleaded http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/comment-page-1/#comment-259 Unleaded Thu, 13 Jan 2011 21:30:00 +0000 http://www.thatsmyview.net/?p=317#comment-259 How do you set the desktop up as an "individual desktop" in the view manager? How do you set the desktop up as an “individual desktop” in the view manager?

]]> By: How to fix PCoIP VRAM issue with PowerShell, t5545 supports PCoIP now « VM Junkie http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/comment-page-1/#comment-61 How to fix PCoIP VRAM issue with PowerShell, t5545 supports PCoIP now « VM Junkie Wed, 03 Feb 2010 00:46:46 +0000 http://www.thatsmyview.net/?p=317#comment-61 [...] The better fix is to set your template’s VRAM properly. This is easier said than done, because there are bugs in the vSphere Client’s video settings dialog box that causes some settings (like the number of monitors) not to be written to the VMX file. So the only way to do this reliably has been to add the VM has an Individual Desktop in View Manager and have it do the settings properly. This was outlined at this That’s my View blog post. [...] [...] The better fix is to set your template’s VRAM properly. This is easier said than done, because there are bugs in the vSphere Client’s video settings dialog box that causes some settings (like the number of monitors) not to be written to the VMX file. So the only way to do this reliably has been to add the VM has an Individual Desktop in View Manager and have it do the settings properly. This was outlined at this That’s my View blog post. [...]

]]> By: MrBeatnik http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/comment-page-1/#comment-57 MrBeatnik Thu, 21 Jan 2010 15:40:37 +0000 http://www.thatsmyview.net/?p=317#comment-57 Quick questions.<br><br>Point 7 says "If PCoIP/Screen resizing isn’t already working (VI3.5)".<br>Does this imply that 3.5 causes some issues with this (I'm already finding various issues with View 4 in a 3.5 infrastructure)? Point 7 would not apply if using vSphere?<br><br>It .NET required at all? I appreciate .NET will likey be needed for some apps, but in a basic VM setup, do you need .NET for the PCoIP functionality?<br><br>Cheers! Quick questions.

Point 7 says “If PCoIP/Screen resizing isn’t already working (VI3.5)”.
Does this imply that 3.5 causes some issues with this (I'm already finding various issues with View 4 in a 3.5 infrastructure)? Point 7 would not apply if using vSphere?

It .NET required at all? I appreciate .NET will likey be needed for some apps, but in a basic VM setup, do you need .NET for the PCoIP functionality?

Cheers!

]]> By: Adam http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/comment-page-1/#comment-52 Adam Sat, 09 Jan 2010 01:44:11 +0000 http://www.thatsmyview.net/?p=317#comment-52 Can you explain more or point me in the right direction for these "Known Issues" with .NET Framework. I am having issues with crystal reports viewer as well as office 2003 displaying properly. Can you explain more or point me in the right direction for these “Known Issues” with .NET Framework. I am having issues with crystal reports viewer as well as office 2003 displaying properly.

]]> By: Saroun Sam http://www.thatsmyview.net/2009/12/18/how-to-get-pcoip-with-view-4-to-work-every-time/comment-page-1/#comment-51 Saroun Sam Tue, 05 Jan 2010 08:28:29 +0000 http://www.thatsmyview.net/?p=317#comment-51 Another big problem is not being able to use PCoIP at all. You try to connect with PCoIP but it gives you a black screen and then just shuts down the client. I have found that you have to crank up the hardware acceleration to the max and then right-click the VM and choose Edit Settings. Don't make any changes and simply click OK--this sends a task into vCenter called "Reconfiguring Virtual Machine" and it seems to apply the changes made through the Console. I believe it forces the VM to re-read its .VMX file. After this, try to reconnect again--you may have to try twice but PCoIP will no longer give you a black screen. Another big problem is not being able to use PCoIP at all. You try to connect with PCoIP but it gives you a black screen and then just shuts down the client. I have found that you have to crank up the hardware acceleration to the max and then right-click the VM and choose Edit Settings. Don't make any changes and simply click OK–this sends a task into vCenter called “Reconfiguring Virtual Machine” and it seems to apply the changes made through the Console. I believe it forces the VM to re-read its .VMX file. After this, try to reconnect again–you may have to try twice but PCoIP will no longer give you a black screen.

]]>