Hi everyone,
We have this XP PC that we need to rdp in from our Win 7 machines. The strange thing is whenever we rdp in, we noticed that the XP machine is very sluggish and the CPU usage almost maxed out at 100%. We only have Outlook 2010 running, and some vendor printing service monitoring running, and antivirus [McAfee].
When we access the XP locally, everything is back to normal. CPU usage is like 1 or 2 %.
So, it appeared the RDP process actually cause the client PC CPU usage to spike. Wonder if anyone else had faced similar issues? Any suggestion to solve it?
Thank you in advance!
EBS Computer Services is an IT service provider.
SM Yeoh wrote:
When I checked the task manager, the main memory hog is the antivirus, followed by outlook
Not memory - CPU. I assume there's a process hogging 80/90% of the CPU - what is it?
- Show off your IT IQ. Take the Challenge »
- Setting up new windows image deployment how to
- Is there something better then file explorer?
- Powershell where-object variable help
- ROM
- CPU
- RAM
- GPU
6 Replies
EBS Computer Services is an IT service provider.
Which process exactly is using the CPU?
Is the box fully patched?
When I checked the task manager, the main memory hog is the antivirus, followed by outlook
It is fully patched
EBS Computer Services is an IT service provider.
SM Yeoh wrote:
When I checked the task manager, the main memory hog is the antivirus, followed by outlook
Not memory - CPU. I assume there's a process hogging 80/90% of the CPU - what is it?
By default RDP pushes a lot of things through like printers and stuff, you might have an issue there, try disabling the printer redirection as well as sounds
thank you Joe and Christian for your help. Funny thing is the issue has been happening for some time. Now that I finally got down to troubleshoot it, it suddenly went back to normal. I am not sure what happened either. Perhaps my colleague did something that I am not aware of as I am not the only user to that PC. Nevertheless, I will keep monitoring it and look out for the CPU hog as Joe suggested, and try to remove printer redirection [as I do notice printer redirection log in the remote client event log] if the problem happens again.
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.