kicking / logging out remote windows users?
up vote
14
down vote
favorite
I'd like to have something akin to a unix "who" and an option to kick out RDP sessions that are not supposed to be there (i.e. using up the limited number of connections). This is for a win2003 server Standard.
Additional info: this is a devel environment, people all use RDP as Administrator (I know, I know), so kicking out should be by session number or at least by remote IP/machine name, not per user.
Thanks!
windows remote-desktop kill
asked Oct 29 '09 at 12:04
Ira
83114
add a comment |
up vote
14
down vote
favorite
I'd like to have something akin to a unix "who" and an option to kick out RDP sessions that are not supposed to be there (i.e. using up the limited number of connections). This is for a win2003 server Standard.
Additional info: this is a devel environment, people all use RDP as Administrator (I know, I know), so kicking out should be by session number or at least by remote IP/machine name, not per user.
Thanks!
windows remote-desktop kill
asked Oct 29 '09 at 12:04
Ira
83114
add a comment |
up vote
14
down vote
favorite
up vote
14
down vote
favorite
I'd like to have something akin to a unix "who" and an option to kick out RDP sessions that are not supposed to be there (i.e. using up the limited number of connections). This is for a win2003 server Standard.
Additional info: this is a devel environment, people all use RDP as Administrator (I know, I know), so kicking out should be by session number or at least by remote IP/machine name, not per user.
Thanks!
windows remote-desktop kill
asked Oct 29 '09 at 12:04
Ira
83114
I'd like to have something akin to a unix "who" and an option to kick out RDP sessions that are not supposed to be there (i.e. using up the limited number of connections). This is for a win2003 server Standard.
Additional info: this is a devel environment, people all use RDP as Administrator (I know, I know), so kicking out should be by session number or at least by remote IP/machine name, not per user.
Thanks!
windows remote-desktop kill
windows remote-desktop kill
asked Oct 29 '09 at 12:04
Ira
83114
asked Oct 29 '09 at 12:04
Ira
83114
asked Oct 29 '09 at 12:04
Ira
83114
asked Oct 29 '09 at 12:04
Ira
83114
asked Oct 29 '09 at 12:04
Ira
83114
83114
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
up vote
18
down vote
accepted
Refer this post on kicking the users.
The summary of the commands is as follows:
Use qwinsta to get a list of the Remote Sessions in the command window (Get the session Id of user to kick out):
qwinsta /server:SERVERIP
Use rwinsta to disconnect the remote session:
rwinsta /server:SERVERIP SESSIONID
Also you may want to change the default timeout for idle RDP connections.here or here.
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
yup, I just found this post listing also quser and rwinsta: anandpv.spaces.live.com/blog/cns!AFCCA5892B178862!804.entry Thanks!
– Ira
Oct 29 '09 at 14:11
add a comment |
up vote
2
down vote
You should also be able to do this by pulling up Task Manager and going to Users and selecting users to Logoff or Disconnect. Disconnect will close their RDP session, but they can log back in to it. Logoff will... well, log off their current session.
answered Oct 29 '09 at 14:28
MattGWagner
181124
2
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :)
– Kip
Oct 29 '09 at 16:03
add a comment |
up vote
0
down vote
mstsc /console or mstsc /admin should let you always log on, but it will kick off anyone else who's logged in using the same technique.
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
add a comment |
up vote
0
down vote
For Windows 7 or other client OS from Microsoft, some of the MSTSC options will not work. As a last resort you may want to try restarting the machine (if that is an option)
shutdown /m mydevbox.myorg.com /r /f /t 0
answered Jul 28 '16 at 3:28
Faiz
1306
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f62498%2fkicking-logging-out-remote-windows-users%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
18
down vote
accepted
Refer this post on kicking the users.
The summary of the commands is as follows:
Use qwinsta to get a list of the Remote Sessions in the command window (Get the session Id of user to kick out):
qwinsta /server:SERVERIP
Use rwinsta to disconnect the remote session:
rwinsta /server:SERVERIP SESSIONID
Also you may want to change the default timeout for idle RDP connections.here or here.
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
yup, I just found this post listing also quser and rwinsta: anandpv.spaces.live.com/blog/cns!AFCCA5892B178862!804.entry Thanks!
– Ira
Oct 29 '09 at 14:11
add a comment |
up vote
18
down vote
accepted
Refer this post on kicking the users.
The summary of the commands is as follows:
Use qwinsta to get a list of the Remote Sessions in the command window (Get the session Id of user to kick out):
qwinsta /server:SERVERIP
Use rwinsta to disconnect the remote session:
rwinsta /server:SERVERIP SESSIONID
Also you may want to change the default timeout for idle RDP connections.here or here.
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
yup, I just found this post listing also quser and rwinsta: anandpv.spaces.live.com/blog/cns!AFCCA5892B178862!804.entry Thanks!
– Ira
Oct 29 '09 at 14:11
add a comment |
up vote
18
down vote
accepted
up vote
18
down vote
accepted
Refer this post on kicking the users.
The summary of the commands is as follows:
Use qwinsta to get a list of the Remote Sessions in the command window (Get the session Id of user to kick out):
qwinsta /server:SERVERIP
Use rwinsta to disconnect the remote session:
rwinsta /server:SERVERIP SESSIONID
Also you may want to change the default timeout for idle RDP connections.here or here.
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
Refer this post on kicking the users.
The summary of the commands is as follows:
Use qwinsta to get a list of the Remote Sessions in the command window (Get the session Id of user to kick out):
qwinsta /server:SERVERIP
Use rwinsta to disconnect the remote session:
rwinsta /server:SERVERIP SESSIONID
Also you may want to change the default timeout for idle RDP connections.here or here.
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
edited Dec 5 at 22:29
Cristian Ciupitu
4,1192540
4,1192540
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
answered Oct 29 '09 at 12:12
Ganesh R.
4,75112027
4,75112027
yup, I just found this post listing also quser and rwinsta: anandpv.spaces.live.com/blog/cns!AFCCA5892B178862!804.entry Thanks!
– Ira
Oct 29 '09 at 14:11
add a comment |
yup, I just found this post listing also quser and rwinsta: anandpv.spaces.live.com/blog/cns!AFCCA5892B178862!804.entry Thanks!
– Ira
Oct 29 '09 at 14:11
yup, I just found this post listing also quser and rwinsta: anandpv.spaces.live.com/blog/cns!AFCCA5892B178862!804.entry Thanks!
– Ira
Oct 29 '09 at 14:11
yup, I just found this post listing also quser and rwinsta: anandpv.spaces.live.com/blog/cns!AFCCA5892B178862!804.entry Thanks!
– Ira
Oct 29 '09 at 14:11
add a comment |
up vote
2
down vote
You should also be able to do this by pulling up Task Manager and going to Users and selecting users to Logoff or Disconnect. Disconnect will close their RDP session, but they can log back in to it. Logoff will... well, log off their current session.
answered Oct 29 '09 at 14:28
MattGWagner
181124
2
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :)
– Kip
Oct 29 '09 at 16:03
add a comment |
up vote
2
down vote
You should also be able to do this by pulling up Task Manager and going to Users and selecting users to Logoff or Disconnect. Disconnect will close their RDP session, but they can log back in to it. Logoff will... well, log off their current session.
answered Oct 29 '09 at 14:28
MattGWagner
181124
2
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :)
– Kip
Oct 29 '09 at 16:03
add a comment |
up vote
2
down vote
up vote
2
down vote
You should also be able to do this by pulling up Task Manager and going to Users and selecting users to Logoff or Disconnect. Disconnect will close their RDP session, but they can log back in to it. Logoff will... well, log off their current session.
answered Oct 29 '09 at 14:28
MattGWagner
181124
You should also be able to do this by pulling up Task Manager and going to Users and selecting users to Logoff or Disconnect. Disconnect will close their RDP session, but they can log back in to it. Logoff will... well, log off their current session.
answered Oct 29 '09 at 14:28
MattGWagner
181124
answered Oct 29 '09 at 14:28
MattGWagner
181124
answered Oct 29 '09 at 14:28
MattGWagner
181124
answered Oct 29 '09 at 14:28
MattGWagner
181124
181124
2
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :)
– Kip
Oct 29 '09 at 16:03
add a comment |
2
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :)
– Kip
Oct 29 '09 at 16:03
2
2
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :)
– Kip
Oct 29 '09 at 16:03
That would mean you were on the machine in question. What if you want to connect to a machine that is full already :)
– Kip
Oct 29 '09 at 16:03
add a comment |
up vote
0
down vote
mstsc /console or mstsc /admin should let you always log on, but it will kick off anyone else who's logged in using the same technique.
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
add a comment |
up vote
0
down vote
mstsc /console or mstsc /admin should let you always log on, but it will kick off anyone else who's logged in using the same technique.
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
add a comment |
up vote
0
down vote
up vote
0
down vote
mstsc /console or mstsc /admin should let you always log on, but it will kick off anyone else who's logged in using the same technique.
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
mstsc /console or mstsc /admin should let you always log on, but it will kick off anyone else who's logged in using the same technique.
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
answered Oct 29 '09 at 14:55
tjrobinson
2,09022341
2,09022341
add a comment |
add a comment |
up vote
0
down vote
For Windows 7 or other client OS from Microsoft, some of the MSTSC options will not work. As a last resort you may want to try restarting the machine (if that is an option)
shutdown /m mydevbox.myorg.com /r /f /t 0
answered Jul 28 '16 at 3:28
Faiz
1306
add a comment |
up vote
0
down vote
For Windows 7 or other client OS from Microsoft, some of the MSTSC options will not work. As a last resort you may want to try restarting the machine (if that is an option)
shutdown /m mydevbox.myorg.com /r /f /t 0
answered Jul 28 '16 at 3:28
Faiz
1306
add a comment |
up vote
0
down vote
up vote
0
down vote
For Windows 7 or other client OS from Microsoft, some of the MSTSC options will not work. As a last resort you may want to try restarting the machine (if that is an option)
shutdown /m mydevbox.myorg.com /r /f /t 0
answered Jul 28 '16 at 3:28
Faiz
1306
For Windows 7 or other client OS from Microsoft, some of the MSTSC options will not work. As a last resort you may want to try restarting the machine (if that is an option)
shutdown /m mydevbox.myorg.com /r /f /t 0
answered Jul 28 '16 at 3:28
Faiz
1306
answered Jul 28 '16 at 3:28
Faiz
1306
answered Jul 28 '16 at 3:28
Faiz
1306
answered Jul 28 '16 at 3:28
Faiz
1306
1306
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f62498%2fkicking-logging-out-remote-windows-users%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
