Management of PCOIP devices


Reading the post from Andrew Sharrock about the Wyse P20 and the management of it, I came across the Teradici PCoIP Management Console provided by Wyse.

Maybe I’m duplicating some of Andrew’s post, but these are the steps I made (and screenshots from my environment) when I configured the client with the Teradici PCoIP Management Console.

First I downloaded the management console: a zip file containing vmware virtual machine files (vmx & vmdk). Next I imported the prepped virtual machine (, using the vCenter converter plugin. The conversion is needed because they assume that you will run the VM with VMware Player.

The import is very straight forward and after turning it on you will see a basic menu in the console stating that you can access the web interface at a given ip-adress. You can also alter things like the hostname, IP (dhcp=standard), the password for the web interface (which is blank by default) and more…


Next I fired up my IE8-browser and typed the web interface adress into the adress bar of IE8. To my surprise I got the message my browser was not supported. It even tells me what browser to use: Firefox 3


Google Chrome also does not work, changed to another machine and started up Firefox (3.5.5) from there and it worked. The first thing the web interface comes up with is a license agreement you will have to agree to.


When the you agree to the license agreement the web console does appear, which has a nice design and looks very usable at first sight.

Teradici web console

I noticed that it had discovered my client (portal) right away when I first looked at the web interface. The other thing I noticed was the option to use SRV records for the Management Console and the Connection Broker, i’ll take a look at that another time maybe.

On the DEVICES tab I clicked the device and it gives you all the options you can set and save in a profile to manage groups of thin/zero PCoIP clients.


Browsing through the settings I noticed that it detected the hardware connected to the PCoIP terminal e.g. mouse and monitor.


The first thing to configure will be the View Manager Server (connection broker), to do this you first have to create a (device) group (or use default group) with a profile and add the device to it. The groups profile can then be modified to contain the setting for the View Manager Server. After modifying the profile apply the profile to the device or all devices and your settings are effective.

Back to the start screen of the device management tab you can see that the device is not belonging to a group yet.


Select the device and choose a group from the drop down box and hit “Add”, this adds the device to the chosen group. Next is the profile.

device added

Now a profile has to be created and assigned to the default group, to do that click on the profile tab and click “add new”.


When the profile is ready click on “Set Properties” to be able to enter the settings for the device like the IP/hostname for the View Manager etc.


Now you’ve set the right properties, the group has to be configured to use this profile.

apply profile

When the group change is saved the group properties (profile application status) show whether the profile is applied or not, if necessary click “apply profile”.

after applying the profile to the group

After applying the profile to the group the thin client configured, you can tell the device or group of devices to reset in order to try to connect with the new settings using the POWER tab from the management console.


  1. Thanks for the review! I just wanted to point out that the latest version of the PCoIP Management Console (1.2.2) supports Internet Explorer 7 and 8 in addition to Firefox 3.0 and 3.5.

    Management Console product manager

  2. Pingback: New Wyse P20 Firmware 3.1.0 & PCoIP Mgmt Console 1.2.2 | Virtual Architect

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.