Windows xp works on VESA PC Thin Client eBox-2300

Similar Questions

• Cable virtual thin client for xp

  I have a virtual machine running Windows XP. I have a thin client, which must be copied using a crossover cable, connected to a XP Server. How can I do this with virtualization?

  Jumpered the value Network Adapter to the Virtual Machine and connect the cable to the Ethernet of the host card

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

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

• 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

• How to configure the mode of kiosh for thin clients on windows server 2008

  I have an eight Thin Clients who will use RDP to access (Terminal Server Services) Remote Desktop Services on a Microsoft Windows Server 2008 R2 Standard. I would like to set up a group of users for these Thin Clients to be in a mode Kiosh so that they have very limited capabilities, can not download and run anything, unable to save anything in the computer except on the desktop and when they log off and back on everything, they had disappeared because the mandatory profile is loaded again.

  I'll have another group that more access is needed.

  Kiosk.

  Post in the Windows Server Forums:
  http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer/

• 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

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

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

• 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

• HP Thin Client T5550: HPDM - sending of the zone settings

  Hello everyone, I have a huge issue with my HP Device Manager and I would appreciate your help.

  When I try to send to my HP Thin Client T5550 time zone settings, it is just the time zone of Dublin.

  It doesn't matter what time zone I send, it always comes back to the zone of Dublin.

  The only difference between the time zones on my HPDM and my thin client is UTC and GMT.

  On HPDM zone is defined as UTC, but on the thin client, it is GMT. I don't know if this could cause problems? And if so, how can I solve this?

  For your information, when I send the same zone to my HP Thin Client T520 settings everything works smoothly.

  I would be grateful for all the help I can get.

  I guess that we are talking about Windows CE on T5550. It is actually a known issue of HPDM, because Windows CE is thus more complete support of HPDM, this issue will not be fixed in a newer version of HPDM.

  I suggest that contact technical consultant for the extraordinary. Or if you know the order of change of time zone, you can try to change it through files & records task.

• Thin Client HP T510 printer questions

  So we have thin clients. We have a local default printer installed for the administrator who "invades" on the "Default user" profile (which is great, that's what must happen) when we try to install a network printer:

  1. We disable the write filter
  2. We disable the security for the user
  3. We install the printer network under the user's profile
  4. We invited domain administrator credentials.
  5. We enter the identification information and properly install/test the printer
  6. We restart and allow the connection of the user (automatic)
  7. The printer is there, but it says "access denied, unable to connect."

  Key information:

  1. These thin clients MUST have locally installed printers
  2. These thin clients are not on the field, they are the default WORKGROUP

  This seems like it should be easy to make it work, but I can't seem to find a solution and I have worked on it for over a week now. Thanks in advance.

  Solution:

  Put printer driver software on USB stick and install locally via the setup.exe.  Do not use the software in windows, for some reson he has a problem with striking pilots from the network.  Running the driver software installation file locally worked like a champ.

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

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