Skip to content

September 20, 2012

8

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.

Read more from Uncategorized
8 Comments Post a comment
  1. james
    Nov 14 2012

    I seem to have run headlong into this in my setup. I’m using a standard non-privilaged user as my default, but then providing my admin level account when trying to run the app. (Testing for me only, rather than for users) but it runs into the Volatile Env problem.

    Any progress on a workaround / fix?

    Reply
  2. Saqib Fayyaz
    Nov 19 2012

    Experiencing extrememly slow login issues with PCOIP – hopefully this will help.

    Any tips are welcome!!

    Reply
  3. May 14 2013

    Is is possible to export profiles, then import them to another VM?

    Thanks

    Jonathan

    Reply
    • RexRemus
      May 22 2013

      If you nabbed the registry key where I save them it should be pretty easy. You could also just make your own .REG files ahead of time and drop them in and the tool should just pickup those profiles and go.

      The config data is stored under:
      HKCU\Software\PCoIP Config

      If you dump that out and tweak it you should be ok. I do have plans to add better support around import/export in a future release but for now this is what we’ve got.

      Reply
  4. Brad
    Jul 3 2013

    Any reason why after running PCoIP Config and select the default profile, I am getting no info. Everything just shows “0″ as a result, like it’s not reading any data. Any help would be appreciated.

    Thanks,

    Brad

    Reply
    • Brad
      Jul 3 2013

      Sorry, just noticed it works for view 5.0 and 5.1. I’m guessing that is why I am getting no data.

      Thanks,

      Brad

      Reply
  5. Brandon
    Aug 22 2013

    I was wondering if you could explain more on the health score. I get a lot of red and yellow for loss and variance. What does that tell me needs to be adjusted?

    Reply
    • RexRemus
      Sep 30 2013

      It may not be something you CAN adjust. High variance is more indicative of poor network conditions and you can’t fix those from PCoIP. I’ll come back to that in a moment, but let’s address latency now – Latency is one of the few items that is a simple and direct measurement, the bottom line is this – if it’s 250ms or greater it’s basically going to be in the red as that’s the max “supported” latency from VMware. That doesn’t mean a session can’t work with higher latency, only that the overall experience (health score) is going to be impacted by the latency. The reduced score will primarily come from the high latency. It doesn’t mean it needs to be “fixed” – if you’re sending desktops across the ocean high latency is a given, it’s just warning you that the experience is reduced and it’s being heavily reduced by THAT factor. So high latency alone isn’t major cause for alarm.

      Variance on the other hand IS more of a concern. Latency and variance work together. A solid 250ms with a low variance is good. There’s delay, noticeable delay, but it’s consistent for the end user and they can adapt. 250ms of latency, with a high variance (staying in orange/red), is not so good. This indicates possible network congestion, almost certainly increased packet loss because of it, and an inconsistent experience for your users. This may be because PCoIP is not properly prioritized in QoS/CoS on the network circuit, or simply that the circuit is too small and needs to be increased in size. In either case, the fix is not in the protocol, it’s in the environment around it.

      Reply

Share your thoughts, post a comment.

(required)
(required)

Note: HTML is allowed. Your email address will never be published.

Subscribe to comments