![]() ![]() Microsoft Windows Embedded Standard 2009 (WES) and Windows XP Embedded (XPe) Quick. INSTALL XP ON HP COMPAQ T5000 THIN DOWNLOADChange Connection Method to 'Web Browser' View online or download Hp T5630w - Compaq Thin Client Manual.Right-click your Licensing Server name select Properties.I'm pasting it here, slightly edited, for reference, but the credit goes to EricWy: There's also a proposed solution that involves deleting some registry values from under the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM" registry key that some reported success with. Microsoft support did not offer any further assistance other than to go to the thin client vendor." That's pretty disappointing if it's true. Hotkey: Automatic log on to User is the default for the XPe based terminals. User-specific settings and configuration parameters must be reapplied after the firmware is replaced. Anleirungen, Treiber und Dienstprogramme gibt es bei HP. To automatically reset an XPe client, reflash the firmware. Welches XP wurde nun installiert HP Compaq liferte dieses Ding mit XP-embedet aus. There's a disheartening statement in that thread: "The official word from Microsoft is 2008R2 RDS does not support clients below 6.0. Hotkey: XPe-based thin clients do not have specific reset procedures. Their devices worked properly before the grace period expired. ![]() INSTALL XP ON HP COMPAQ T5000 THIN LICENSEThe users there seem to have tied the problems to activating the license server. This long thread on is filled with users having a similar experience. I saw something similar with a couple Wyse thin clients but rather than troubleshoot the issue the Customer just opted to replace the hardware (because they only had two of the devices). I fear that you may be having a problem with "licensing". Will new thin clients need to be purchased? Network Level Authentication (NLA) is disabled. So this is specific to the HP Thin Client interaction. New connections to the terminal server result in:īecause of a security error, the client could not connect to theĬonnecting to the old Windows 2003 server works fine. The other device type, of which there are many in the environment, is the HP T5510 Thin Client. That issue has been traced back to the Linux rdesktop capabilities. and RDP sessions initiated to the new terminal server disconnect immediately. The first batch of users migrated well, but as we encountered people with older HP devices, we discovered that some simply could not connect to the Windows 2008 R2 server. The environment is a mix of several generations of HP thin clients, as well as some Axel hardware terminals. I'm in the middle of a migration from an old virtualized Windows 2003 Terminal Server to a 2008 R2 RDS host. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |