We have the NX 3.5 and NX 4.0 clients on HP thin clients. I have installed the 4.0 client on t5725, t5745, t610 and t620 (current model). The t5725s need a good amount of tuning because they are so old and only have a single core. But t5745 and higher work perfectly well. In our case, we are deploying using LightWeight mode. If you deploy using one of the codecs, you will probably need the t620.
We are looking at the HP t620s. I have seen various posts and howtos online for getting the NX Client up and running on HP Thin Clients running Thin Pro. They all seem to be using NX 3.5, but you seem to report using 4.x which is great news that it works as well. Would you happen to have any documentation you could share? If not, any gotchas or advise?
@brandon.ess: We do not use the standard HP tools — we have found our own home brewed solutions to work far better. What you do is take a t620 and go into the admin side and assign a password to root. Then you create a custom connection to run /usr/bin/xterm which gives you the command prompt. Then you type in ‘fsunlock” to be able to change the file system. Then download the NX 4 .deb package and install using normal dpkg commands. At that point, the client runs and you can connect to the server. We run the NX client as user ‘user’, and what I do is mount a RAM file system into /home/user/.nx. The NX client sees this as hard drive space and all caching then is done at memory speeds instead of using the local flash “hard drive” which are much slower. When users pick NX, I lay a new tarball with all settings into /home/user/.nx and then activate the client. That way the users have no way to bork up the settings and everything is wiped clean with each new launch. t5725, t5745, t610 and t620 all work with this technique. The t620s are blazingly fast.
When we push updates to the HP workstations, we always use the open source software FOG. It’s far faster than the HP tools. We can do hundreds of workstations a night with FOG with no problems.