I a 16 user L230. my problem is that the terminals freezes. At logon, they are fine but they start to freeze after about 20mins after i switch the system on. its not particular stations athat freezes but...
The terminals never actually freeze as they are getting desktop sessions from the host. What can happen is the desktop session can lock up and thus any corresponding user input doesn't happen due to the session being locked up. Next time this happens, see if the server/host is responsive. Assuming it is, launch Performance Monitor(Provided as part of the Windows OS) by going to Start ' Run ' Perfmon. Monitor your CPU performance. See what's taking all the CPU resources. It's not uncommon to see unncessary programs running, i.e. jusched.exe (Java Scheduler update), qttask.exe (Quick Time updater), etc. All these programs and other unnecessary programs run at startup and run for EVERY single user so in your case, the jusched.exe runs 16 times and can take valuable system resources. Disable these by going to Start ' Run ' msconfig, press enter, the farthest tab on the right labled STARTUP is where you can disable these programs. After deselecting the ones you don't need, reboot the host and tell the dialog box to NEVER tell you again so that it doesn't alarm you're users that you've messed with the startup config. Lastly, don't overlook that fact that you need 1GB NIC and backbone to the server, each device can take up to 15MB/s of network bandwidth.
Jul 05, 2011 |
NComputing L230 Network Terminal