Skip to content

Posts from the ‘Uncategorized’ Category


PCoIP Log Viewer Updated for View 5.3

Well, like an idiot, I’ve had this update ready to go for a while (before xmas of 2013) and had left it in a beta state.  I never heard anything bad back from the beta testers (which could be good or bad I guess!) but I’ll assume things are working ok.

So it’s probably time to move this over into “prod” and get it out there as I’ve had a few requests recently for this update.

So long as you are only parsing View 5.2 or newer log files you can do it all in the Log Viewer itself under the new parsing framework. You can find the Log Viewer here.

If you need to parse older log files (5.1 or older) you’ll need the standalone parser for that.  You can find it linked inside the content here.

For those of you who already have the Log Viewer installed it should auto update – if it does not, or if it breaks somehow, please uninstall it via the Java Control Panel console (or appropriate interface for your chosen OS), and then re-install it from the JNLP file linked above.

Thank you and let me know if you’re having issues with log files!  I had a very limited subset to test with when making the update so it’s quite likely there will be errors lurking out there somewhere.


Rethinking the PCoIP Config Utility

As I am doing some planning for View 5.3 and the new dynamic PCoIP tuning feature I am debating re-writing the PCoIP Config Utility from the ground up.  I’d like your feedback on a few items though, the first of which is this-

One “issue” with the utility as it stands today is that it requires Admin privileges to run.  This can be dealt with in various ways but there’s only really one reason it requires escalation – the PCoIP registry entries are in HKLM and not HKCU.  In order to get access to the keys and, most importantly, make changes to them, you need higher privileges.

This could be gotten around by changing the security on the Registry keys that house the PCoIP settings, but I don’t know if this would be something frowned upon by most users and/or their security teams.

So, I am asking:  Are people OK with things as they are and having the app require escalation, or would they prefer to make other changes and have the app run without escalation?  If so, what changes are they willing to do?

Also, I am open to other thoughts/options on how to implement this as well.  One option I tossed around a while ago was to install a system-level service with access to the required Registry keys and then have the front-end piece talk to that service to apply changes.  This way, you could install the service once into a master image and users could run the utility as-is and stop/restart it without any special permissions.  Is this a better way?

Please drop your thoughts into the comments.


PCoIP Config Utility Download Errors

This is just a quick update – I know the link to download this is dead. I am currently tied up at VMware Partner Exchange but I know something is screwed up on my web host. I can’t dig into it now but will get it sorted as soon as I get home (this weekend). Apologies for the mess, this just blew up at a time where I don’t have the tools and access I need to fix it.

Stay tuned for more info this weekend.


Updated TinyCore Builder Link

For those hoping to find a simple and quick method to create a small, bootable Linux installation for PC repurposing – look no further…

TinyCore Builder allows you to fill out a simple form, and get a very compact bootable Linux image with the VMware View Client out the other end. The image provided is ideal for USB or PXE booting a repurposed PC againbst a VMware View environment.

The TinyCore Builder recently moved so if you were already aware of and using this tool, please update your links to the following URL:



PCoIP Configuration Utility Release 1.0 – Update and Shame!

Well, this is the kind of post I don’t like to make.  After getting a few responses and doing some additional troubleshooting (thanks Ed) I’ve found an issue with the new session disconnection detection that can cause the app to basically fail right from launch if you provide admin level credentials to authorize the app.  I believe this is related to the process elevating and then HKCU being visible to the app via the elevated user vs. the actual logged in user.  I’m going to do some tweaking and testing and hopefully get a fix for this up soon.  Clearly not everyone will be hit by this (I was never prompted to provide credentials in my testing so never caught this) but I have to think a good number of people will be, so for now, if you see an error about not finding the Volatile Environment – you have my sincerest apologies!

I’ll update the blog as soon as a fix is found.