Disconnect vs SIgn Out on Windows RDCLogging into Windows Server via RDC Takes Too LongHow do you find what process is holding a file open in Windows?Windows 7 Multi Monitor RDC ProblemRDC client access permissionsWinXP RDC connection bar appears like the RDC connection bar for Windows Server 2008?Terminal Server Role broke RDCHow to configure Windows RDC to use 16-color mode?Kaspersky blocked RDC on Windows - how to fix?RDP-ing or RDC-ingCopy configuration between multiple RDC sessionsSafe to Disconnect during RDC Logoff
What is the most expensive material in the world that could be used to create Pun-Pun's lute?
How can the Zone of Truth spell be defeated without the caster knowing?
How to make a pipeline wait for end-of-file or stop after an error?
Reducing vertical space in stackrel
Pass By Reference VS Pass by Value
Don’t seats that recline flat defeat the purpose of having seatbelts?
Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?
Why do games have consumables?
Is there really no use for MD5 anymore?
Pulling the rope with one hand is as heavy as with two hands?
Rivers without rain
how to sum variables from file in bash
simple conditions equation
Why was Germany not as successful as other Europeans in establishing overseas colonies?
How to solve constants out of the internal energy equation?
What are the potential pitfalls when using metals as a currency?
What's the polite way to say "I need to urinate"?
How can I change the color of a part of a line?
Will a top journal at least read my introduction?
The Defining Moment
How to get a plain text file version of a CP/M .BAS (M-BASIC) program?
What happened to Captain America in Endgame?
A Note on N!
Sci-fi novel series with instant travel between planets through gates. A river runs through the gates
Disconnect vs SIgn Out on Windows RDC
Logging into Windows Server via RDC Takes Too LongHow do you find what process is holding a file open in Windows?Windows 7 Multi Monitor RDC ProblemRDC client access permissionsWinXP RDC connection bar appears like the RDC connection bar for Windows Server 2008?Terminal Server Role broke RDCHow to configure Windows RDC to use 16-color mode?Kaspersky blocked RDC on Windows - how to fix?RDP-ing or RDC-ingCopy configuration between multiple RDC sessionsSafe to Disconnect during RDC Logoff
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I'm wondering how different end-of-session protocols affect Windows Server performance or anything else. On our Win10 server, users can either "disconnect" or "sign out".
I sign out every time after a session, unless there's a long process running that I need to complete. This can take a while - I wait for 5-10 minutes on a "please wait for user profile service" blue screen. Logging on similarly takes me 10-15 minutes.
I learned that other users always use "disconnect", essentially always remaining logged in, largely to avoid the long sign-in/sign-out wait time that I experience. Is there any disadvantage to this approach, or can I adopt it as well? My intuition is that keeping 5-10 users perpetually logged in degrades the performance of the server or possibly costs our company money, but I have no evidence to back this up
windows login rdc
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
add a comment |
I'm wondering how different end-of-session protocols affect Windows Server performance or anything else. On our Win10 server, users can either "disconnect" or "sign out".
I sign out every time after a session, unless there's a long process running that I need to complete. This can take a while - I wait for 5-10 minutes on a "please wait for user profile service" blue screen. Logging on similarly takes me 10-15 minutes.
I learned that other users always use "disconnect", essentially always remaining logged in, largely to avoid the long sign-in/sign-out wait time that I experience. Is there any disadvantage to this approach, or can I adopt it as well? My intuition is that keeping 5-10 users perpetually logged in degrades the performance of the server or possibly costs our company money, but I have no evidence to back this up
windows login rdc
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
How would it cost your company money?
– joeqwerty
Mar 16 at 14:17
i thought some cloud providers charged by user or login time
– Mike Palmice
Mar 16 at 14:26
Perhaps you should address the 10-15 minute logon performance issue. You're also not going to be able to differentiate between a session that the user disconnected, or a session that was disconnected from a network interruption.
– Greg Askew
Mar 16 at 14:36
Ok, but let's assume that none of the disconnected sessions were caused by network problems; also aren't the effects the same? w.r.t. 10-15 min logon, my user profile has been removed and reinstalled to no avail. I agree the long logon period is troublesome. I've posted a separate question here: serverfault.com/questions/958572/…
– Mike Palmice
Mar 16 at 14:45
add a comment |
I'm wondering how different end-of-session protocols affect Windows Server performance or anything else. On our Win10 server, users can either "disconnect" or "sign out".
I sign out every time after a session, unless there's a long process running that I need to complete. This can take a while - I wait for 5-10 minutes on a "please wait for user profile service" blue screen. Logging on similarly takes me 10-15 minutes.
I learned that other users always use "disconnect", essentially always remaining logged in, largely to avoid the long sign-in/sign-out wait time that I experience. Is there any disadvantage to this approach, or can I adopt it as well? My intuition is that keeping 5-10 users perpetually logged in degrades the performance of the server or possibly costs our company money, but I have no evidence to back this up
windows login rdc
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
I'm wondering how different end-of-session protocols affect Windows Server performance or anything else. On our Win10 server, users can either "disconnect" or "sign out".
I sign out every time after a session, unless there's a long process running that I need to complete. This can take a while - I wait for 5-10 minutes on a "please wait for user profile service" blue screen. Logging on similarly takes me 10-15 minutes.
I learned that other users always use "disconnect", essentially always remaining logged in, largely to avoid the long sign-in/sign-out wait time that I experience. Is there any disadvantage to this approach, or can I adopt it as well? My intuition is that keeping 5-10 users perpetually logged in degrades the performance of the server or possibly costs our company money, but I have no evidence to back this up
windows login rdc
windows login rdc
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
asked Mar 16 at 13:51
Mike PalmiceMike Palmice
1014
1014
How would it cost your company money?
– joeqwerty
Mar 16 at 14:17
i thought some cloud providers charged by user or login time
– Mike Palmice
Mar 16 at 14:26
Perhaps you should address the 10-15 minute logon performance issue. You're also not going to be able to differentiate between a session that the user disconnected, or a session that was disconnected from a network interruption.
– Greg Askew
Mar 16 at 14:36
Ok, but let's assume that none of the disconnected sessions were caused by network problems; also aren't the effects the same? w.r.t. 10-15 min logon, my user profile has been removed and reinstalled to no avail. I agree the long logon period is troublesome. I've posted a separate question here: serverfault.com/questions/958572/…
– Mike Palmice
Mar 16 at 14:45
add a comment |
How would it cost your company money?
– joeqwerty
Mar 16 at 14:17
i thought some cloud providers charged by user or login time
– Mike Palmice
Mar 16 at 14:26
Perhaps you should address the 10-15 minute logon performance issue. You're also not going to be able to differentiate between a session that the user disconnected, or a session that was disconnected from a network interruption.
– Greg Askew
Mar 16 at 14:36
Ok, but let's assume that none of the disconnected sessions were caused by network problems; also aren't the effects the same? w.r.t. 10-15 min logon, my user profile has been removed and reinstalled to no avail. I agree the long logon period is troublesome. I've posted a separate question here: serverfault.com/questions/958572/…
– Mike Palmice
Mar 16 at 14:45
How would it cost your company money?
– joeqwerty
Mar 16 at 14:17
How would it cost your company money?
– joeqwerty
Mar 16 at 14:17
i thought some cloud providers charged by user or login time
– Mike Palmice
Mar 16 at 14:26
i thought some cloud providers charged by user or login time
– Mike Palmice
Mar 16 at 14:26
Perhaps you should address the 10-15 minute logon performance issue. You're also not going to be able to differentiate between a session that the user disconnected, or a session that was disconnected from a network interruption.
– Greg Askew
Mar 16 at 14:36
Perhaps you should address the 10-15 minute logon performance issue. You're also not going to be able to differentiate between a session that the user disconnected, or a session that was disconnected from a network interruption.
– Greg Askew
Mar 16 at 14:36
Ok, but let's assume that none of the disconnected sessions were caused by network problems; also aren't the effects the same? w.r.t. 10-15 min logon, my user profile has been removed and reinstalled to no avail. I agree the long logon period is troublesome. I've posted a separate question here: serverfault.com/questions/958572/…
– Mike Palmice
Mar 16 at 14:45
Ok, but let's assume that none of the disconnected sessions were caused by network problems; also aren't the effects the same? w.r.t. 10-15 min logon, my user profile has been removed and reinstalled to no avail. I agree the long logon period is troublesome. I've posted a separate question here: serverfault.com/questions/958572/…
– Mike Palmice
Mar 16 at 14:45
add a comment |
1 Answer
1
active
oldest
votes
Personally, I always "Logoff" from a RDP connection, in order to avoid various issues, the biggest one being that my password could expire and if it does while I'm still "connected" to a server, then my account would enter an "account lockout" loop as it would constantly try to authentify to that server.
Another issue that can be avoided is that some programs have issues when more than one instance of their process is running. So if User A connects to the server, launches said process, then "Disconnects", and User B connects later on and tries to launch the same process, he may encounter an error message.
And obviously, when you "Disconnect" from a server, all the resources you used when you were logged in are still in use and won't be freed until you do a "Logoff", which could affect the system in the long run depending on its specs, and how many users connected to it and haven't logged off.
edited Apr 20 at 23:01
womble♦
86k18146205
answered Apr 20 at 20:05
AuraAura
1515
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
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',
autoActivateHeartbeat: false,
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%2fserverfault.com%2fquestions%2f958570%2fdisconnect-vs-sign-out-on-windows-rdc%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Personally, I always "Logoff" from a RDP connection, in order to avoid various issues, the biggest one being that my password could expire and if it does while I'm still "connected" to a server, then my account would enter an "account lockout" loop as it would constantly try to authentify to that server.
Another issue that can be avoided is that some programs have issues when more than one instance of their process is running. So if User A connects to the server, launches said process, then "Disconnects", and User B connects later on and tries to launch the same process, he may encounter an error message.
And obviously, when you "Disconnect" from a server, all the resources you used when you were logged in are still in use and won't be freed until you do a "Logoff", which could affect the system in the long run depending on its specs, and how many users connected to it and haven't logged off.
edited Apr 20 at 23:01
womble♦
86k18146205
answered Apr 20 at 20:05
AuraAura
1515
add a comment |
Personally, I always "Logoff" from a RDP connection, in order to avoid various issues, the biggest one being that my password could expire and if it does while I'm still "connected" to a server, then my account would enter an "account lockout" loop as it would constantly try to authentify to that server.
Another issue that can be avoided is that some programs have issues when more than one instance of their process is running. So if User A connects to the server, launches said process, then "Disconnects", and User B connects later on and tries to launch the same process, he may encounter an error message.
And obviously, when you "Disconnect" from a server, all the resources you used when you were logged in are still in use and won't be freed until you do a "Logoff", which could affect the system in the long run depending on its specs, and how many users connected to it and haven't logged off.
edited Apr 20 at 23:01
womble♦
86k18146205
answered Apr 20 at 20:05
AuraAura
1515
add a comment |
Personally, I always "Logoff" from a RDP connection, in order to avoid various issues, the biggest one being that my password could expire and if it does while I'm still "connected" to a server, then my account would enter an "account lockout" loop as it would constantly try to authentify to that server.
Another issue that can be avoided is that some programs have issues when more than one instance of their process is running. So if User A connects to the server, launches said process, then "Disconnects", and User B connects later on and tries to launch the same process, he may encounter an error message.
And obviously, when you "Disconnect" from a server, all the resources you used when you were logged in are still in use and won't be freed until you do a "Logoff", which could affect the system in the long run depending on its specs, and how many users connected to it and haven't logged off.
edited Apr 20 at 23:01
womble♦
86k18146205
answered Apr 20 at 20:05
AuraAura
1515
Personally, I always "Logoff" from a RDP connection, in order to avoid various issues, the biggest one being that my password could expire and if it does while I'm still "connected" to a server, then my account would enter an "account lockout" loop as it would constantly try to authentify to that server.
Another issue that can be avoided is that some programs have issues when more than one instance of their process is running. So if User A connects to the server, launches said process, then "Disconnects", and User B connects later on and tries to launch the same process, he may encounter an error message.
And obviously, when you "Disconnect" from a server, all the resources you used when you were logged in are still in use and won't be freed until you do a "Logoff", which could affect the system in the long run depending on its specs, and how many users connected to it and haven't logged off.
edited Apr 20 at 23:01
womble♦
86k18146205
answered Apr 20 at 20:05
AuraAura
1515
edited Apr 20 at 23:01
womble♦
86k18146205
edited Apr 20 at 23:01
womble♦
86k18146205
edited Apr 20 at 23:01
womble♦
86k18146205
86k18146205
answered Apr 20 at 20:05
AuraAura
1515
answered Apr 20 at 20:05
AuraAura
1515
answered Apr 20 at 20:05
AuraAura
1515
1515
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f958570%2fdisconnect-vs-sign-out-on-windows-rdc%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
How would it cost your company money?
– joeqwerty
Mar 16 at 14:17
i thought some cloud providers charged by user or login time
– Mike Palmice
Mar 16 at 14:26
Perhaps you should address the 10-15 minute logon performance issue. You're also not going to be able to differentiate between a session that the user disconnected, or a session that was disconnected from a network interruption.
– Greg Askew
Mar 16 at 14:36
Ok, but let's assume that none of the disconnected sessions were caused by network problems; also aren't the effects the same? w.r.t. 10-15 min logon, my user profile has been removed and reinstalled to no avail. I agree the long logon period is troublesome. I've posted a separate question here: serverfault.com/questions/958572/…
– Mike Palmice
Mar 16 at 14:45