Zero Clients and view 5

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

• Zero Clients and Horizon discovers

  Hello

  We have a project to justice some of our users on zero customers.  Does anyone know what version of view Horizon I need to support zero customers?  Is pretty Standard, or do you need advanced or same company?

  Kind regards

  M.

  There is no minimum version required. Any version of view Horizon will support end users, so there is a customer support for her.

• Problems with audio/video streaming with USB devices on zero clients

  Hello:
  We are using view 6.1.1 in our environment and problems getting audio/video streaming to work well with the USB headsets, with zero customers.  Helmets are Jabra Link 360 and customers zero Samsung NC241.  Helmets are used as well for the phones to Jabber and also as audio device by default.   We started with the audio driver Teradici and everything seemed to work well, except that users could not answer calls on the headset itself with the button on the headset.  They were able to answer the calls of Windows though and the part worked fine.  In order to get the physical button to work, we had to first fill the USB receiver they use on the zero clients so that Windows will see as the device Jabra 360 and not the audio device Teradici.  Then we had the EHCI USB mode on them as well, and after that he started to work very well.  However, the helmets also serve as the audio device main as well as the communication (phone) device, with audio streaming continuously throughout the day.  With the current configuration, audio streaming will cut in and out during the day, and audio/video is not always to stay in either phase.

  I also applied the registry in this KB hack, VMware KB: improvement in audio quality when you use speakers or USB headsets with a desktop VMware view Horizon 5.2 , which helped clear up Crackle that we originally with the part phone headsets.  But there is still the issue of streaming audio.

  I wonder if the effectiveness of the bridging USB is not as effective and also is there a way to make this work better?  I read that the use of the pilot Teradici is supposed to help with audio/video problems, but do not know how that can be applied to USB devices as we use.  I've been reading upward on Teradici audio/video settings, but do not know where to go from there.  I was hoping that there are some best practices to use USB headsets with a view, but so far I'm not finding anything useful.

  For any help or suggestion would be greatly appreciated.  Thanks in advance.

  We were finally getting help by the people of Cisco after validation in the here and even open a support ticket with VMware, which was open for more than a month without will.  Where others try to implement similar, here are our findings:

  • Zero clients combine traffic USB and PCoIP.  It is not good when there is a lot of audio/video/USB traffic, especially the USB headsets that also carry audio softphone.  In our case, the USB traffic was so dense that it was causing audio and video become troubled and freeze and eventually cause the pcoip_server service to break in the virtual machine itself and cause the client disconnect.  The fix?  Don't use customers zero with USB phones software, they are not just designed for this type of solution.
  • Thin clients are much better designed for USB softphones.  In our case, we used the Cisco VXME client, which is the method of support for the use of Windows thin clients with the client of the Horizon.  There is integration between the two products that isolates the VOIP traffic out of the virtual machine and keeps it local on the client itself.  Regular audio and video traffic still go through the virtual machine using Teradici or VMware RTAV driver.

  Hope this helps others who may run this question.  One thing we did not try was a wired headset using the AV sockets on the zero client and Teradici audio driver.  This can work, but our needs here were the headphones must be bluetooth, so we were forced to stick with USB.

• Check the USB scanner does not not from zero client

  I installed a scanner control Epson TM-S1000, who works a clone if the device is connected directly to the ESX host and attached via vSphere virtual desktop, but does not work if hooked up on the zero client.  I tried a variety of measures to solve this problem without any results.  It's confusing because I do not understand why the OS (Win 7) would see these quite different according to where the USB is connected.  Windows recognizes the device when it is connected through the client, but it does not work properly.  I opened a ticket with Teradici as well.

  Originally, why the OS would react differently to a USB device connected to the host against zero client; and what I can do about it?

  Hello

  can you tell me what version of the agent of the view, you connect to?

  We have seen several problems with Epson devices (including this specific control scanner). Problem is actually in the driver epson themselves and it starts in a sequence that is not consistent with the usb specifications. Thus, it is not redirected properly and actually ends up in a blocked State.

  HOWEVER, the good news is that there is a registry key that you can define what must do the work;

  on the vm agent defined the following key:

  HKLM\Software\VMware, Inc. \VMware VDM\USB\Vid_04b8 & Pid_0202\DeviceFlags = DWORD: 0x1000

  Please note that Im sure the Vid/Pid of the TM-S1000 is Vid = 04 b 8 Pid = 0202 but please check that and replace them with the good vid pid for your device if its different;

  Please see VMware KB: Epson printers are block in VMware View Horizon for more details.

  In my view, that this registry key (solution) is available in the Agents v5.2.1 and later view.

  see you soon

  peterB

• Zero clients - AutoConnect printers via the strategy?

  I can't find a definitive answer to my question.

  If I turn on the group policy 'AutoConnect map additional printer for VMware View' in my domain name AD and apply to my pool active Persona, and then add a printer assigned to a particular user, is there any problem if the user connects a Teradici function Zero Client?

  According to the document found in:

  http://communities.VMware.com/servlet/JiveServlet/previewBody/14416-102-6-17439/location%20Based%20Printing%20on%20A%20Zero%20Client.PDF

  It refers to "Disabling channels to see virtual offices" to operate printing according to the location on the zero Clients that I did not.  However, in my pool of test, using the settings below it seems to work with a zero customer very well in preliminary trials.  I guess it's because I'm affecting the printer based on the user name and not by IP address, MAC address, or name of the client, so no information is really necessary on the zero client properly said.

  

  If I assign printers via the username as stated above, if it works reliable ok with zero clients, and is there any potential problem with Group Policy "AutoConnect card additional printer for VMware View" turned on with a zero customer if I as shown in the screenshot?

  We are a mixed HP Windows Embedded thin client and Teradici based zero client environment and I want to deal with all the identical machines in my Persona pool so I can get rid of some persistent desktops and use a floating pool of Persona based instead.  I don't want to cause problems with my zero client users if I activate my pool of production strategy.

  We must remove this document. It is inaccurate and provides information not supported by VMware. At the time where it has been committed we had embedded a feature called printing according to the location. The original version did not work with Clients from scratch from Teradici.

  This doc has provided a way to make it work, but the solution breaks many other components. Shortly after that it has been released Teradici, updated their Firmware to fix the problem.

  You should be fine without any problem.

  WP

• IPv6 and view

  Hi all

  Anyone know if the view is compatible with IPv6?

  IPv6 is a good response to massive infrastructure VDI with frequent updating, recompose, etc...

  I mean, can we use a complete solution of IPv6 including?

  • Connection brokers
    
  • View customer (Zero customer)
    
  • View agent (Windows 7)
    

  I know that with Teradici 3.5 firmware, IPv6 is supported on the zero client, and of course on Windows 7 this is also the case.

  I can barely find information on the rest of the components and especially the broker for connections.

  Thank you

  Eric

  
  
  

  Sorry, cannot discuss road maps.

  Track down the local VMware team and ask them a NDA submission.

  Linjo

• 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

• PCoIP zero client does not display an Horizon view Client user of the window for one (and only one)

  The zero client is a Samsung NC241 via Teradici Tera 2. My user has 3 virtual workstations assigned;  Current SOE with WinXP, a specific COMPUTER WinXP and a test for the upcoming Win7. When I connect the customer to see I'm automatically redirected to the WinXP for HER, without going through the window that lists usually all available virtual PC. This happens on all terminals, I tried. Other users, even if you connect to the same terminal, are given the option to select a virtual PC, even if they have the choice of a!

  I have checked the setting for the PC virtual in the Teradici PCoIP Management Console and also the settings of the user under the Horizon view VMware administrator but cannot find where my configurations user and desktop are different from those that work "correctly".

  Is someone able to propose what I'm looking for?

  TIA

  Thanks, Stu, for your input.

  I arrived on the solution after you follow through with your suggestion above. I used the client on a Windows PC, then after that record on I clicked on 'Options' in the bar of VMwareView Client session and erased the text is 'auto connect to this office. We have the option 'Enable automatic reconnection' set to false, so I'm not sure why that followed me.

  But the good news is that it worked!

• PCoIP View Client and built-in customer Teradici

  Just a quick question.

  Is the client for Windows (which contains an option PCoIP) identical using the built-in Teradici PCoIP customer?

  Specifically, if I conducted tests using view Client on Windows XP, I can be reasonably certain that if I went with a TC5 DevonIT or Dell FX100 the embedded Teradici PCoIP would operate the same?

  Thank you

  There are two ways to render the elements of a composition of the bureau. On the host side and rendered client-side rendering. We can say that those, Flash, WMV, H.264, MPEG etc are more demanding and difficult to make and deliver across a network components. On a PC, when you play this type of content, you will notice the CPU or spikes runs at high usage during playback that is working to decode and display the video.

  With the rendering side host you must have a VERY good encoder to manage videos and do it as efficiently as possible through a network. Historically, this has been a problem for server based computing solutions.

  Rendered on the client side or ROR then renders the native content on the client side. Graphics commands or content are sent between the host and the client, and the client is rendering and the display of the content. With video overlays use then... think of it as your weather man standing in front of a green screen.

  He has pro on and con everyone.

  ROR requires customer support capacity, has CODECS on the client. It also requires that the drive supports the media type. The advantage is that it requires less host resources, because the client is used. The disadvantages are the limited player support, management more on the client and the limited media are supported.

  Made on the host side just works. Any CODEC will work, any player will work and any client can be used. The benefits are, any client can be used, less complexity, media format more broad support, assistance to larger players, less management on the client endpoint. The downside is that it requires more resources on the side of the host which can lead to the consolidation of weak reports how often media is used.

  VMware View with PCoIP supports rendering both MMR and accelerate

  Customer discovered with PCoIP and RDP for windows supports ROR

  Customer discovered with PCoIP and RDP for Linux supports the ROR with RDP and support for ROR with PCoIP is coming

  The two clients support rendering with PCoIP host-side. If the right player, media, client and guest OS combination serves ROR is tried in the first place, if this fails host-side rendering is used.

  Client PCoIP zero do not support ROR so rendering on the host side is used.

  A list of the types of media supported and players are in the view Administrator Guide.

  WP

• VMware VIew 6 (PCOIP): Windows Client and web browser connects, Android and Ubuntu - don't

  Hello colleagues!

  VMware Horizon Client 3.4.0 build-2769709

  VMware View 6.1.1 construction-2769403

  VMware vSphere 6.0.0 2776511

  That's what's wrong: used SecurityServer and connecting to the server. External connection - via a router. When it is connected to a vmware PCOIP Protocol (Internet) outside of the view with a Windows client and a web browser, it works fine. But when connecting from Android or Linux (Ubuntu 14) load the desktop does not occur. Android immediately displays the message 'connection to server lost', Ubuntu delivers all messages - I'll be back on the screen to select a pool table.

  Which connection via MS RDP connection protocol is correctly to all customers.

  In the settings ConnectionServer in PCOIP Security Gateway set up the external address of the router.

  Redirect them router ports:

  -TCP 80,443,8443,4172,32111

  -UDP 4172,32111

  Any ideas?

  In security settings server in 'URL of PCOIP' was FQDN, but it must be the IP address.

• View of the horizon - Tera1 zero clients

  I know Tera1 Zero Clients are not supported with view Horizon 6.1, but I was wondering if someone use them anyway?

  Not happy to learn that they are not supported, that's for sure

  They are not supported, but they are still working with existing features.

  10ZiG offers redemption Tera1 devices from any manufacturer: http://www.pages03.net/10zig/terra1/

• See 5.2 and view Agent v5.1.2 (Win v7)

  Hello

  I'm about to upgrade to v5.1.2 v5.2 view.  If I improve View Composer and view connection Server v5.2, will be my VM v5.1.2 Agent view running always not connect to one zero Client or no one will be able to connect until the officers are also updated to v5.2?  I've read the documentation, and he says "only during the upgrade", so I don't know exactly what this means.  I'm running the linked clones.

  Thank you.

  I did this same bet level and always have customers connected and running on the older agent.  Eventually you want to redial with the agent of 5.2, but it will work.

• Reference Dell Wyse Zero client P25

  Anyone know if I can run Redhat 5 on a Dell Wyse zero client? Assuming that vmware view is the redhat image management software. This is not a thin client and I do not think that customer to view gets intalled on zero clients.

  V/R

  There are many parts to the VMware View solution. The main parts, that you ask the subject are:

  Client access device: what do you use to access your desktop remotely hosted VDI and RDSH

  The Office of VDI and RDSH host: the Virtual Machine you remote in and work (that is displayed to the customer)

  Zero clients are a feature of client access that are VMware Ready Certified for VMware View and appear on the VMware View Client HCL. A zero client can be used to access your virtual desktop VMware View with PCoIP such as the Protocol of distance communication.

  We also provide the customers of VMware View software running on a wide variety of client devices and operating systems such as Linux Distros, installs Thin Clients with custom Linux for our client partners customers Windows, OS X, iOS and Android customers. Our open client is just a client for devices based on Linux, typically used by our thin client partners to create customers for their specific needs. It's just the customer that allows you to access your remote desktop of VDI.

  The only host or remote VDI desktop OS / OS RDSH we support connection from any device using RDP client access or PCoIP is Windows. We do not offer an offering to connect to desktop computers based on Linux. Our base platform vSphere does support Linux servers / hosts (without Linux Desktop OSs are listed) so you might use alternative office as connectivity and vSphere allows to virtualize your Linux virtual machines.

  WP

• Thin/zero client beyond 3 G

  We need connect the thin client of 20-30 on 3G.

  We use vSphere5 + view 5.

  Can someone give me advice what thin clients are good for that?

  Also, there are about 20 thin client for office LAN. I want to take only one or two kind of thin and zero clients.

  Thank you

  I'd love for you to try the zero Clients, I used to work at Teradici, and I'm a big fan of them.  I don't think that any fan of Zero customer recommend their use in your use case.  As Tim noted that they do not support caching on the side sex (and other features that are harder to explain that also decrease the bandwidth).

  So far HP vs Wyse goes, it is not really important to me, just look at the speed of the processor, and like I said I recommend devices based on Windows.  Not because I don't like not (I didn't!), but because they support things better (of THE USB devices).

  Gunnar