View 4 thin client hardware supports PCoIP

Similar Questions

• Any thin client with support of 3G connection

  I think to connect remote sites using the 3 G connection. So is there any thin client that supports 3G. The right choice is TC and 3G modem is the right choice. The desktop environment is entirely a visualization of VMware VDI.

  Hiiich

  Some thin client comes with a USB port. So I think in that there is no problem with the help of the USB modem if you can install the drivers and compatible software. But so far there is no such thin clients, with support from the 3G connection or USB modem. Everything must be based on a LAN or WLAN connection.

  milton123

• Zero Client vs. Thin Client

  I spent days trying to figure why my USB printers randomly stop working with my Zero Client/Linked Clones. I support the case open with VMware and Teradici. Anyway, as I continue to troubleshoot, I started to wonder, would I have the same problem if I was using a thin Client. It really makes me think, so I decided to make this post.

  I would ask you all, who is using zero Clients, that is using thin Clients (which models) and why?

  In my case, I'll settle for those using Zero Clients and Thin Clients that support PCoIP hear and I would like to exclude things like VDI Blaster and all types of jobs reallocated.

  I'm curious about the advantages/disadvantages of each.

  Thank you

  Mike

  I have two scripts VBS permanently running, one as an administrator and the other as the user.  The admin script periodically stop the spooler service deletes the spooler files (if they are old) and then restarts the service.  In our environment, all local USB printers are printers Dell.  The second script (which runs under the logged in user) periodically checks to make sure that the default printer is correct (ensuring that it's Dell). If a user moves from one client to another (where the default printer may need to be different), the script will change the default printer.

  If you are good with scripts, you should be able to adapt to your environment.  Otherwise PM me and I can help you.

  https://github.com/jftuga/VMware/tree/master/vmware_view_zero-client_printing

  -John

• VMware View 4.5 supported Thin Clients

  Does anyone know if VMware maintains a list of clients from different vendors that support view 4.5? If this isn't the case, I would be happy to hear what you use thin clients.

  Thank you!

  There was once a pdf version, but it is now part of the HCL

  http://www.VMware.com/support/pubs/view_pubs.html

• Virtual Printing PCoIP clients Linux support?

  Does anyone know if virtual printing is supported on PCoIP when clients connecting from Linux based on?

  I work well with XP (or XPF) virtual printing clients who connect on PCoIP for view 4.5 XP VM.

  But does not work when connecting to the same virtual light based client Linux machine.  HP thinpro t5745.

  It works on thin client based on Linux, the connections to the VM even RDP Protocol.

  I have a HP LaserJet 2100 printer IP address definined network locally.  Works very well on the spot and when connecting from XP.

  Thank you

  This matrix is 1 1/2 years old, but I thinkit is still valid. There is no TP / Virtual printing support for the Linux Client.

  http://blogs.VMware.com/view/2009/06/view-thin-client-feature-matrix.html

  Kind regards

  Christoph

  Don't forget to assign points if this answer was helpful for you.

  Blog: http://www.thatsmyview.net/

• Use of thin client Sun Ray 3i with view 5

  Hello

  everything is almost in the title, after wipe UN "I'm sorry for that but I can't answer your question" with the support of SUN/ORACLE I turn to you.

  
  

  I pay project to use these beautiful thin client with view 5, I'd like to, so just know if someone knows how to deal with these beasts the. Because it is there not Windows os type or other embedded.

  I thought that it was doable, but comment on...

  
  

  Anyway thanks in advance!

  Hi Padua,

  I just threw a glance to discover compatibility matrix. A priori the couple discovers 5.x and Sun Ray 3i is well supportati ( http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vdm and you're looking for Oracle as the partner name).

  Then, you can find some info in the docs of Oracle (see Chapter 19):

  • http://docs.Oracle.com/CD/E25749_01/E25745/HTML/index.html

  Good luck!

  A +.

  Franck

• PCoIP sessions switching between thin clients

  Hi all

  I can't find all posts on this topic.

  I was wondering if it is possible to connect to a PCoIP session since a thin client (Wyse P20 / Dell FX100) then connect to the same session of a thin client different self-disconnection of the previous session. Thin clients could be side by side or on separate parts of the network / country.

  I'm under VMware View 5, with ESXi 5 backend.

  Kind regards

  Tim

  Sorry, I wasn't clear.

  The behavior you observe is the result to set this option to 'Yes' – he tells to ignore existing sessions and to establish a new view.

  If you want your existing users 'take over' connected sessions, you need to 'no '.

• Thin clients with view 4.5

  I was in the thin client compatibility guide, and I'm trying to decide what thin client to the demo. I would like to pcoip and find the Wyse P20 very attractive, although it has only usb 1.1

  Can someone make suggestions as to which clients you use with view 4.5?

  Currently, I have only a Wyse C10LE, which has no RDP and HP 5455

  I'd be willing to look at other companies, I wanted just to have an idea as to who are the most popular

  -MN

  We were extremely pleased with the Wyse P20. Like you we demo also had the HP T5545 and Wyse C10LE, and we were quite impressed by both.

  We thought that the Wyse R50LE was decent, but if you want the best experience then the P20 is the way to go.

• 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.

• Thin client HP t5135 VDI / configuration of VMWare View

  I tried to configure my t5135 to be a thin client VDI, but in vain. I'm looking for some idea where I can configure my VDI / VMWare View in this thin client. I tried several configs, but can't seem to get that it connects to my login server, I installed the windows client and it works fine.

  Thank you

  Matt

  Had the same problem with the t5145. HP said to allow the direct connection and it should work with vmview. However he has worked with the former client of 2.0 client just couldn't do SSO on. Technology of lvl 2 HP said that he could not do the tunneling using the broker.

• Thin clients connect not to view.

  Good so it's weird. I have a HP thin client (model hstnc-006-tc is important) sitting in my NOC. I point to my server connection. I can connect to the domain controller in the thin client, see the desktop that the user has rights, but when they connect he says "the login server Vew prepares the office" and sits there for about 30 seconds. After 30 seconds, or so he error with the following error: "this office is currently not available. Please, try to connect to this desktop computer later, or contact your system administrator. »

  The inside of the connection manager, I see my office as available. It is active, title and power. I get no error on the part of the present events. Now, my connection to the server and the server vcenter actually live on different networks. Can only cause a problem? It wasn't when I was testing it from my office. I was under the impression that the customer should not talk to vcenter, it is only necessary to connect with the login server, ports 443, 3389 and 4001 are open to the.

  Any thoughts?

  Thanks in advance.

  Please check you can test using the full domain name

  Agent to server connection computer

  Client computer to the server connection

  Client computer to the Agent computer

• Trolling video streaming using view 4.5 Client with PCoIP

  I have a strange problem that just started.  I don't know if it's my machines VMS, the new client or new thin clients that I use.  What happens when I go to watch a video on youtube say, video is very laggy, until I put my cursor on the video.  When I do this, it works fine?  I swapped just to use a desktop dell computer (I never noticed this before on the desktop) to a workstation from dell.  I've also recently updated to 4.5, so I don't know which is the problem.  Is there something I can do to fix the slow video?

  You can try to change the settings of the Pool.  Specific options for Adobe Flash...

• What zero or thin Client is the most popular? What piece of management?

  I think far in advance and do not want mixed marks in our environment. We rely on the movement of a large group of VDI (already have VDI in place, but expanding).

  1. why thin above zero... it's just that the user may have access offline (if something were to happen to VDI)?  Any advice would be appreciated.

  2 what Management Consoles use you - at the moment we have WDM (Wyse Device Manager), but I'm not sure that our future purchase will be produced Wyse.  We have the Teradici PCoIP Management Console - does this work for the most part zero and thin clients?

  These are two hiccups, that I was confronted.  I'd like to narrow down my choices of zero or thin, and what is the best way to manage them.

  We also use only customer zero for our environment from view.

  They are managed via the Teradici Management Console. As already said devices only with a Tera1 or Tera2-Chip (processor) are supported.

  We only use Wyse P20 and also new P25 units for our society.

  With the new Management Console (1.8.0 +) the old Tera1 and the new Tera2 are already supported.

  There is also a firmware combined for the two chips that can be used by this console.

  Establishment of autoconfig is also working with new clients.

  Here is a list of the most (if not all) zero customers who use a Tera-chip: http://www.teradici.com/where-to-buy/product-search-results.php?vendor_id=0&category_id=2&form_factor_id=0&vmware_ready=&keywords=&x=11&y=9

• Shado task does not connect to the Thin Client

  Trying to hide a T520 on HPDM 4.6SP4 thin client, when I run the task of shadow, I retrieve a VNC connection on the server HPDM and not the thin client. T520 thin clients are ThinPro 5. This happens on the T510 Smart thin clients zero Core as well. I'm guessing there's a conf file that may have a value defined by mistake, but didn't find it.

  Dear customer,

  Welcome and thanks for posting your query on the Forum from the HP Support

  Looks like you are facing difficulties regarding the task of the shadow copy in the HP Device Manager

  1 shadow task uses the built in VNC server for the HP Device Manager software

  2. If you have installed a separate VNC software on the server of HPDM, there could be a conflict

  3. also please check under "services.msc" to find out how many services VNC running concurrently

  4. If you find that several services VNC please disable those who is not necessary

  5. Please goto Add / Remove programs and uninstall VNC Viewer is installed separately

  Hope this helps, for other queries in response to the post and feel free to join us again
   
  * Click on the button white Thumbs Up on the right of say thank you *.
  Make it easier for others to find solutions by checking a response "accept as Solution" if it solves your problem.
   
  Thank you
  K N R K
  Although I am an employee of HP, I speak for myself and not for HP

• Choosing the thin client just for our solution! (health care)

  Hello community,

  I can't try to define the best thin client PCOIP solution so that I work at the hospital.

  We are currently working with Vmware view 4.5 with Oracle sunray thin clients/broker

  It works very well with smart card authentication, but we want to feature implend instead of RDP PCOIP

  and get rid of the sunray broker because he dousent enters our landscape.

  Now that we're about to go upscaling (from 100vm to 1000vms) as possible, we are looking for the right thin client

  We tried the new dell Fx130 & 170 with the dell Detos reference edition

  However, we feel its underdeveloped and it can not handle the Pre-os how smart card authentication

  customers current sunray are skillfully to (follow me desktop) and lacks a disconnect button.

  Ideally:

  1. We do not want a built-in windows machine since it's patching/security on the thin client
  2. It's a simple thin/zero client that we can manage a centralized management point.
  3. who has PCOIP functionality
  4. A biometric capability / card smartcard/proximity (if necessary with another agent of connection)
  5. and has a material disconnect as button
  6. Follow me / roaming Office

  Can someone help me in the forest of solutions and thin clients or push me in the right direction?

  Any help is appreciated!

  This can be done with the power button. Push, little time to disconnect it take longer to power off of NC