Most of our 250+ machines are desktops, followed by laptops, thin clients and a then dozen or so VMware servers. We have approx two dozen thin clients. Most run their own VMware vm. These machines are not a problem, LD finds them and installs the agent on them, and we can connect to them. About a half dozen of the remaining thin clients however, log in through terminal server to get to a shared vm. These are the machines we're concerned with here...
Can we use LD with these remaining thin clients? If so, how? I've checked the LD docs and this forum, and can only find reference to handheld devices, which these are not. My co-worker informs me that we can connect to the terminal server itself, but we can not connect to the individual sessions, which is what we would really want to do. If we can't, what good is LD for these machines?
If anyone knows the answer, we'd appreciate the assistance.
Thanks in advance,
Tom
P.S. - Under "Popular Tags", as I compose my message, "requirement" is missing the middle "e".
Are these Diskless thinclients? Or do they have a Disk with an OS on them?
When you say they login through terminal services to run a shared VM, how does this happen. What do they boot to? What do they use to login through terminal services?
While I haven't actually played with one of these myself...I'm told that they have a hard disk of approx 10gb capacity. Although...HP's website does not mention any hard disk whatsoever. It just says that Genuine Windows XP SP2 is "Embedded".
I haven't seen this myself, but when powered up, it wants to know what it should connect to. We tell it the name of our terminal server, then click a button that says "Connect". It then makes the connection, and one then logs onto the server as they would normally log onto their own normal PC. ( This is what I'm being told. We don't have such a user here in this building that I can go check out. )
Sounds like this is different than a diskless client.
It is just that if it is bringing up Terminal services, then the Terminal Services Operating System is running on the server and a scan would only scan the Server side. It wouldn't have access to scan the local box because it is just passing the screen to the local box, but not running on it.
The agent would have to be on the OS that launches the terminal services session, which is why I was wondering. Does it boot to an XP embedded and then ask you to Terminal Services in?
If so then the XP Embedded software needs to have the agent on it.
(Sorry...I am not an expert on embedded devices, but since no one else responded to your post I figured I could at least share a guess.)
Thanks, I appreciate it.
It's very frustrating. One of the reasons we have LD is for remote control. We're now starting to put out more thin clients and setting them up this way, and the boss says we'll be doing even more in the future. It sounds like we'll eventually replace all of our desktops with thin clients as time goes on. How are we supposed to connect to them?
I guess the laptops are safe, for the moment. ![]()
Most of the thin clients we use have CE embedded so we don't use LANDesk. If the embedded XP will let you install software, you should be able to deploy the LANDesk agent. If you only want Remote Control, I would limit the agent to just the basics and the Remote Control features. Also, with Terminal Services, you can install the Terminal Services Manager which I believe is included in the Administration Tools Pack. This will allow you to monitor the connections on any of the terminal servers in your organization as well as allow you to Shadow any user connected. This way the LANDesk licenses can be leveraged for full functionality on the PCs where you need to be able to deploy software, conduct inventories, etc.
Hope this Helps
BF
Did you ever figure out what OS is on the Thin Clients?
In most cases we can install on Windows XP embedded. Windows CE will not work but because the devices are primarily using XP embedded (according to the Google search I just did) we can PROBABLY find a way to install the Agent and manage the devices. If you can send one in for testing we usually find a way.
--Jed
Hey tsmith,
I was having the same problem deploy Ldagent to the hp thin clients with windows embedded. I was playing around with the thin client and ran the ldagent.msi. The msi work for the thin client but after it installs you have to go to the HP Sygate Security Agent. Within the Security Agent you have to browse to the landesk agent folder to allow the executables for ldagent.
Hope this solves the problem.
I have the same issue trying to get the LDMS Agent installed on a T5720, but when I run the LDAgent.exe to install the agent it tried to install, but nothing happens. I can see the temp folder gets created, but then it quickly disappears. When I push the agent to the thinclient it comes back and tells me it is successful, but again nothing happens. I couldn't figure out what Jason is talking about when he says 'HP Sygate Security Agent'. I don't have anything on the thinclient that refers to that. Another thing I noticed is that there is not a typical hard drive in this device. It appears as a Flash Drive. When I go into Disk Manager no disk shows up. i am not sure if this is my problem. Any ideas?
Hey Scott,
I ran the MSI of the ldagent not the exe of the agent. I created my own agent just for thin clients. You can try to read this documentation provide by LANDesk.
http://community.landesk.com/support/docs/DOC-1100. After creating a MSI version of the agent just run the msi.
I'm an idiot. I was actually searching for a file called ldagent.msi. Guess I didn't realize it was the Advanced Agent Install. Thanks for you help. I had to go into the HP Device Manager - Management Console and disable the FBWF and reboot the thinclient before it would work. Couldn't get the agent.exe to work, but that advancedagent.msi is working fine.
I've just spent about a month configuring and testing HP Thinclients with LANDesk. There are many hurdles - too many for this post. The big factor on any Thin client (XPE) is what type of write filter they are using - File-Based Write Filter (FBWF) or Enhanced Write Filter (EWF) . If you ask nicely HP provide an image with FBWF. IMO - FBWF is the only way to go with XPE and the client. Also get used to provisioning for any software distribution, yes XPE should be patched. You can hit me up on email if you want to go into this. BTW, LANDesk was not really helpful on this one (me and Thinclients) - sorry guys.
Zman,
I second your opinion on LANDesk being helpful with support on ThinClients. IMHO LANDesk should provide more support and information about the possilities and hurdles as many people have a mixed environment.
Did you ever get Vboot to work on ThinClients? PXE boot and restoring an image that way are working excellent, but Vboot is problem because of the fragmentation of ThinClient disks...
Thnx,
Frank
Axle-IT
I'm just about to push for some thin clients in our environment so I can get my feet wet on the technology. Given what's mentioned above, can anyone recommend a solution that's working well for them? I would like to have LD installed if possible. The first application I'd like to test thin clients on is one of our training rooms. I'm not terribly familiar with the embedded XP vs. a Citrix or RDP-based solution (would that be a "disked" client vs. a "diskless" client?). My lofty goal in this would be to use the Launchpad with virtual apps available via either means, RDP or on the disk, with the apps stored on the file server.
Any recommendations are appreciated. Thanks.
| ||||||
