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.
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.
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:
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.
From some recent comments it seems there were still some parser errors showing up between View 5.0 and View 5.1 logs. Having been sent some sample logs I identified that the PCoIP version was different (newer) than what I was expecting for View 5.1 GA. I’ve updated the parser to identify this new version and key off it for proper parsing (at least in my limited testing).
This means there’s an update to the parser and the viewer to reflect the new versioning. As always the Viewer will update itself, but you’ll need to grab the parser from here.
The updated parser can found here. It should report version 1.0.0158 when passed ‘-h’.
If you need to freshly install the viewer you can find it here.