PCoIP sessions switching between thin clients

Similar Questions

• Zero Client and Thin Client

  Hi all

  AM new kind of opinion,

  I want to know

  What is the difference between thin and Zero Client

  are all of the Thin/Zero to the RDP clients or just specific type

  Thank you

  OK - all variants of clients include zero (including screens ZC) thanks to the TERA processor an ASIC of RDP implementation in addition to the support of the PCoIP Protocol. Most of the users of zero client select PCoIP due to improved performance, especially the graphics. You can find more information about customers zero at the Teradici FAQ: http://www.teradici.com/pcoip/pcoip-technology/pcoip-faqs.php

  Thin clients certified by the VMware Ready program include variants of the RDP and PCoIP clients installed on an operating system software. You can find compatible devices here: http://www.vmware.com/resources/compatibility/search.php?action=base&deviceCategory=vdm

• XP SP3 causes BSOD during the passage of the WYSE Thin Client session to session VMware VDM Web Access

  Hello

  For our VDI environment, we use both clients Wyse thin (Thin OS 6.2.0_16) and VMware VDM Web Access to access Windows XP virtual machines that are available through the VMware VDM connection server. The connection and the agent server is at version 2.1.1 build-663. We run ESX 3.5 and Virtual Center 2.5 times with update 3.

  The issue I'm having is once a Windows XP SP2 virtual computer has been upgraded to SP3 will be blue screen when I try to access it for the Wyse terminal after his last accessed from VMware VDM Web Access. Order real to get there would be to access the VM SP3 from the Wyse Terminal, then go VDM Web access, and then again from the Wyse Terminal and it will have a blue screen. Disconnect or disconnect makes a difference. I'm curious to see if anyone else has this problem. I enclose the capture of blue screen and the mini dump file. If you need more information please let me know.

  Thanks for your help!

  -Pete

  Hi Peter,.

  The root cause of the problem is change colordepth of 15 bits to 16 bits. Let me explain the cause of the problem.

  -Connection of the terminal WYSE in a VM XP - effective colordepth in the RDP session = 15 bits

  -Access Web VDM from PC connection (I guess) - effective in the RDP session colordepth = 16 bits.

  -The switch back to results WYSE Thin Client = 15 new bits

  This actually switch between colordepth 15 bits to 16 bits and viseversa result BSOD.

  Thank you to use DesktopColorDepth = 16 RGB565 = Yes command in your wnos.ini and try to place this order through brokers VDM. It should solve the problem.

  Thank you

  Blanchon

• SCCM Remote Client - disconnect the PCoIP Session

  Hello

  We have a problem on virtual machines Windows XP 64-bit with SCCM remote client.

  When the user approved the request, PCoIP session closes. This is not the case on the Windows 7 virtual machines.

  I checked pcoip logs and that:

  04/08/2013, 11:36:40.416 > RC LVL:2: 0 MGMT_IMG: CODEC: change of State of CODEC_DISABLED to CODEC_DISABLED

  04/08/2013, 11:36:40.416 > LVL:2 RC: COMMON 0: TERA_PCOIP: session_evenement = TERA_MGMT_SYS_SESS_EVENT_RESET, disconnect the cause (0xfffffe0c)

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: main server: called cb_notify_session_status (mask 0 x 10) with tera_disconnect_cause (0xfffffe0c)

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: server: TERA_MGMT_SYS_SESS_EVENT_RESET cause of disconnection (0xfffffe0c).

  04/08/2013, 11:36:40.416 > LVL:1 RC: SERVER-501: map_tera_to_vdp_connection_result_code: tera unknown disconnect cause(-500)

  04/08/2013, 11:36:40.416 > LVL:1 RC:-501 SERVER: server: map_tera_to_agent_close_code() failed due to disconnection (0xfffffe0c). With the help of PCOIP_AGENT_CLOSE_CODE_BROKER_INITIATED

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: connection_closed: code = 2.

  04/08/2013, 11:36:40.416 > RC LVL:1: 0 VGMAC: the Session Statistics: average TX = 0.116288 average RX = 0.0140269 (Mbit/s) Loss=0.00%/0.00% (R/T)

  04/08/2013, 11:36:40.416 > RC LVL:2: 0 MGMT_SYS: closing of the Session remotely!

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 MGMT_SYS: *.

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 MGMT_SYS: *.

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 MGMT_SYS: *.

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 MGMT_SYS: *.

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: Server mailbox: MBX_SHUTDOWN with agent disconnection (0x0) reason code

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: Server mailbox: stop the mailbox message loop

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: backend: had completed the message of the application

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: backend: output

  04/08/2013, 11:36:40.416 > LVL:2 RC: 0 SERVER: the Server Cleanup: kill pcoip with agent disconnect reason code (0) and wait

  04/08/2013, 11:36:40.416 > LVL:1 RC: SERVER 0: map_agent_to_tera: DISCONNECT_GENERIC-> TERA_DISCONNECT_CAUSE_HOST_BROKER_GENERIC

  04/08/2013, 11:36:40.416 > LVL:0 RC: 0 MGMT_SESS: tear down the session

  04/08/2013, 11:36:40.416 > RC LVL:2: 0 MGMT_VCHAN: VChanPluginExit: closing the plugin 'VMware_Server '.

  04/08/2013, 11:36:40.447 > RC LVL:2: 0 MGMT_VCHAN: VChanPluginExit: Plugin 'VMware_Server' is closed.

  04/08/2013, 11:36:40.447 > RC LVL:1: 0 MGMT_VCHAN: = > parted with success all plugins VChan

  04/08/2013, 11:36:40.447 > LVL:2 RC: 0 SERVER: the Server Cleanup: detachment inputdevtap

  04/08/2013, 11:36:40.447 > LVL:0 RC: EXTERN 0: input_devtap == > can't get the process token for the user.

  04/08/2013, 11:36:40.447 > LVL:2 RC: 0 SERVER: the Server Cleanup: closing of mailboxes

  04/08/2013, 11:36:40.447 > LVL:2 RC: 0 SERVER: the Server Cleanup: free copy of the argument

  04/08/2013, 11:36:40.447 > LVL:2 RC: 0 SERVER: the Server Cleanup: complete cleaning

  Hi Linjo,

  Seems, all my problems are related to the type of OS client!

  I will deploy Windows XP 32-bit or Windows 7 for VDI other sites.

  BR

• View 4 thin client hardware supports PCoIP

  If my thin client is windows-based os, there is no difficulty when we improve the mode 4. But what happens if my thin client is thin-os, such as wyse S10? do I have to replace it with a new model like P20 or seller will provide a new firmware?

  Hi Dingding,

  You can still use your existing endpoint hardware after and upgrade to view 3-4 of the view, as RDP is still available as a graphic distance communication protocol in View 4.

  If however, you want to upgrade to PCoIP, then you will need to worry about your endpoint equipment.

  PCoIP software, you can use VMware View 4 Client for Windows, which runs on Windows XP, Windows Vista and Windows 7. (And maybe even Windows XP Embedded)

  If you want to use your Wyse with PCoIP devices, you must wait for Wyse provide updated models. The P20 is the only model that Wyse announced so far. Wyse in the future will also support PCoIP on thin BONES.

  Here's an announcement from Wyse on PCoIP:

  http://www.BusinessWire.com/portal/site/Google/?ndmViewId=News_view&NewSID=20091110005514&newsLang=en

  Christoph Wegener

• Group ADF opening too many sessions of database JDBC Thin Client.

  Hi all
  
  I have several panels of the ADF, which allows the user to run some simple queries against a database of Oracle is using the view objects ADF and ADF view links and ADF application module.
  Each ADF Panel as I mentioned contains several queries view link and links in the form of Jbuttons to other ADF signs other ADF links running.
  Run Control Panel of the ADF as described here opens up to 21 sessions of data showing as "JDBC Thin Client" when I look at their place of session$ v.
  Why I find myself with a lot of databases of sessions.
  Why didn't he just uses one or two sessions of database to run all of these links to view? It seems that it opens a session of data base for each of these links to view.
  
  How can I change this destructive behavior? I have that one to see one or two sessions of database for the whole ADF matter how ADF display the links it contains.
  Your suggestions are most appreciated.
  
  Thank you.
  Bobby has.

  Why so many AMs? Can not put all the your under a single AM?
  Each AM you will use will open a connection to the DB.

• Thin client HP t520: thin client HP t520 occultation

  Recently, we purchased a few t520 Thin Clients and cannot be shadown using 4.6 SP4 HPDM.  We shadown t510, 5730 and 5740 devices regularly.  With devices t520, the task starts, send, process, and ends, but never opens the shadow session.

  Good news - I got it working.

  Devices t520 necessary an update of the Agent.  Once the Agent has been updated, and VNC enabled - I could also shadown.

  Thanks for your help!

• Thin client HP 420: thin client usb problem

  We test a workstation 420 and everything seems to work fine except when you are connected to an RDP session to our server 2012R2 farm, usb storage disks/keys are not recognized.

  Everything seems to be ok on the thin client in local resources and the USB is recognized when a usb diagnosed.

  Other usb devices are thin dongles, wireless, keyboard / mouse, etc.

  Any thoughts on how to get them recognized in windows Explorer

  So nobody here knows something about thin client HP configurations

  Spoiler (Highlight to read)

• Switching between 2.4 and 5g.

  I have a Nighthawk r7000. It offers two networks: 2.4 G and 5G. Would I be able to manually switch between the 2 networks? I just tried to spend 5 to 2.4 (just) to test it and make sure it worked, and I got a message "unable to join the network. Then I tried again, and my device (iPad) couldn't even SEE the 2.4 g. FYI, I recently downloaded the latest firmware (1.0.5.44). Thanks in advance for your help.

  Just changine SSID and passwords should not change anything other that clients will have to re - authorize on the new SSID.

  However, I have seen the router work well and the brick itself a reboot :-(

• HP Thin Client T5550: HPDM - sending of the zone settings

  Hello everyone, I have a huge issue with my HP Device Manager and I would appreciate your help.

  When I try to send to my HP Thin Client T5550 time zone settings, it is just the time zone of Dublin.

  It doesn't matter what time zone I send, it always comes back to the zone of Dublin.

  The only difference between the time zones on my HPDM and my thin client is UTC and GMT.

  On HPDM zone is defined as UTC, but on the thin client, it is GMT. I don't know if this could cause problems? And if so, how can I solve this?

  For your information, when I send the same zone to my HP Thin Client T520 settings everything works smoothly.

  I would be grateful for all the help I can get.

  I guess that we are talking about Windows CE on T5550. It is actually a known issue of HPDM, because Windows CE is thus more complete support of HPDM, this issue will not be fixed in a newer version of HPDM.

  I suggest that contact technical consultant for the extraordinary. Or if you know the order of change of time zone, you can try to change it through files & records task.

• Thin client HP 5740e: HELP! Expired password and should be changed but access denied when you try to do

  Hello

  I have a thin client HP 5740e and for some reason any local user account requires a password change.  Yet, when I try to change the password it says access denied.  And yet, I can't it to allow me to move to another counts as administrator to open a session.  I held down the SHIFT key during startup, but it always goes straight to this local user account & the expired password prompt. I'm stuck in an infinite loop and do not know how to cope.  Safe mode puts me in the same situation.  And I can't update the BIOS because I can't have everything.

  OS = Windows Embedded Standard 7

  I also tried to reinstall the last image of the HP Web site using a USB key, but it fails every time. I tried 2 different USB drives with the same exact error no each.

  Image, try to install = SP56020

  ERROR: An unexpected condition has occurred

  Does anyone have a suggestion?

  I finally could get as an administrator using RDP to my office.  I didn't know the name of thin client lacked a figure, that's why I've been unsuccessful before that.

  Once I got away, I could watch the local user account permissions.  Now I see what was wrong.

  [Check]      The user cannot change password

  [Disabled] Password never expires

  I still don't know why I couldn't install a new image of the plant, but at least I am now able to work with this device.  I also disabled the automatic connection at the moment.

  Sorry to have littered the Forum!

• Thin Client T510: Do not support the SMB for no image preload on Linux platform

  Hello world

  I have a problem with a Thin Client T510 (C4G87AT #ABA), this one came with Windows CE and today I flashed with a USB to thin Pro 5 (T6X52011). When I want to deploy the image I captured (wallpaper, RD Session etc...) I have the following error:

  2015-08-19 15:30:43 [error details]:... /... / Task/linux/ImageTask_Thinpro.cpp@384: Metheod of the Image is not compatible.
  .. /.. / Task/linux/ImageTask_Thinpro.cpp@1624: do not support SMB for no image preload on Linux platform.

  When I look in the console HPDM, I see the T510 and connected

  Agent version: 4.6.3670.21244

  HDPM 4.6 SP5

  OS: T6X52011

  My OS: Windows 8.1 x 64

  Can someone help me please? Thks and have a nice day.

  Hi, thks for this Council. Theres is how I fix.

  Firstly, the master repository has change from D:\HPDM\HDPM to D:\HPDM on the server, so the configuration was not good at the moment. Another thing, the password of the user hpdm has changed in Active Directory, but not in the configuration. I changed all the settings for in line with the current configuration and capture Images of thinpro news works very well and deploy this new works pictures well too but Deplopyement of old images does not work.

  I'll open another thread if I need assistance. In this case, I'll mark as fixed.

• Get the Thin Client IP address

  Hello. I'm trying to find out the IP address of the machine that I use for programming. I want to use my LabVIEW program on a server. However, the string to the property intellectual VI gives the IP address of the network, so in this case the server IP address. It is a problem, as we hope, in the future, run multiple thin on program clients, if we want the program to know what thin client, it works on. However, I don't have access to the command prompt on the thin client due to administrative restrictions. This eliminates the other solution I found, which was to find the Login Windows user name (each light client has its own unique user name) through different screw which involved the command prompt. Any ideas on how to find the IP address of the customer of the Services Terminal Server Session, I believe that my computer called? Thanks for your time.

  I called and he was referred to this, which worked. We use Citrix server and the username thing worked, and we are now able to run the program for each thin client using his user name.

• How can disable switch between different input languages (= keyboard languages) by pressing the Alt + Shift keys? __

  Although I can now perform steps

  1. On the start menu, choose Control Panel.

  2. In Control Panel, select regional and Language Options.

  3. In the Regional And Language Options dialog box tab, under Text Services and input languages, click details.

  4. In the text Services and input, in the Preferences section languages, dialog box click on the key parameters.

  5. In the dialog box advanced key settings, click Change Key Sequence.

  6. In the change Key Sequence dialog box, clear the switch input languages check box, and click OK.

  7. In the advanced key settings dialog box, click OK.

  8. In the text Services and input languages dialog box, click OK.

  9. In the Regional And Language Options dialog box, click OK.

     But I need some settings registry keys to do the trick above to me, because it is difficult to do it on the number of PCs that requires users to restrict the swith between input languages.
     No idea or help is greatly appreciated.

     Thank you in advance.

  Hello
  I found the place where exactly this may be small :).

  [HKEY_CURRENT_USER\Keyboard Layout\Toggle]
  "Hotkey" = "1".
  'Language Hotkey' = '3 '.
  'Shortcut page layout' = '2 '.

  Change the value of "Language Hotkey" accordingly.

  1 sequence of button enabled; Use Left ALT + SHIFT to switch between locales.
  2 key activated sequence; Use CTRL + SHIFT to switch between locales.
  3 invalid key sequences.
  4 If the default locale is Thai, the grave accent key activates / deactivates the input locale. otherwise the keystrokes are disabled.

  Another problem is that it sits under HKCU as well, same as if I pack this setting with MSI, it won't have a any use to me. Since then, installation is done using MSI localadmin account and HKCU is associated with the current session. If a new user who connects to this settting does not apply, and even if it rises "access denied" :(

  Hope this helps anyone with the same problem.
  Thank you.

• Thin Client t510 - printer redirect on windows server 2003

  Hi all

  just bought 4 T510 Flexible thin client. I have attached USB printer (Brother HL-2040 or a Brother HL-2130), but it does not redirect on the RDP session.

  I tried everything, to my knowledge, but without success. In the options of the Windows driver, I wrote EXACTLY the side server name of the printer (which is actually the same name identified by the customer).

  I noticed in the information system that the RDP version is rdp is 1.6.0 - 1.45...

  I thank in advance.

  I have the same problem but I managed to solve.
  I bought 10 of these T510 terminals, but with the same result on 3 different Windows Server 2008 R2 Terminal different (updated to the latest patch).
  Only one of these terminals sold the year before worked and so I checked the version of the software.
  By installing the old version of the terminals intelligent Zero Client the new T510 work with my printer in the Terminal Server session.
  New version does not work!

  I tried everything... this add features such as storage of the password, the support for the speed, etc... etc..., but the printer no longer works!
  I think that the change in the Protocol version RPD to give me problems.
  Now I have one here in the office with which I am trying to understand if I can solve the problem with the latest versions of the software that I could use.
  We install the Smart Core zero Image Z6X41019 Rev 1 (March 7, 2012) and it should work.
  PS, You must put the printer in T510 in the driver entry not working also the exact name of the driver that you see in Windows.