Networks

Ask something
Discussion Locked

Remote Desktop

0 helpful
13 replies

by deerek11

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Hello All, I am working in a cluster envoiroment with serveral servers I use remote desktop threw out the day to control all of the server using my user account to log in but now we are seeing on the server each time I log in or any one from the IT dept after we log in all the services start and we think this is creating a problem with a SQL server is there a better way to remote to servers without starting all the services each time we log on remotely or should we be using the administator account?? Any Suggestions???

13 replies

by collignond

Get hold of the 2003 Administration Tools Pack, the remote desktop view that it gives you is of the currently running processes. It also has the added feature that you can nave all the servers in a list and specify usernames and passwords for each. and it connects to each with a single click on each servers icon.

by deerek11

Ok If I get the administator pack for windows 2003 will that prevent each time I log on remotly using Remote desktop starting all processes. That is the problem I am having each time I log on using Remote Desktop it starts all services including SQL and I think that is causing a problem for the SQL server.

by adembo

If you dont want the services started, why dont you just set the services to Manual?

by deerek11

If I set all service to manual if the server reboots they will not start or will they?? If I set them to Manual will I have to start the service every so often or how will that work? Also by setting the service to start manual can that be for one user account so I always use that account to remote to the servers with??

by adembo

Im a little confused. You want the services to start, and are already started. Then, when you log on, you are saying they start again? Thats not possible.

Services do not start when a user logs on with Remote Desktop. If your services are set to "Automatic" they will start when the computer boots, not when a user logs on. I guess a little more info as to what you need.

by deerek11

The problem we are having is everytime I log on and off the servers using remote desktop it looks like it starting all the services for each time I log on. Are you saying that the remote desktop connection doesn't start services for that connection?

by adembo

I am indeed saying that connecting via Remote Desktop does not start any services. Services only start automatically when the computer boots, or manually by clicking start.

Why not verify this so you see for yourself, but logging onto the console and viewing the services. Then, log on to the comptuer via remote desktop and see if there is any changes. You will not see any services started or stopped from logging on.

What are the problems you are having with SQL?

by deerek11

Thanks so much for assiting me with this issue when you are done assiting me I will definiley increase the points but the problem I am having is I just log on RDP to one of our server here and then I opened up taks manager and look at all the processes running and click on the tab show other process then I RDP to the same server and all the processes that were running started for that user too even if I use the same user account it starts all the processes this is the problem I am having my manager doesnt want or he is thinking this is creating a problem for our sql server becuase if you look at the processes running each time I log on using RDP it starts a new process for that account is there a way to stop this also does this slow down the server??

by adembo

So is it processes or services that are causing the problem? Is it the process that the service runs? If you log onto the server as a different user, its bound to have processes that run as that user. If you launch Internet Explorer when you are on RDP, why would it run that process under anybody elses account than yours that you log on as?

You may try assigning the service an account to run under. By default, its probably set to system, but if you change the service to run as a specified account, that may fix your issue.

It would be important to know what processes are running that you are concerned about. If you look at Terminal Services Manager on your server, you should be able to see all processes that are running as each user that is logged on. You can use that to help in determining what process may be causing issues.

by ptaparia

A good way (Im not sure if it is the most secure one though) would be to create a Remote Access User account in your AD and have that user log in each time you remote access a server.

What this will do is that it will automatically log the user into the last session that the user logged into thereby not starting up the processes that are invoked by the services each time a new user logs in. You will have to configure your terminal server to increase the idle time for any connection to ensure that your connection is not disconnected after some amount of inactivity.

I feel the above is the easiest method to handle the situation given the amount of time and resources you need for the task. If you are adventurous, try deploying SMS (System Management Server) on your network and use Remote Tools to connect to any PC's console without having to log in each time.

Hope this helps.

by ptaparia

I forgot to add that when you log in using the Remote Access account, do not log off when your work is over. Simply close the remote desktop window.

This discussion is closed to new replies.