Set time limit for active but idle Remote Desktop Services sessions using registry without rebooting












0















This policy setting allows you to specify the maximum amount of time that an active Remote Desktop Services session can be idle (without user input) before it is automatically disconnected.



I'm trying to make registry changes as suggested here but it requires a reboot to take effect. Is it possible for the changes to take effect immediately without requiring a reboot?



HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
MaxIdleTime=60000


I have made the registry changes as above and also tried doing this via a group policy and then kept the server idle for more than a couple of minutes, but I still don't get the prompt like this.



I have tried logging off and then logging back in but still the changes doesn't getting applied. Only when I restart the server does the registry settings gets applied.



Idle Timer Expired










share|improve this question























  • Did you try restarting the appropriate service (the one that handles Remote Desktop Services)?

    – DavidPostill
    Feb 13 at 21:39











  • When I try to restart Remote Desktop Services using Restart-Service -Name TermService. I'm getting Restart-Service : Cannot stop service 'Remote Desktop Services (TermService)' because it has dependent services. It can only be stopped if the Force flag is set. Forcing it to stop makes the Remote Desktop Services session to end.

    – Ishan
    Feb 13 at 22:08













  • Is it possible this is an XY problem? It appears you're trying to change this setting while in a RDP session to the RDSH server. What exactly are you trying to accomplish?

    – Twisty Impersonator
    Feb 14 at 2:05











  • Try running gpupdate from a command prompt.

    – Joe
    Feb 14 at 3:30
















0















This policy setting allows you to specify the maximum amount of time that an active Remote Desktop Services session can be idle (without user input) before it is automatically disconnected.



I'm trying to make registry changes as suggested here but it requires a reboot to take effect. Is it possible for the changes to take effect immediately without requiring a reboot?



HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
MaxIdleTime=60000


I have made the registry changes as above and also tried doing this via a group policy and then kept the server idle for more than a couple of minutes, but I still don't get the prompt like this.



I have tried logging off and then logging back in but still the changes doesn't getting applied. Only when I restart the server does the registry settings gets applied.



Idle Timer Expired










share|improve this question























  • Did you try restarting the appropriate service (the one that handles Remote Desktop Services)?

    – DavidPostill
    Feb 13 at 21:39











  • When I try to restart Remote Desktop Services using Restart-Service -Name TermService. I'm getting Restart-Service : Cannot stop service 'Remote Desktop Services (TermService)' because it has dependent services. It can only be stopped if the Force flag is set. Forcing it to stop makes the Remote Desktop Services session to end.

    – Ishan
    Feb 13 at 22:08













  • Is it possible this is an XY problem? It appears you're trying to change this setting while in a RDP session to the RDSH server. What exactly are you trying to accomplish?

    – Twisty Impersonator
    Feb 14 at 2:05











  • Try running gpupdate from a command prompt.

    – Joe
    Feb 14 at 3:30














0












0








0








This policy setting allows you to specify the maximum amount of time that an active Remote Desktop Services session can be idle (without user input) before it is automatically disconnected.



I'm trying to make registry changes as suggested here but it requires a reboot to take effect. Is it possible for the changes to take effect immediately without requiring a reboot?



HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
MaxIdleTime=60000


I have made the registry changes as above and also tried doing this via a group policy and then kept the server idle for more than a couple of minutes, but I still don't get the prompt like this.



I have tried logging off and then logging back in but still the changes doesn't getting applied. Only when I restart the server does the registry settings gets applied.



Idle Timer Expired










share|improve this question














This policy setting allows you to specify the maximum amount of time that an active Remote Desktop Services session can be idle (without user input) before it is automatically disconnected.



I'm trying to make registry changes as suggested here but it requires a reboot to take effect. Is it possible for the changes to take effect immediately without requiring a reboot?



HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal Services
MaxIdleTime=60000


I have made the registry changes as above and also tried doing this via a group policy and then kept the server idle for more than a couple of minutes, but I still don't get the prompt like this.



I have tried logging off and then logging back in but still the changes doesn't getting applied. Only when I restart the server does the registry settings gets applied.



Idle Timer Expired







windows remote-desktop windows-registry group-policy windows-server






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 13 at 21:34









IshanIshan

1,43061429




1,43061429













  • Did you try restarting the appropriate service (the one that handles Remote Desktop Services)?

    – DavidPostill
    Feb 13 at 21:39











  • When I try to restart Remote Desktop Services using Restart-Service -Name TermService. I'm getting Restart-Service : Cannot stop service 'Remote Desktop Services (TermService)' because it has dependent services. It can only be stopped if the Force flag is set. Forcing it to stop makes the Remote Desktop Services session to end.

    – Ishan
    Feb 13 at 22:08













  • Is it possible this is an XY problem? It appears you're trying to change this setting while in a RDP session to the RDSH server. What exactly are you trying to accomplish?

    – Twisty Impersonator
    Feb 14 at 2:05











  • Try running gpupdate from a command prompt.

    – Joe
    Feb 14 at 3:30



















  • Did you try restarting the appropriate service (the one that handles Remote Desktop Services)?

    – DavidPostill
    Feb 13 at 21:39











  • When I try to restart Remote Desktop Services using Restart-Service -Name TermService. I'm getting Restart-Service : Cannot stop service 'Remote Desktop Services (TermService)' because it has dependent services. It can only be stopped if the Force flag is set. Forcing it to stop makes the Remote Desktop Services session to end.

    – Ishan
    Feb 13 at 22:08













  • Is it possible this is an XY problem? It appears you're trying to change this setting while in a RDP session to the RDSH server. What exactly are you trying to accomplish?

    – Twisty Impersonator
    Feb 14 at 2:05











  • Try running gpupdate from a command prompt.

    – Joe
    Feb 14 at 3:30

















Did you try restarting the appropriate service (the one that handles Remote Desktop Services)?

– DavidPostill
Feb 13 at 21:39





Did you try restarting the appropriate service (the one that handles Remote Desktop Services)?

– DavidPostill
Feb 13 at 21:39













When I try to restart Remote Desktop Services using Restart-Service -Name TermService. I'm getting Restart-Service : Cannot stop service 'Remote Desktop Services (TermService)' because it has dependent services. It can only be stopped if the Force flag is set. Forcing it to stop makes the Remote Desktop Services session to end.

– Ishan
Feb 13 at 22:08







When I try to restart Remote Desktop Services using Restart-Service -Name TermService. I'm getting Restart-Service : Cannot stop service 'Remote Desktop Services (TermService)' because it has dependent services. It can only be stopped if the Force flag is set. Forcing it to stop makes the Remote Desktop Services session to end.

– Ishan
Feb 13 at 22:08















Is it possible this is an XY problem? It appears you're trying to change this setting while in a RDP session to the RDSH server. What exactly are you trying to accomplish?

– Twisty Impersonator
Feb 14 at 2:05





Is it possible this is an XY problem? It appears you're trying to change this setting while in a RDP session to the RDSH server. What exactly are you trying to accomplish?

– Twisty Impersonator
Feb 14 at 2:05













Try running gpupdate from a command prompt.

– Joe
Feb 14 at 3:30





Try running gpupdate from a command prompt.

– Joe
Feb 14 at 3:30










0






active

oldest

votes











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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1405452%2fset-time-limit-for-active-but-idle-remote-desktop-services-sessions-using-regist%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1405452%2fset-time-limit-for-active-but-idle-remote-desktop-services-sessions-using-regist%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

Eduardo VII do Reino Unido