Skip to content

February 27, 2013

8

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.

Read more from Uncategorized
8 Comments Post a comment
  1. Dwayne O'Hara
    Mar 2 2013

    I woudl love to get hold of the PCOIP config utility as i have been asked to improve the perfomance of PCOIP for many bad wan sites

    Reply
    • RexRemus
      Mar 4 2013

      The download should be back up

      Reply
  2. peter
    Mar 4 2013

    hi, pls let us know when the magic pcoip tool is back online

    peter

    Reply
    • RexRemus
      Mar 4 2013

      Sorry all. It should be back online now.

      Reply
  3. Dwayne O'Hara
    Mar 4 2013

    Fanatastic tool, Im so happy you managed to get the download link sorted.
    I can now simulate sort of what my user exp will be when i skinny down the settings

    Thanks, looking forward to the next version

    Woudl be good to have a display that shows current settings

    Reply
  4. l8nighter
    Mar 21 2013

    Can someone else verify the PCoIP Log Viewer works correctly with View 5.2? I can get it to convert the log file to xml but when I go to display it as a graph it doesn’t show anything. Thanks

    Reply
  5. Brandon Seymour
    Oct 18 2013

    can someone explain to me what the Variance is and if I see loss there what to adjust?

    Reply
    • RexRemus
      Oct 18 2013

      Variance is more or less equivalent to jitter – it’s a measure of the delta between ping times or how “consistent” the latency is. A steady stream of pings like this: 99ms, 100ms, 102ms, 98ms has a low variance, a stream of pings like this: 99ms, 150ms, 45ms, 110ms has a high variance.

      When you see ping times and variance move and it correlates with packet loss it’s not something you’re likely to be able to fix within the protocol. That indicative of improper (of non-existent) QoS setup, an overloaded (too small) circuit, or some other factor affecting the delivery of the VDI session. It’s almost impossible to say what exactly, but it’s pointing you to examine the network infrastructure more than the protocol itself.

      Reply

Share your thoughts, post a comment.

(required)
(required)

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

Subscribe to comments