Profilinh ISE and Thin Clients

Similar Questions

• BTA - how to add thick and Thin Clients to User Mode

  In BTA, when I build a single Java Client scenario appears as User Mode - I need heavy Client and Thin Client - how do I add those?

  Thick and customer light will be available only if you have built your scripts using FOT. If you have saved your only option in OpenScript client is Java.

• 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

• 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

• 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

• 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

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

• Wyse thin client: autostart and full screen

  I'm testing a wyse computer V10 Thinclient (6.3.0_12) with our Infrastructure perspective (3.0.1 build-142034). There are two problems I couldn't solve:

  • How to configure the session of 'full screen '? I tried fullscreen = yes in the wnos.ini, but this makes no difference, I still see the wyse "taskbar" on the bottom.

  • How to configure a start of the connection. Now I see my inventory on the desktop to wyse as icons, but I want one of them starts automatically.

  I found some discussions on similar problems, but no resolution.

  Daniel

  If you follow one of these two steps the WYSE thin client will inherent parameters. He does not receive the settings for connections from ini files. He gets the parameters of the broker using our API.  There is nothing there, on the next, WYSE thin client make sure that the connection broker View Manager is configured, which can be done manually, using DHCP options or management of WYSE software. If this is the case, the devices wil inherent of the user or the GPO settings when using logs, launch your default desktop, full-screen if configured.

  You have the broker actually part, which is why the option full screen is grayed out, it has recived the default settings of the broker.

  WP

• HP Thin Client running Windows Embedded don't profile with attributes DHCP

  My company has a large population of HP Thin Clients that are not attached to our AD domain and therefore cannot do dot1x because they have no certificates.

  We decided to do the profiling for these devices. We present a few attributes, two of these DHCP attributes.

  About 90% of our profile of thin clients, as expected, but the other 10% will refuse to work. We need to statically assign them to a group of identity to authenticate properly.

  A lot of troubleshooting reduced us to query DHCP the thin client sent was not received by the strategy node. A TAC engineer looked over the config switch, IP helper address configuration and said that everything seems to be configured correctly.

  The only explanation is that it seems that these specific thin clients were not finishing the DHCP process before reassigned switch the VLAN of the port. So when the dhcp request has been sent, the thin client was already in our vlan "invited" who does not dhcp to the ISE.

  It's very strange, because we have so many thin clients that works properly. It's only a handful that do not. We have not been able to further refine to something specific. They are running Windows Embedded Standard 7 and a majority of them are HP t5740. I don't see Windows or HP updates available for these units and not sure if there are any registry hacks available to expedite the DHCP process.

  Has anyone ever come across something similar to this?

  It's pretty obvious to me, the end point isn't you get profiled before there was authenticted, which means that you do not correspond to the profiling conditions defined in rules 6 and 7, which means it will match the rule 11 (I think, having not seen your real rules). What I expected this, is that endpoint gets profiled, if ISE receives the attributes of this endpoint via dhcp e.g. forwarding help. Then, what should happen is, that it should issue a certificate of authenticity to the switch, which will lead to the passage to be re - authenticate this ending point, which now must have customization attributes you are trying to match. However if the DHCP packet never reaches ise, it won't work. That's why I think you should do a trace of package on the ise server, to see if the packets actually reach ise. If they don't you will probably need to find another way to profile, or activate dhcp for assistance on your guest virtual local network. Have you looked at the attributes of endpoint maybe after 30 seconds? They change?

• flexible thin client T520: T520 Thin Client, how can I join a domain?

  I need to put my thin clients on the domain.

  Do not click no right, no "system" in the control panel... How to loosen things up I can do a basic administration?

  Not quite what I needed.

  I am logged on as administrator

  There is no 'System' icon in "All Control Panel items" to interact with.

  in the Explorer, 'Computer' is not right clickable, so there is no contextual menu from the drop-down list select 'properties '.

  NETDom is not a valid command of the high - command prompt = yes.

  Is what I found to work through experimentation;

  From a command prompt, type "explorer".

  This opens a window of the Explorer, which lists the 'C' and 'RAMDrive.

  (Just by clicking on the start menu, and the computer in the conventional way, shows that "RAMDrive").

  From there you can right click on "Computer" and put in place the familiar 'Control Panel>>System Control Panel items'

  "Then it's the usual"edit parameters"in working to change group settings" area.

• 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

• Thin Client T5000 series password reset

  Hello, I bought a few days there are some thin clients to someone.

  These has always his password to get into the bios.

  All thins are T5000 series.

  Dous anyone know how to remove this password? / or clear all default settings?

  -J' looked for a reset jumper, but did not. One jumper is near the audio output, but I guess that's not what I'm looking for.

  -removed battery CMOS for a few minutes, did not help (maybe I should consider longer?)

  Thanks in advance,

  Drosaert S.

  Thanks Hanspuppa, that worked.

  Suddenly, I realized that, as you say, some capacitors may still have some fees top just after their closure.

  So I left the Jules Destrooper unplugged for a whole night, and after that I removed the CMOS battary for 1 hour. That's all.

  Thanks for your help...

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

• T610: thin client, multi-imaging platform

  Hi all

  IV ' e hoping to put this in the right place and someone can help or point me in the right direction.

  I'm looking for information on Thin Clients and Device Manager (HPDM), specifically on best practices on building and image capture, cross-platform and imaging would be advantageous.

  I am currently using HPDM Imaging for my thin clients t5470 and t5470e, t610, t620.

  I'm looking for a few docuemntation on recommended Configuration of HP for Imaging. is it to make a "gold" image or it can be pre-determined by HPDM like Microsofts SCCM or WDT?
  
  It would be fantastic if I could get it down to a single Image of WES7 for most of my Thin Clients if possible.

  Thanks in advance.
  J

  HPDM provides no functionality of creating an image, tt just do capture and deploy.

  The factory image include all drivers are built by HP R & D WES, there should be no one who can help you, but as far as I know there is no document to save the steps in detail. I suggest that you raise a ticket to impact to HP for help.

  MDT can not be used to deploy the image provided by HP. When building the image, no matter it is an original image or Thinupdate captured image, HP has done little customization in/after imaging process. I don't think that MDT can identify and carry out even these customizations.