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.

Tags: VMware

Similar Questions

  • PCoIP Thin Clients with view 4.6 external?

    I can't seem to find confirmation of this anywhere, but if upgrade us to 4.6 view and configure security for external access PCoIP server, can we send home with a Wyse P20 or Samsung NC240 users so it works now with PCoIP and without VPN?  It would be huge for us because we currently send a full PC with our teleworkers House and many prefer something simple.  Thank you!

    Yes as long as the security pcoip gateway is configured, the P20 and even the view for ipad will connect and has PCOIP feature enabled. It's as simple as that.

  • 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
  • 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):

    Good luck!

    A +.

    Franck

  • Thin Client connection problem

    Hi Folks,

    I have a issue to solve with some new thin client (Devon IT TC2B)and I really need some help

    When I use the view client from any PC or from my Mac, everything works perfect!

    But I a use my new Thin Client with the View Client embedded I have the following error: "The secure connection to the View Server has unexpectedly disconnected.

    Any ideas? If anyone can help me I'd really appreciate it!

    Thanks in advance!

    Randy C.

    PS: I have attached a screenshoot from my mistake of thin client.

    I see 2 possibilities:
    -A network issue affecting the Thin Clients.  Settings DNS, Firewall, etc.
    -The Client of the view needs to be refreshed on Thin Clients.

    Best regards

    Patricio Cerda

  • Not realistic Win7 with View Composer?

    If View Composer creates clones based on a snapshot, but does not change the SID or (especially) the CMID.

    KMS is the only practical solution in VDI for the linked clones license.

    Without changing the CMID, KMS will not work.

    http://blogs.technet.com/ASKCORE/archive/2009/10/16/KMS-host-client-count-not-increasing-due-to-duplicate-CMID-s.aspx

    So, Win7 with linked clones will not be possible, or (if you use a clumsy method to change the CMID) supported by Microsoft.

    Does anyone know if I jump thorugh the hoops to get the number of my KMS above 25 will be KMS activates the CMID even again and again?

    Anyway to change View Composer sysprep to include / generalize?

    Regarding the last comment, thin clients with VIEW4/PCoIP press

    the HCL (including various thin clients HP) have generally been certified

    hardware and software meeting required set out under VMWare

    light client certification program.

    With the exception of customers zero in the HCL (which already)

    a native support of PCoIP via a TERA processor), we should be able to

    install a client VIEW of any one and you connect via the PCoIP Protocol.

    I hope that clarifies.

    Ian

  • Thin client for virtual desktop

    This Thin Client would agree to operate the virtual office?

    HP GY227AT; Thin client HP Compaq t5730 - Tower - 1 x Sempron 2100 + / 1 GHz - RAM 1 GB - no HDD - Radeon X 1250 - Gigabit Ethernet - Win XP Embedded

    What is the minimum/recommended specification for a thin Client Solution typical?

    Rgds,

    Jamie

    Welcome to the Forums - if you are referring you can use this Thin Client with VMware View, the answer is Yes according to the compatibility guide - http://www.vmware.com/resources/compatibility/search.php?action=base&deviceCategory=vdm

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • HPDM: HPDM can't see any of my thin clients

    A few months ago, I set up a server HPDM on Win 2012r2 and light HP 12, mainly mt245 clients. I could see all the thin clients with HPDM, I even used it for the Image of each of them.

    Yesterday, I went to add a new abd mt245 the image. All TCs went from HPDM and it does not find it again. I tried to walk to the beach. I tried to manually add as well as at the foot of the range of the exact IP that the TC has to say things. I ping the TC from the server and vice versa.

    The Windows Firewall is turned off completely.

    Any thoughts?

    Thank you

    Travis

    Well. I thought about it. I forgot to click on the name of the gateway on the left. Stupid sound is not automatically select one on its own.

    Travis

  • Replace the Win7 login with view Client screen

    Howdy

    I don't know yet if it's possible, but I heard that you can replace the login screen of Windows XP with the Client of the view, so that when the computer/Thin Client starts, the first thing you see is a connection for the customer to view, and by entering the credentials, you are connected to the virtual computer.  Loging out of the virtual machine that takes back you to the login screen ' display/computer customer '.

    Is there something similar to this in Windows 7?

    I would like a way for my users can connect to a virtual machine as quickly and easily to these thin clients as posible, making them more in the terminals that real thin clients.

    Standard t5745, embeded Windows 7 HP thin client, view 3.5 (eeeww, we modernize quickly.)

    Thanks everyone, any ideas or suggestions are welcome

    Torstein II beginning Sir

    Matte Gud velsigne deg worked!

    Yep, Gina has been replaced by another system of credential called ICredentialProvider

    It seems very difficult (and not well documented), but I found a few sources of Microsoft for you:

    http://msdn.Microsoft.com/en-us/magazine/cc163489.aspx

    and

    http://msdn.Microsoft.com/en-us/library/bb776042%28V=vs.85%29.aspx

    Hope that it will help, but requires programming with the API. And, please, don't forget to score.

    See you soon

  • 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

  • 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 Client PC with Windows Embedded Standard 7/8 requirements?

    Dear support,

    Could you help us do I need a VDA or SA if we use

    Thin client, PC with Windows Embedded Standard 7/8?

    Thank you.

    Hello

    I suggest you to post the question on the TechNet Support link below. It is the team dedicated to the issue that you are facing.

    http://social.technet.Microsoft.com/forums/Windows/en-us/home?Forum=w7itpronetworking&filter=AllTypes&sort=lastpostdesc

    Do not hesitate to write us if you have problems with Windows

  • Windows XP SP3 with view Client 5.1: unable to connect: discovers the connection connection to the server has failed

    Hi guys,.

    I need help.  I have a problem with my opinion of Client on a Windows XP SP3 computer.  When I click on connect, I get the following message immediately:

    "Failed to connect to the view connection server. Verify that the server connection mode address and network settings are correct. »

    A few details:

    My client's IP address is on the same subnet as the view connection server

    There is no firewall and DNS solves the login server see very well.  Here is the output of my customer's orders

    C:\ > nslookup X.X.X.172

    < resolves very well >

    C:\ > nslookup dd - view.viewdomain.com

    < resolves very well >

    C:\ > nslookup dd-notice

    < resolves very well >

    C:\ > tracert X.X.X.172

    < works great >

    If I open a browser on the XP workstation which is a failure, I can go to https://dd-view.viewdomain.com.  It displays the page that I need to connect with View Client. What do I think, so this should check the connectivity between the two.

    I've seen customer 5.1.0 build-704644 installed on my Windows XP SP3 client computer

    My connection to the server is running 5.1.1 build-799444 and is configured with a pool of offices 25 clone related with SSL active

    LAST IMPORTANT NOTE: I have the same version of the Client view (5.1.0 build-704644) installed on another Windows 7 workstation on the same subnet and it connects to my view connection server office pool very well.

    I tried to install the three versions of the customer view of this system of XP SP3 including the latest version, when the connection after installation, they all fail the same way. My body needs to function. The client machines can not move to something more recent to Windows XP SP3 because I am not the administrator for them.

    Any ideas?  Is this a bug or is Windows XP SP3 just not supported with view 5.1?

    VR,

    Brian Whyte

    Political of McAffee HBSS blocked 443 attempts out of the customer to view.

    The difference is that the Windows 7 machine that worked was becoming another policy HBSS applied to what was not blocking attempts.

  • 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

  • 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

Maybe you are looking for