Discussion Locked
0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We use Terminal Services only for remote administration of our server. We seem to be running into a problems with the server automatically loading programs when we log in through Terminal Services. Normally it is programs that are actually alreadyrunning on ther server, then Terminal Services starts them again and we get an error because the programs isn't meant to be running twice. Is there a way to prevent certain things from launching when we use Terminal Services? When we log in we useAdministrator so we can get all of our screen settings and things the same. Any help is appreciated!
3 replies
by p. dickason, cne, mcse, cca
If you want to be safe, you really need two seperate user ID's for this purpose. One used only for the console and the second used for remote administration. Then move any program which may be in 'all users' startup group to be in the console userid's startup group only. In addition if the programs get started from the registry, they will need to be removed from the registry and placed in the console user id's startup group also. Or you can just ignore the message since an error message means it probably isn't doing anything anyway. Hope this helps.
Pete
by btrue
Poster rated this answer
by btrue
This question was closed by the author
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending
0 helpful
10 replies
Question Locked
Do You Save Useful Windows Tutorial Videos for Later
0 helpful
7 replies
0 helpful
1 reply
Question Unanswered
Is WSL still relevant in 2026?
0 helpful
0 replies
0 helpful
2 replies