By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AppStream 2.0 Session Disconnect timeouts per user

0

We have a Stack/Fleet working well with 12 hour disconnect timeout and 0 idle disconnect timeout. The issue is that only a few users need to keep processing apps running for many hours after they disconnect. No one ever uses the end session option so looking for a way to save money without creating more stacks and fleets.

If disconnect timeout was controlled (or could be overridden) by GPO RDP settings it would be very easy to give one group of users 12 hours and another group of users 2 hours etc on the same fleet but this is not the case. It would be possible to push a scheduled task to machines running the 2 hour users to kill them after 2 hours idle time, but Appstream doesn't handle manually killed sessions very well.

I'm looking for any other suggestions that don't involve creating a bunch of duplicate stack/fleets that are already complicated to implement and manage just for different user disconnect timeouts. I think it could be done by doing API calls so often that describe the fleet and note and track sessions with NOT_CONNECTED and send an expire-session --session-id command to machines that meet a certain username and disconnected time limit but alas, this is perhaps more complicated than more stacks and fleets.

This was a similar question but there didn't seem to be a solution. https://repost.aws/questions/QUa1I7wmzhRL-k6YFYP1ozTA/which-service-process-deems-when-to-kill-an-ongoing-appstream-session

**The TLDR is that we just want a way for an application running on a Windows Appstream to call a process when it completes to end the Appstream session. **

  • rePost-User-1579460
    5 months ago

    A solution could be created if there was a way to call the "End Session" feature/button from inside the user's Windows session.

Topics
End User Computing
Tags
Amazon AppStream
Language
English
rePost-User-1579460
asked 5 months ago285 views
1 Answer
0

Hello,

Photon Agent is responsible for communicating the session state to the backend service.

However, if the fleet is domain joined, GPO can be used to an extent.

You can join your Amazon AppStream 2.0 Always-On and On-Demand Windows fleets and image builders to domains in Microsoft Active Directory and use your existing Active Directory domains, either cloud-based or on-premises, to launch domain-joined streaming instances.

By joining AppStream 2.0 to your Active Directory domain, you can [1]:

  • Use Group Policy settings that are available in the Group Policy Management Console (GPMC) to define the end user experience.

References [1] https://docs.aws.amazon.com/appstream2/latest/developerguide/active-directory.html

AWS
LMarhawu
answered 5 months ago
  • rePost-User-1579460
    5 months ago

    Thank you for responding. I am able to use GPO's on our domain joined On-Demand fleet. I don't believe there are any GPO setting that can control or over override the default fleet disconnect timeout setting.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content