User that doesn't start services on Servers

Do you mean you want to prevent numerous "applications" from starting when users log in? Services run regardless of whether a user is logged in or not...

You could certainly stop a user account from loading certain some applications automatically if they are loaded through that user's "Startup" (C:\Documents and Settings\\Start Menu\Programs\Startup) by default or in its individual registry settings (HKEY_CURRENT_USER\Microsoft\Windows\CurrentVersion\Run by default).

Winterfrost is right. A server doesn't have to have a user logged on to provide a service.

If your talking about applications that are installed on the local machine [server or not] that usually start at log in or startup, this is different than services that start.

remote desktop into a server for remote admin should not interfer with services running nor cause undo hogging or system resources.

"I am having the problem when I connecto to servers using remote desktop if you look into task manager all the processes are running twice and is slowing down the server."

Some processes *must* run for each logged-in user. You won't be able to create a user who does not start any new processes or it couldn't even log in. Perhaps if you told us which processes were causing the large performance impact, we could assist better.

"I was thinking of setting up a user that on a local level on the server that it doesn't start any processes but what is require to open up a new session or is there a better way to do this..."

Again, you can see my answer above for how to prevent certain processes from starting when a user logs in: Startup menu and Run key are where I would start. You might also need to check what processes the login script is running and exclude this user from running them based on user name or group membership.

"... also I notice that you said that by remote desktop to a server doesn't cause any hogging or system resources issues I can't find any thing relating to that on microsoft support pages"

I think he's just saying that by simply logging in another session shouldn't cause a serious impact on performance. Now if you are firing up a dozen new applications when each user logs in (as part of the All Users profile, login script, etc.), that's a different story. Again, it would be helpful to know what you are seeing which is causing such a huge performance lag.

As an aside, if you are simply trying to see what is going on on the server and are this concerned about additional sessions, maybe Remote Desktop isn't the right solution. Have you checked out remote control packages like VNC (http://www.realvnc.com -- it's free), pcAnywhere, or NetOp? They let you see/control the actual server console without needing to log in to a new virtual/terminal session like Remote Desktop.

I'm still fuzzy about this whole thing about remote desktop to servers. Again Winterfrost has some good ideas.

Unless your hacking into a server OR your doing a remote assistance, the remote desktop/remote administration connection shouldn't cause any performance hits or even chew up network bandwidth.

Give us a snap shot of what your seeing in task manager after you remote in that shows double services running.