FAQ

All models of single-link DVI and VGA monitors are compatible. VP200 processors can support all single-link DVI specification resolutions up to 1920x1200. Each VP200 processor can support two displays, each with resolution up to 1920x1200.

In Firmware 2.x, dual 2560x1600 @30Hz display resolution and experimental support for displays with up to 1536 pixels horizontally and 2048 pixels vertically over a single-link DVI connection are supported.

Note: If your monitor supports 2560x1600 @60Hz but not @30Hz, an external device that scales up the frequency to match that of your display can be used between the Portal and your monitor. An example of such device is the Videomax graphics accelerator by Thruput. For details about this device, seewww.thruput.co.uk

Standalone mode allows the Host Card to operate without installation in a PCIe slot. In Standalone mode, the Host Card is powered from a floppy drive (+5V/+12V) power connector instead of from a PCIe slot. To enable the Standalone mode, the Host Card’s Standalone Mode Header needs to be configured. By default, Standalone mode is disabled and the jumper is set to pin 2-3 of the Standalone Mode Header. To enable Standalone mode, you need to:

(1) Set the jumper to pin 1-2 of the Standalone Mode header. 
(2) Connect the floppy drive power connector.

Note: In Standalone mode, the Host card draws power from an external power supply through the floppy drive power connector. 
Note: In Standalone mode, USB and audio functions are not supported. 
Note: In Standalone mode, the Host Card must be securely installed in the PC/workstation chassis to avoid electrical shorts or physical damage.

Yes. There are many connection brokers with PCoIP session control capabilities. The following companies have announced PCoIP support for their connection broker products.

• ClearCube Sentral
• Ericom PowerTerm WebConnect
• Leostream Connection Broker
• Symantec Workspace Corporate
• VMware View Manager

Other brokers may offer PCoIP compatibility. Please ask your connection broker provider for more information.

VP200 technology does not require users to load a driver on the host PC/workstation. However, for Firmware 2.x, an optional host software driver is available that provides features such as Local Cursor, which can greatly enhance user experience in a WAN environment.

The only additional software you may need is the Realtek High Definition Audio driver, if you are using an OS other than Windows Vista (and you wish to have audio). This driver can be downloaded from Realtek's website.

The firmware can be updated using the Administrative Web Interface and is uploaded to the Host or Portal through the network interface. The PCoIP Management Console can also be used to update the firmware. For details, see PCoIP Management Console User Manual.

Example - Firmware Upload Process using the Administrative Web Interface:

1. Ensure host PC or Workstation is in an idle state (all applications must be closed). 
2. Log in to the Host Administration Web Interface 
3. Select the Firmware Upload webpage and click the Browse button to browse to the firmware “.all” file, e.g. tera1x00_rel1-9_v175.all 
4. Select the File Upload window Open button 
5. Select the webpage Upload button 
6. Select the webpage OK button on the warning window that reads, “Are you sure? This will upload a new firmware image. This operation may take a few minutes.” 
7. Wait for the firmware upload to complete. The following message appears when complete: “Success Flash successfully programmed! You must reset the device for the changes to take effect.” 
8. Select the Reset button.

9. Select the OK button on the warning window that reads, "The PCoIP processor will reset on the next host system restart; your changes will take effect then. Are you sure you want to proceed?" 
10. Repeat steps 2 through 7 on the Portal, but do not restart the Portal. 
11. Restart the host PC/workstation 
12. Reset the Portal 
13. Start PCoIP Session

Note: Be sure that both the Host Card and Portal use the same firmware version.

PCoIP technology is OS-independent. It has been extensively tested with Windows XP and Vista. It is compatible with all PC applications as no hardware or OS changes are required in the host PC/workstation.

Linux operating systems have been tested with human interface devices (HID).

Windows Vista natively contains a high definition audio driver, and we highly recommend that you use this native audio driver if your host PC/workstation uses Windows Vista. For Windows XP and Linux, you must install the Realtek HD audio driver for audio support. This driver can be downloaded from Realtek's website.

You can configure the Portal via the On-screen Display (OSD), Administrative Web Interface, PCoIP Management Console or connection broker. For details, please see the Administrative Interface User Manual, PCoIP Management Console User Manual or contact connection broker supplier(s).

The BIOS configuration settings determine the power level of the host PC/workstation when it is in standby. You can press a function key while the PC boots to access the BIOS configuration settings. 
For example, if S3 is configured in the BIOS, when standby is triggered through the Remote PC Power Button or the OS, the host PC/workstation goes to power level S3.

Connect the DMS-59 to dual DVI cable to the Host Card's DMS-59 connector andconnect the DVI-1 connector of the cable to the primary connector of graphics card. If you are using dual moniors, connect the graphics card's secondary DVI connector to the DVI-2 connector of the cable.

It supports remote power management to the host PC/workstation. In a typical system, a 2-wire Host Card Power Button Cable is connected between the Host Card's Power Button Cable Connector and the PC motherboard's 2-pin power button header.

When the Power Button Cable Connector is used, a jumper should be set to pin 2-3 of the Wake Configuration Header.

With this connection, you can remotely power On and Off your host PC/workstation using the Portal’s Remote PC Power Button.

If the 2-wire Host Card Power Button cable is not connected, the Portal's Remote PC Power Button has no effect. However, the host PC/workstation can still be powered down through the OS.

Each PCoIP session currently requires a minimum of 1Mbps per system with firmware release 2.x and a minimum of 3 Mbps with firmware 1.x. Both firmware 1.x and 2.x can use up to 220 Mbps per system.

Both the PCoIP Host and Portal have configuration parameters that control the amount of traffic they generate. For details, please see the Bandwidth and Image parameters sections of PCoIP Administrative Interface User Manual.

Follow this conservative procedure for determining network requirements which will deliver an excellent user experience under worst case use conditions:

(1) Segment the user base by applications and display 
(2) Determine the per-user bandwidth allocation for each user type 
(3) Determine the number of active users contributing to every link 
(4) Determine the Link Planning Bandwidth for each network link 
(5) Set the Device Bandwidth Target for each PC-over-IP Host.

A typical PCoIP deployment uses a standard IP network and does not require special equipment.

Note: You should not use half-duplex equipment for PCoIP deployment.

PCoIP technology is not specifically distance-sensitive; however, network latency due to distance and switch hops may inhibit the user experience. Generally, PCoIP sessions over a corporate LAN will have little noticeable network latency. PCoIP sessions can also operate over Wide Area Networks, but the additional network latency may be noticeable to users.

Bandwidth limits can be configured and such settings must be set properly for both the Host and Portal via the Administrative Web Interface. For details, please see the Bandwidth section of the PCoIP Administrative Interface User Manual.

In bandwidth-constrained environments, it may be useful to also adjust the imaging parameters to optimize user experience for the bandwidth configuration. Please see the Image section of the PCoIP Administrative Interface User Manual.

We recommend that you test with different bandwidth and imaging parameters to balance bandwidth usage and user experience.

No. Regardless of firmware image-quality settings, still images are always lossless. The time it takes to display them depends on your image-quality settings and available network bandwidth.

For most situations, it is recommended to use 40 for Minimum Image Quality and 90 for Maximum Initial Image Quality. For details, please see the Image section of PCoIP Administrative Interface User Manual.

Maximum display resolution is limited only by the DVI specification; however, practical limitations are network-based and depend on content and the desired user experience. Network bandwidth requirements generally scale with display resolution.

Network bandwidth limitations – whether configured or real – result in reduced update rate and image quality.

PCoIP technology is aware of network congestion via packet loss and delay variation.

When the network is congested, the PCoIP reduces temporal image quality and associated bandwidth usage, and later increases them to take advantage of the available bandwidth when the network is not congested again.

The screen update rate is affected by network congestion, bandwidth settings and imaging settings. Minimum Image Quality and Device Bandwidth settings are available to optimize PCoIP for your network configuration.

For more information, please see the Bandwidth and Image Configuration Example section of the Administrative Interface User Manual.

• The LINK LED on the Portal's Ethernet port is On if it is properly connected to networking equipment such as a switch or router.
• The network icon in the lower-right corner of the OSD does not show a red cross if it is properly connected to the network.
• You can use the ping test in OSD diagnostics to verify that the Portal can reach other devices, such as your Host Card, in the network.

Access to both the Portal and Host Administrative Web Interface are password-protected. Configuration changes via the Portal OSD are also password-protected. However, password protection is disabled by default. It can be enabled using the PCoIP Management Console.

The password is configurable if password-protection is enabled. For further details, please see the Password section of the Administrative Interface Manual.

You can use the Portal's Administrative Web Interface to allow/disallow USB devices by class/sub-class/protocol or vendor ID/product ID. Please see the USB section of PCoIP Administrative Interface User Manual.

Authorizing a hub device will allow any type of device to be subsequently connected through the hub to the host PC/workstation. When it is preferred to maintain USB security (e.g. not allow mass storage devices) while still enabling a multi-function keyboard implemented with an on board USB hub, it is recommended to authorize the multi-function keyboard's hub using Vendor ID/Product ID. If the multi-function keyboard does not have externally available USB ports, then security will be maintained. If there are externally available USB ports, then this implementation will allow any USB device to function (including USB mass storage device, etc.).

1. On the VP200 Zero Client OSD screen under Options select Password and in the Password dialogue box select Reset.
2. You will be presented with a Challenge Code.
3. Provide the Challenge Code to Leadtek sales rep or Leadtek support site.
4. Leadtek may have some additional questions to verify ownership of the device. Once ownership has been determined, Leadtek will open a ticket with Teradici asking for a Response to the Challenge Code.
5. Teradici will provide the Response to Leadtek.
6. Leadtek will provide the Response to the customer.

• If you are using Windows Vista, be sure you are using the OS's native high definition audio driver.
• If you are using Windows Vista 64-bit, be sure the "Enable Microsoft Windows Vista 64-bit mode" option is enabled in the Host Card's Audio Permissions of the Administrative Web Interface.
• If you are using Windows XP or Linux, be sure you have installed the Realtek HD audio driver. This driver can be downloaded from Realtek's website. After installing the Realtek driver, you have enabled the audio function on the Portal. Now you can simply enable the function on the Host before using audio function. In the "Initial Setup" webpage of the Configuration menu, ensure that the audio is enabled. Press "Apply" and then press "Reset". A popup windows appears to remind you that the PCoIP will reset on the next host system restart and your changes will take effect then.
• Be sure that audio is enabled for both the Host and Portal. Audio can be enabled or disabled using the Administrative Web Interface. For more information, please see the Audio section of the PCoIP Administrative Interface User Manual. You must restart the PC after enabling audio for the Host Card.
• Be sure the Host Card is firmly inserted to the host PC/workstation's PCIe slot.
• Be sure your speaker's audio cable is firmly connected to the Portal's rear line-out or headphone jack.
• Windows Vista supports outputting audio to only one port at a time, either the headphone or the rear line-out jack. Be sure you set the desired audio-out jack as default in Sounds under Control Panel in your OS. 
  For example, if you are listening music from the headphone jack but want to switch to the rear line-out jack instead, you need to enable the rear line-out jack by setting it as default in Sounds. Note that you may need to restart the audio application for the change to take effect.

Note: If you are using the Host Card in Standalone mode (not inserted in a PCIe slot), audio and USB functions are not available.

• Be sure the PC power supply is connected to AC power and is on standby.
• Be sure the Wake Configuration Header is properly connected for the desired Wake option.
• If a 2-pin jumper is set to pin 2-3 of the Host Card's Wake Configuration Header, be sure the Host Card Power Button Cable is connected between the Host Card's Power Button Cable Connector and the PC motherboard's front panel On/Off switch header.
• If a 2-pin jumper is set to pin 1-2 of the Host Card's Wake Configuration Header, be sure the Host Card is inserted to a PCIe slot.
• Be sure the Portal and Host are reachable on the network.
• Be sure the Portal's Remote PC Power Button setting is properly configured in the Administrative Web Interface. For more information, please see the Power section of the Administrative Interface manual.
• If DHCP is used to configure the IP address of the Host Card and remote power on no longer functions but did previously, the DHCP lease to the Host Card may have expired while the host PC was powered down. When this happens the Host Card appears to be unplugged from the network and messages sent from the Portal are not forwarded to the Host Card. The DHCP lease expiration time is a deployment specific configuration setting. To avoid this problem, ensure the DHCP lease time is longer than the amount of time a Host Card may be powered down or assign the Host Card IP address statically rather than using DHCP.

• It is likely a Windows OS driver issue, i.e. the "Standard OpenHCD USB Host Controller" did not get installed. Or it may be the problem with generic USB device initialization in Windows. The driver was installed but disabled. Enabling it may solve the problem. Check if there's any exclamation (!) or question (?) mark in Device Manager.
• Be sure that USB device authorization is properly configured in the Administrative Web Interface for the Portal (see the USB section of the Administrative Interface Manual).
• Be sure the Host Card is firmly inserted in the host PC/workstation's PCIe slot.

If you are using the Host Card in Standalone mode (not inserted in a PCIe slot), audio and USB functions are not available.

• Be sure all network cables are firmly connected and the network jack activity lights are On.
• Be sure that the Host and Portal are reachable on the network (e.g. subnets are not masked).
• If Connection Management and Host Discovery are disabled, be sure the Host Card's IP and MAC addresses are properly configured in the Session tab of the OSD, or in the Portal's Administrative Web Interface. Also be sure the "accept any peer" option is enabled in the Host Card's Session page in the Web Administrative Interface.

Be sure the Portal's power cable is firmly connected and plugged into a functioning AC outlet. Press the Portal power switch to ON. The Power LED should light. If the Portal is properly connected to a monitor, the OSD will appear on the monitor in approximately 10 seconds.

• Be sure the Host and Portal network cables are firmly connected and the network jack activity lights are lit on both the Host and Portal.
• Be sure the Host and Portal are reachable on the network (e.g. their subnets are not masked).
• Be sure the ports required for PCoIP are open and not blocked by IT administrators.
• Be sure the DVI cable(s) are properly connected between the GPU and the Host Card at the host PC/workstation.
• Be sure the DVI cable(s) are properly connected to the Portal.
• Be sure Connection Management is disabled in the OSD when a connection broker is not used.
• Be sure the Host Card's and Portal's Ethernet cable is connected to a LAN port but not a WAN port of a router when connected to a local network.

• Power cycle your host PC/workstation if you encounter this issue.
• Be sure the graphics card's DVI output is connected to the Host Card at the host PC/workstation. Note that the Host Card is not compatible with VGA output.
• Be sure a PCoIP session has been connected.
• Be sure the DVI cables are firmly connected on the Host Card and Portal.
• Be sure that a DVI cable is connected between the graphics card's DVI port that is driving video signals and the Host card's DVI port.
• Be sure the monitors support the PCoIP supported resolution.
• Be sure the proper graphics card driver is installed.
• Be sure the default video output option in your BIOS is properly configured. Most BIOS lets you choose PCIe, VGA, or AUTO as default.
• Be sure your desired displays are enabled in display properties of your OS. (e.g. right click in Desktop --> Properties --> Settings --> "Extend my Windows desktop onto this monitor") For instance, if you have on-board VGA and a DVI graphics card in your host PC/workstation, and video outputs only from your VGA but not DVI port, you can connect a monitor to your host PC/workstation using a VGA cable and then enable the monitors connected to your Portal by enabling them in display properties of your OS.

If the problem is still unresolved, try connecting a monitor directly to the DVI output port of the graphics card to verify that the graphics card is working properly.