RDP session

A client is running 12 sessions on a 2012 remote desktop VM server from a local network.  They are only using one application built on a SQL Server database.  Server has 32GB ram, plenty of processor/hard disk.  Network is on 1000Mb switch.  All workstations are Windows 7.  When using remote session, one user is experiencing occasional delays in typing.  You press the letters on the keyboard, then it takes a few seconds for them to fill in the form.  

We asked one user to run the software on her local machine, using the network only for the SQL connection back to the server.  She experienced no delay.  This appears to be an issue with Remote Desktop traffic over the network.  We tried to disable autotuning as well, with no luck.

We thought we had solved the issue before in another question but it came back in a week for one of the clients. I checked the computer for a different AV installed (that was the issue on another computer) but none had got on there. any ideas?

Please advise.
LVL 1
Jordan SmithAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick BogersDatacenter platform engineer LindowsCommented:
Hi,

I would check for malware being present and secondly i would inspect her RDP settings, maybe her graphical settings are set way to high?
0
OOsorioCommented:
There are several possibilities. As Patricksr1972 mentions, it could be a settings issue in RDP or malwares, trojans, viruses, etc. Check Programs and Features and remove any unnecessary programs. Users usually unknowingly download all sorts of features. This latter could also be true for this users Terminal Sever profile. If you can't find the problem on the work station side try creating a new Terminal Server profile for this user.
0
Jordan SmithAuthor Commented:
We ended up fixing the problem by moving the affected users to the local version of the software instead of the Terminal services way. turns out the problem is the vendors fault. not fully compatible with SQL 2012
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jordan SmithAuthor Commented:
We figured out the problem talking to the vendor
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.