Tech Support Forum - View Single Post - Windows 2003 Server, Terminal Services Sessions using lots of CPU

**Eclipse2003** · 07-02-2009, 06:30 AM

I have a network where we connect to the server via Terminal Services for our client management software. As of now, we just connect and the users open up the software by double clicking. If I set a Group Policy where once they click connect it opens up the software and they don't see the desktop at all, will that save CPU resources? Or do you have any other suggestions as to how we can save resources because the server has been acting a bit slow lately and the CPU usage can get kind of high. Also, there are multiple processes for the same application such as Mozy which is our online backup system. I am assuming it opens a new process for each user that logs in. Let me know your thoughts. Thanks!

07-02-2009, 06:30 AM	#1 (permalink)
Eclipse2003 TSF Enthusiast Join Date: Apr 2005 Location: Ohio Posts: 1,156 OS: XP	Windows 2003 Server, Terminal Services Sessions using lots of CPU I have a network where we connect to the server via Terminal Services for our client management software. As of now, we just connect and the users open up the software by double clicking. If I set a Group Policy where once they click connect it opens up the software and they don't see the desktop at all, will that save CPU resources? Or do you have any other suggestions as to how we can save resources because the server has been acting a bit slow lately and the CPU usage can get kind of high. Also, there are multiple processes for the same application such as Mozy which is our online backup system. I am assuming it opens a new process for each user that logs in. Let me know your thoughts. Thanks!