Thin client HP t5740 + TravelScan 662

Similar Questions

• client light t5740 - agent HPDM

  Hello

  I was wondering if someone could remember where HPDM agent (for a thin client of t5740), specifically 4.3

  device recently returned repaired with HPDM version 4.5 HP, however this doesn't seem to be compatible with the version of HPDM (4.3) on the server.

  search for the error code: 14000052 gave me this idea, but others thoughts most welcome.

  Thank you.

  turns out that the bios of the thin client is not able to boot from a USB pendrive of 64 GB!

  a 2 GB key has worked — first time, no problem!

  moral of the story is - keep these keys GB 1 & 2... they can become useful at some point.

  see you soon

• Imaging of HP Thin client tool

  Hello

  My apologies if this is a repost and has been processed before

  t5740 trying to install "Thin clients microsoft windows embedded standard image", specifically a version with an older version of the agent HPDM, however same issue on all versions.

  currently have windows embedded standard 2009 5.1.2600

  in other words, unable to use the 'thin client HP imaging tool.

  the 'usb format' or 'deployment' options work.

  When booting from newly created usb key, received the "error loading operating system" on the light client device.

  am I missing something really really obvious!

  the USB is fine - is it specific to a file that could be a problem, I wonder?

  ...

  Thanks for any idea!

  got Ahold of the image of the HP website...

  However, nothing wrong with the image - curiously was to do with the bios not recognize a 64 GB usb key!

  an old 2 GB key worked well.

  keep these old 1 & 2 GB handy glue!

  Bravo nevertheless!

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

• HP t620 Flexible Thin Client: Windows 10 IoT Ent. Client light-load Multi Touch

  Customers light t620 (Std/MORE) running 'Windows 10 IoT Enterprise for Thin Clients' supported multi touch? Or alone only?

  Having a hard time finding a definitive answer online.

  Thank you

  The answer is Yes.

  See Page 5... http://WWW8.HP.com/h20195/v2/GetPDF.aspx/c04312126.PDF

  "Smooth, immersive experience with technologies like advanced multi-touch and Windows® 10 applications"

  -Keith

• Thin Client T520: Hp Thin Client Test without account 'user '.

  Hello

  My problem is that I created a new account user without administrative privileges for a long time and yesterday, I deleted the user account original (I still have the administrator and the new), but the customer never resumed. I can see the mouse, but it does not start.

  I have the Lightweight Client T520 with Windows 8.

  According to the message that you have posted, I wish to confirm that the operating system could be damaged and need to re - install the operating system on the workstation again to make it work

  This Thin Client device comes with various types of operating system by default, as shown below:

  

  Here is the link to this page: http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=6875922 & lang = to & cc = us

  I don't see Windows 8 (32 bit) operating system on the HP Support Site's list

  Hope this helps, for other queries in response to the post and feel free to join us again

  * Click on the white button on the right to say thank you Thumbs Up *.

  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

• 4.7 HP Device Manager: HPDM finding Thin Clients

  I'm trying to implement HP Device Manager 4.7 on a newly configured Windows 2012 R2 server.

  I am replacing a Server 2008 R2, where HP Device Manager works perfectly on our network.  In fact, if I uninstall HPDM on the new server and reinstall it on Server 2008 R2 I can always access all thin clients.

  The only difference I see in the facilities which is for some reason any gateway in HPDM is not a subnet mask.  Research of the device are not lacking, they don't sell anything or simply continue indefinitely until I have Cancel.

  Any help would be great.  Thanks in advance.

  Just to confirm: you did turn with HPDM 4.7 on Server 2008 R2 successfully, but not the right to 2012 R2 server?

  Is your Windows 2012 R2 server with more than 1 NIC card? Could you please assign a specific NIC loca in the Gateway Configuration window and see if that fixes the problem?

  Otherwise the logging level value please DEBUG and post the gateway.log when start HPDM Gateway

• 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

• Thin Client T5550: Central management program

  Operating system: Microsoft Windows CE 6.0

  Hello everyone. A few days ago, I asked a question on the HP Device Manager and the answer I got was that HPDM can't stand Windows CE 6.0.

  And given that HP can't stand my thin client operating system, it is unnecessary for me to sit for hours to learn how to manage the HPDM.

  Question:

  Are there other programs for central management AS HPDM can I use to manage my thin clients of?

  Best regards

  Linus.

  In terms of Thin Client, HPDM is the single management tool published by HP.

  In your case, are all of your thin clients running with Windows CE? If so, you can use the old version of HPDM (4.4.3) who fully support this.

  If your thinclients are with different operating systems, it is best to contact the special support team.