Central Administration of the thin client

Similar Questions

• Central directors of the thin client

  
  

  HP Device Manager

• Get the Thin Client IP address

  Hello. I'm trying to find out the IP address of the machine that I use for programming. I want to use my LabVIEW program on a server. However, the string to the property intellectual VI gives the IP address of the network, so in this case the server IP address. It is a problem, as we hope, in the future, run multiple thin on program clients, if we want the program to know what thin client, it works on. However, I don't have access to the command prompt on the thin client due to administrative restrictions. This eliminates the other solution I found, which was to find the Login Windows user name (each light client has its own unique user name) through different screw which involved the command prompt. Any ideas on how to find the IP address of the customer of the Services Terminal Server Session, I believe that my computer called? Thanks for your time.

  I called and he was referred to this, which worked. We use Citrix server and the username thing worked, and we are now able to run the program for each thin client using his user name.

• 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

• 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

• Connecting the thin client to the virtual desktop

  Guys, I'm looking to provide some knowledge of locations to my current View 4 implementation. I need essentially allow thin clients in the room for a particular virtual desktop access, but the user access to all other workstations when they are in a different room\different thin client.

  At the present time, it seems possible to connect a desktop computer to an end user and not a customer light name or address etc.

  Is there anyway that I can link a pool of funds or office to a lightweight client device so that the bureau is only launched from this location?

  Thank you

  We are able to do something like that today.  Serve us our Wyse thin client and when the thin clients boot they go to an ftp site to obtain their configuration files.  The configuration file can be modified to configure how clients view client work light linux.  So, to process your request, we would put in class A on a network that has a config file that will automatically connect to a certain pool of virtual desktops.  In all networks, they would receive a configuration file that allows them to get the menu and choose what desktop Pool to connect to.

  I don't know what light supplier customer, you have, but I'm assuming that Wyse is not the only one with a certain type of configuration like this.

• This computer can't connect to the remote computer. ONLY 2 people it out 200 users...? baffeled by WindowsXPe Thin Client RDP connection

  Here's the situation.  We have 2 TS servers running WIN2K3 and 200 users with Thin Clients.  We'll call it the first server A and b of a second.

  They normally connect to an IP address and they will be directed to the server A or B according to the load.

  However; users can still select the specific TS server, they want to connect to.

  If user 1 and user 2 cannot connect to Server B.  They get the error listed above in the title.  However the user 1 and 2 can connect to A server.  If they say:

  192.168.123.2 the two of them get

  192.168.123.3 the two of them cannot get.

  I deleted the user de.3 A profile and it still can't get.  I have checked no orphan key inHKEY_LOCAL_MACHINEMicrosoft\Windows NT\CurrentVersion\ProfileList

  I checked the settings in TSCC. MSC, I' checked worm Licensing by user and they are good, I gave them full administrator privileges and still not pass via the serveur.3, they adhere to all groups within the ORGANIZATIONAL unit that they can connect to TS, they were able to connect to her very well this back on Wednesday.  It is not a firewall issue and port 3389 has been verified in the case otherwise he would not just these two on each CT they try.

  Again, they can get utilisant.2.

  In the event de.3 Viewer I can see users connected CORRECTLY but then it pop their right.  There is no other error message when connecting, just the success Message in the security log.

  Let's bounce servers tonight so I'll have to turn it back on and I pray that they can later log on this server, but I'm baffeled.  Why only 2 people would receive this question and most (not sure how many others there may be, but I know 30 people connected today on this server and worked out of it) people are not getting an error.

  The thin client on their desktop is not the issue, because the error follows them any CLIENT LÉGER, they are connecting from.

  Short of this re-boot and short to delete accounts and recreate them, ideas?

  Found the problem.  I did not remove the key to all the indicated previously.  I should have done that for this user since her CentralProfile Key was empty when she had to be filled in by the system.  Removed his Key specific SID for listed above point and viola.  User can connect.

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

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

• Thin client based on Linux T610

  Bulletin Board Hello!

  Just a few questions here I can't find via Google, manual and read other messages of the forum...

  We are trying to use a t610 with the Linux-based operating system and are facing obstacles, a little...

  I saw on the thin clients based on "Windows", after making a change to something, you have to 'Commit' changes...

  Is it possible to do it on a Linux machine? It seems that the operating system partition is read-only?

  Also, is it possible to navigate through the files and folders of this type of thin client?

  I see the terminal in "Administrator" mode and I can't type-nav files and folders through the text editor, but I am a semi-perte to do things this way...

  I know it of maybe a stupid question, but is there a way to recreate the image on this thin client to an OS based on "Windows"?

  The main problem I encounter is an add-on/extension in firefox is not 'stick' in my firefox browser...

  I installed the extension again and after I restart the browser, he is gone and my settings are back to "original"...

  I take a guess here, but I guess whenever this customer "reboots" the start of an image?

  One last question, is there of the "manuals" for those customers based on Linux?

  I see most or all aid seems to aim at Windows and would like to just a reference...

  Thanks for reading!

  Brandon

  If you're talking about the HP ThinPro OS-

  Before you can make changes to the file system, you must run this command from the terminal - "fsunlock". When you are finished, 'fslock' locks the system files again. There isn't another tool file explore included I know in ThinPro. Command line and the Notepad tool are the only real ways to navigate through the file system. If you need help with something, don't forget, it's basically a lighter version of Ubuntu, with a few extra utilities and GUI provided by HP. The nuts and bolts are identical to a version of Ubuntu, so I took a bit of insight of Ubuntu forums online for the problems I've had.

  Regarding your problem of browser extensions, depending on how you do this, you can configure connections to allow them to configure their own settings, or use HP ThinPro settings. If you've not allowed Firefox to create and use its own settings in the file system, nothing don't you change inside the browser will stick. I have not tried to install a browser extension, but I'm sure that this is your problem.

• Thin clients connect not to view.

  Good so it's weird. I have a HP thin client (model hstnc-006-tc is important) sitting in my NOC. I point to my server connection. I can connect to the domain controller in the thin client, see the desktop that the user has rights, but when they connect he says "the login server Vew prepares the office" and sits there for about 30 seconds. After 30 seconds, or so he error with the following error: "this office is currently not available. Please, try to connect to this desktop computer later, or contact your system administrator. »

  The inside of the connection manager, I see my office as available. It is active, title and power. I get no error on the part of the present events. Now, my connection to the server and the server vcenter actually live on different networks. Can only cause a problem? It wasn't when I was testing it from my office. I was under the impression that the customer should not talk to vcenter, it is only necessary to connect with the login server, ports 443, 3389 and 4001 are open to the.

  Any thoughts?

  Thanks in advance.

  Please check you can test using the full domain name

  Agent to server connection computer

  Client computer to the server connection

  Client computer to the Agent computer

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

• 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 HP t610 thin WW: thin client

  Installed an update a few months ago, and everytime I turn on the thin client, he begins to initialize.  After that initial "starting Windows" screen it starts at the end of the update of Windows saying:

  'Stage 3 of 3 '.

  "Configure Windows update."

  '32% complete '.

  "Do not turn off your computer.

  If stays there for a few minutes, then it starts to close.  But it restarts the computer and is stuck in this loop, until I have turn off the workstation.

  NSMerrick, welcome to the forum.

  I think that you will get more responses to your question if you start a thread here.  They are the members who know the better your Thin Client.

  Please click on the Thumbs up button '+' if I helped you and click on "Accept as Solution" If your problem is resolved.