latexfoam
asked on
New Terminal Server Running Slow for remote users
I recently install a Brand New Windows 2003 Advanced Server with Terminal Services. Remote users have been complaining that it is considerable slower then the original server. When I am working on the machine it shows no signs of why its performing so poorly. The memory, processor, and Networking are all under 5 % utilized. Are tehre any setting that would cause this to respond slow when being used as a terminal server?
It appears to me likely that the problem is on the user end, not the server end. Would the users have needed to set up a new RDP connection to the new server - i.e., does the new server have a different name? If so, I'm wondering if they might have set the Experience and/or Display settings too high, so that, for example, their workstations are trying to run the RDP session at a very high resolution level, or trying to send back and forth things like desktop backgrounds and animation. Normally, I advise users to set their display options at 256K and their experience level at "Modem (56kbps)" even if they're using a broadband connection. This makes a huge difference in the speed of working in the RDP session.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I searched Microsoft's web site for answers to this and never came across this solution. After applying the new registry settings all the end users were satisfied with teh speed.
Let me know if this helps.