How to disconnect and logoff idle remote sessions on windows server

Подписаться 9 тыс.

Просмотров 7 тыс.

50% 1

Learn how to disconnect and logoff idle remote sessions using group policy. In this example, I show you how to disconnect and then logoff idle remote sessions on windows servers by deploying a group policy to all servers.
Hi, I’m Danny, a London based IT consultant and blogger. You can view all my blog posts at: www.dannymoran.com

Наука

Опубликовано:

24 ноя 2023

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 11

@OldFellaDave 7 месяцев назад

One of my biggest annoyances ... idle RDP sessions ... this fixes that! Should be a basic requirement of any decent RDP deployment. Nice one Danny ;)

@danny_moran 7 месяцев назад

The main reason I initially implemented this was due to automated patches and updates failing to complete as the system wouldn't reboot automatically due to sessions being left logged in. This change has saved many hours of logging into servers to see why patches didn't get applied. It also returns any of the allocated session resources back to the server, often giving it slightly better performance. Thanks for watching, Dave!

@danielselvakumar7146 3 месяца назад

Hi, thanks for the video, Danny

@danny_moran 3 месяца назад

Thanks for watching!

@andrewenglish3810 7 месяцев назад

This is great for RDP sessions, as for servers were Admins someones forget to log out it can be problematic if some of those servers require a service account to be logged in to run some services that cannot be run as Windows services.

@danny_moran 7 месяцев назад

Yes, you would have to exclude any service accounts that have to be left logged in and cant be setup as an actual windows service. Thanks for watching!

@noyan5 3 месяца назад

I have attempted various methods, but only the administrator account logs off upon disconnect, while none of the user accounts seem to do so. Any insights on why this might be happening would be greatly appreciated.

@danny_moran 3 месяца назад

I've not seen this issue. It should work fine for all user accounts as the GPO is applied to the machine and not to a user.

@jeffreyooi1971 6 месяцев назад

Hi, thanks for the video. I have followed your steps and tested it on our AD. After idle for 1 minute, it has a pop-up message saying: "Session has been idle over its time limit. It will be disconnected in 2 minutes. Press any key now to continue the session". Why your video doesn't have a pop-up message but mine has? After 2 minutes, has another message pop-up: [Window Title] Remote Desktop Connection [Content] Your Remote Desktop Services session ended because the remote computer didn't receive any input from you. [^] Hide details [OK] [Expanded Information] Error code: 0x3 Extended error code: 0x3 Timestamp (UTC): 12/11/23 01:36:39 AM Press Ctrl+C to copy.

@danny_moran 6 месяцев назад

Depending on what tool you are using to connect to the session, it may or may not show the popup message. My demo was using the Hyper-V connection terminal, which is why it might look slightly different and didn't show the popup message. I forgot there was a popup message for the RDP client, as it's been a while since I've had an RDP session disconnected by this policy. The actual policy should still act in the same way regardless of the client used to connect to the session. Thanks for watching!

@jeffreyooi1971 6 месяцев назад

@@danny_moran type I am using the RDP instead of hyper-v connection. Anyway thanks.. 👍👍👍