HP T520 Flexible Thin Client: Flash BIOS on customer T520 light with USB

Similar Questions

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

• 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

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

• 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 t510 - printer redirect on windows server 2003

  Hi all

  just bought 4 T510 Flexible thin client. I have attached USB printer (Brother HL-2040 or a Brother HL-2130), but it does not redirect on the RDP session.

  I tried everything, to my knowledge, but without success. In the options of the Windows driver, I wrote EXACTLY the side server name of the printer (which is actually the same name identified by the customer).

  I noticed in the information system that the RDP version is rdp is 1.6.0 - 1.45...

  I thank in advance.

  I have the same problem but I managed to solve.
  I bought 10 of these T510 terminals, but with the same result on 3 different Windows Server 2008 R2 Terminal different (updated to the latest patch).
  Only one of these terminals sold the year before worked and so I checked the version of the software.
  By installing the old version of the terminals intelligent Zero Client the new T510 work with my printer in the Terminal Server session.
  New version does not work!

  I tried everything... this add features such as storage of the password, the support for the speed, etc... etc..., but the printer no longer works!
  I think that the change in the Protocol version RPD to give me problems.
  Now I have one here in the office with which I am trying to understand if I can solve the problem with the latest versions of the software that I could use.
  We install the Smart Core zero Image Z6X41019 Rev 1 (March 7, 2012) and it should work.
  PS, You must put the printer in T510 in the driver entry not working also the exact name of the driver that you see in Windows.

• 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

• Two monitors on the HP T5545 Thin Client

  I've looked everywhere and I can't find an answer. Did somebody get two monitors working with view 4.5 on a HP t4454 thin client?

  I have no problem with the client installed on a desktop computer, but when it connects via a thin client display only on a single monitor. We're explains View 4.5 and I really need this to work to justify making the leap to virtual offices for our users.

  I've updated the Thin Client at the last image and service packs.

  Any advice would be greatly appreciated!

  There should be a drop-down list display when you go to choose your available desktop, allowing you to select "all monitors". I just checked our units to confirm.

  ____________

  blog.eeg3.net | Useful links related to VMware

  If you have found this device or any other post useful, please consider the use of buttons useful/correct for award points.

• 3.1 client for Linux thin clients

  Its great that you can do all this with light customer Windows, but what of us, guys who have Linux thin clients who don't get to play with all these cool features?

  We release publicly on the Linux client sales literature because it goes directly to the partners of thin client.

  WP

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

• T520: Thin Client T520 device name

  How can you find the device for customer ID light t520 as we tried it and could not find this info. With out I don't then add it to the Device Manager 4.6 which we are currently in place but now need to capture an image, but with the device ID, we cannot add the thin cleint

  Just for reference, the name of the device's MAC address, I ended up manaually add the device to the Device Manager HP by configuring the gateway device HP on the thin client Manager real it self and then finally showed the Device Manager and the device being indicated id is the MAC address.

• Thin Client CA 10

  No doubt this ad in evil, spot, but could not find the right place to post this.  Admin please move this article to the right place.  I volunteer with a non-profit and is currently trying to help with some tasks that they work.  I had some experience with TC.  I thought we could get a lab of the computer market quickly at the lowest cost.  So I found of these CA10 on ebay.  BL-01-CB, they are ok, I can get into the bios, but it seems that the owner has set the password in the software.  I can't change the settings.  How can I do to solve this.  Is there anyway to reset it to factory settings?  If I flash where can I find procedures and for the flash image with.  Your help will be appreciated.  Thank you.

  Hello ttiger211996,

  When you disconnect a computer some of the capacitors may still have a charge that can make things difficult.

  Unplug the computer and leave it on for a while for logistics I hope that all of the capacitors. Once he has to rest for a little out the CMOS battery for at least 5 minutes.

  Reconnect everything and see if the password still exists.

  A user in this forum thread ran into a similar problem of semi

  Thin Client T5000 series password reset

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

• 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