Local computer policy not working












0















The policy appears in gpresult



I have a domain-joined computer that I'm trying to add a local policy to end RDP sessions after being disconnected for a certain amount of time. I'm not sure if I'm doing it correctly but I've tried adding the registry key MaxDisconnectionTime, in "HKLMSoftwarePoliciesMicrosoftWindows NTTerminal Services" and I can see it in regedit. I set it to one minute to test it, but the RDP session does not seem to end after that time has passed. Why could this be and how do I fix it? Keep in mind I have no previous experience with this, and I don't want to add this feature through AD, it has to be local.










share|improve this question























  • How is the domain policy set? Does it create a conflict with the local policy? Edit your question instead of submitting a comment.

    – Ramhound
    Mar 1 at 14:34
















0















The policy appears in gpresult



I have a domain-joined computer that I'm trying to add a local policy to end RDP sessions after being disconnected for a certain amount of time. I'm not sure if I'm doing it correctly but I've tried adding the registry key MaxDisconnectionTime, in "HKLMSoftwarePoliciesMicrosoftWindows NTTerminal Services" and I can see it in regedit. I set it to one minute to test it, but the RDP session does not seem to end after that time has passed. Why could this be and how do I fix it? Keep in mind I have no previous experience with this, and I don't want to add this feature through AD, it has to be local.










share|improve this question























  • How is the domain policy set? Does it create a conflict with the local policy? Edit your question instead of submitting a comment.

    – Ramhound
    Mar 1 at 14:34














0












0








0








The policy appears in gpresult



I have a domain-joined computer that I'm trying to add a local policy to end RDP sessions after being disconnected for a certain amount of time. I'm not sure if I'm doing it correctly but I've tried adding the registry key MaxDisconnectionTime, in "HKLMSoftwarePoliciesMicrosoftWindows NTTerminal Services" and I can see it in regedit. I set it to one minute to test it, but the RDP session does not seem to end after that time has passed. Why could this be and how do I fix it? Keep in mind I have no previous experience with this, and I don't want to add this feature through AD, it has to be local.










share|improve this question














The policy appears in gpresult



I have a domain-joined computer that I'm trying to add a local policy to end RDP sessions after being disconnected for a certain amount of time. I'm not sure if I'm doing it correctly but I've tried adding the registry key MaxDisconnectionTime, in "HKLMSoftwarePoliciesMicrosoftWindows NTTerminal Services" and I can see it in regedit. I set it to one minute to test it, but the RDP session does not seem to end after that time has passed. Why could this be and how do I fix it? Keep in mind I have no previous experience with this, and I don't want to add this feature through AD, it has to be local.







windows-10 remote-desktop windows-registry group-policy






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 1 at 10:58









knifeislifeknifeislife

1




1













  • How is the domain policy set? Does it create a conflict with the local policy? Edit your question instead of submitting a comment.

    – Ramhound
    Mar 1 at 14:34



















  • How is the domain policy set? Does it create a conflict with the local policy? Edit your question instead of submitting a comment.

    – Ramhound
    Mar 1 at 14:34

















How is the domain policy set? Does it create a conflict with the local policy? Edit your question instead of submitting a comment.

– Ramhound
Mar 1 at 14:34





How is the domain policy set? Does it create a conflict with the local policy? Edit your question instead of submitting a comment.

– Ramhound
Mar 1 at 14:34










1 Answer
1






active

oldest

votes


















0














I would recommend using the local group policy editor instead, then navigating this path



Computer Configuration, Admin Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits.



Once done, run cmd command gpupdate /force to push the new gp config.



Hope this helps.






share|improve this answer
























  • I tried this method as well and it seems to have no effect as well, even though the policy does seem to apply according to gpresult

    – knifeislife
    Mar 1 at 12:05











  • Have you tried running it through the user config rather than computer, to see if it makes a difference? or check to see if there is any GPO that is attached to the OU of the domain that takes precedence over the LGPO. I know there are certain hierarchical elements.

    – jimbob
    Mar 1 at 12:23











  • I have now tried doing it through user config and it shows up in gpresult and rsop.msc, still seems to have no effect on the RDP session. It doesn't seem like there's any GPO that has precedence directly over the LGPO either. The only GPO I could find on the PDC related to session time limits was one that enables the screensaver after a certain amount of time. for some reason the RDP session completely ignores my local policies.

    – knifeislife
    Mar 1 at 14:02












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%2f1410436%2flocal-computer-policy-not-working%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









0














I would recommend using the local group policy editor instead, then navigating this path



Computer Configuration, Admin Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits.



Once done, run cmd command gpupdate /force to push the new gp config.



Hope this helps.






share|improve this answer
























  • I tried this method as well and it seems to have no effect as well, even though the policy does seem to apply according to gpresult

    – knifeislife
    Mar 1 at 12:05











  • Have you tried running it through the user config rather than computer, to see if it makes a difference? or check to see if there is any GPO that is attached to the OU of the domain that takes precedence over the LGPO. I know there are certain hierarchical elements.

    – jimbob
    Mar 1 at 12:23











  • I have now tried doing it through user config and it shows up in gpresult and rsop.msc, still seems to have no effect on the RDP session. It doesn't seem like there's any GPO that has precedence directly over the LGPO either. The only GPO I could find on the PDC related to session time limits was one that enables the screensaver after a certain amount of time. for some reason the RDP session completely ignores my local policies.

    – knifeislife
    Mar 1 at 14:02
















0














I would recommend using the local group policy editor instead, then navigating this path



Computer Configuration, Admin Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits.



Once done, run cmd command gpupdate /force to push the new gp config.



Hope this helps.






share|improve this answer
























  • I tried this method as well and it seems to have no effect as well, even though the policy does seem to apply according to gpresult

    – knifeislife
    Mar 1 at 12:05











  • Have you tried running it through the user config rather than computer, to see if it makes a difference? or check to see if there is any GPO that is attached to the OU of the domain that takes precedence over the LGPO. I know there are certain hierarchical elements.

    – jimbob
    Mar 1 at 12:23











  • I have now tried doing it through user config and it shows up in gpresult and rsop.msc, still seems to have no effect on the RDP session. It doesn't seem like there's any GPO that has precedence directly over the LGPO either. The only GPO I could find on the PDC related to session time limits was one that enables the screensaver after a certain amount of time. for some reason the RDP session completely ignores my local policies.

    – knifeislife
    Mar 1 at 14:02














0












0








0







I would recommend using the local group policy editor instead, then navigating this path



Computer Configuration, Admin Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits.



Once done, run cmd command gpupdate /force to push the new gp config.



Hope this helps.






share|improve this answer













I would recommend using the local group policy editor instead, then navigating this path



Computer Configuration, Admin Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits.



Once done, run cmd command gpupdate /force to push the new gp config.



Hope this helps.







share|improve this answer












share|improve this answer



share|improve this answer










answered Mar 1 at 11:38









jimbobjimbob

228




228













  • I tried this method as well and it seems to have no effect as well, even though the policy does seem to apply according to gpresult

    – knifeislife
    Mar 1 at 12:05











  • Have you tried running it through the user config rather than computer, to see if it makes a difference? or check to see if there is any GPO that is attached to the OU of the domain that takes precedence over the LGPO. I know there are certain hierarchical elements.

    – jimbob
    Mar 1 at 12:23











  • I have now tried doing it through user config and it shows up in gpresult and rsop.msc, still seems to have no effect on the RDP session. It doesn't seem like there's any GPO that has precedence directly over the LGPO either. The only GPO I could find on the PDC related to session time limits was one that enables the screensaver after a certain amount of time. for some reason the RDP session completely ignores my local policies.

    – knifeislife
    Mar 1 at 14:02



















  • I tried this method as well and it seems to have no effect as well, even though the policy does seem to apply according to gpresult

    – knifeislife
    Mar 1 at 12:05











  • Have you tried running it through the user config rather than computer, to see if it makes a difference? or check to see if there is any GPO that is attached to the OU of the domain that takes precedence over the LGPO. I know there are certain hierarchical elements.

    – jimbob
    Mar 1 at 12:23











  • I have now tried doing it through user config and it shows up in gpresult and rsop.msc, still seems to have no effect on the RDP session. It doesn't seem like there's any GPO that has precedence directly over the LGPO either. The only GPO I could find on the PDC related to session time limits was one that enables the screensaver after a certain amount of time. for some reason the RDP session completely ignores my local policies.

    – knifeislife
    Mar 1 at 14:02

















I tried this method as well and it seems to have no effect as well, even though the policy does seem to apply according to gpresult

– knifeislife
Mar 1 at 12:05





I tried this method as well and it seems to have no effect as well, even though the policy does seem to apply according to gpresult

– knifeislife
Mar 1 at 12:05













Have you tried running it through the user config rather than computer, to see if it makes a difference? or check to see if there is any GPO that is attached to the OU of the domain that takes precedence over the LGPO. I know there are certain hierarchical elements.

– jimbob
Mar 1 at 12:23





Have you tried running it through the user config rather than computer, to see if it makes a difference? or check to see if there is any GPO that is attached to the OU of the domain that takes precedence over the LGPO. I know there are certain hierarchical elements.

– jimbob
Mar 1 at 12:23













I have now tried doing it through user config and it shows up in gpresult and rsop.msc, still seems to have no effect on the RDP session. It doesn't seem like there's any GPO that has precedence directly over the LGPO either. The only GPO I could find on the PDC related to session time limits was one that enables the screensaver after a certain amount of time. for some reason the RDP session completely ignores my local policies.

– knifeislife
Mar 1 at 14:02





I have now tried doing it through user config and it shows up in gpresult and rsop.msc, still seems to have no effect on the RDP session. It doesn't seem like there's any GPO that has precedence directly over the LGPO either. The only GPO I could find on the PDC related to session time limits was one that enables the screensaver after a certain amount of time. for some reason the RDP session completely ignores my local policies.

– knifeislife
Mar 1 at 14:02


















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%2f1410436%2flocal-computer-policy-not-working%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

How do I know what Microsoft account the skydrive app is syncing to?

When does type information flow backwards in C++?

Grease: Live!