Search

Language:  

Available article translations:

Licensing Mechanism in Remote Appication Server.

APPLIES TO:
  • Parallels Remote Application Server

Question

Is there a way to make user logoff the session (and release the license) when user closed the published application?

Resolution

Remote Application Server licenses are based on the RDP sessions on the RDSH (Remote Desktop Session Host, Terminal Service)

When all published applications are closed from the client side, the RDP session itself remains open for 20 seconds by default. During this period, the license is still consumed.

This is done so that if a user launches an other app the same session could be used and the repose time for the user is much faster.

When the session disconnects (TSClient.exe closes) the license is released.

There is no way to force it using RAS settings, sorry.

You may try to set Session Time Limits using GPO as described here:

https://technet.microsoft.com/en-us/library/cc753112(v=ws.10).aspx

Should you want to change this amount, do the following:

NOTE: "Use Remote Apps" feature must be disabled on the each server, as this is another mechanism and will work in different way.

Go to RAS Console > right click on Terminal Server > Properties > Agent Settings > Publishing Session timeout. Please note that the lower amount is 20 seconds, you need to type it manually.

alttext

NOTE: You need to use this set for ALL Terminal Servers.

For example you have set it to 1 minute, license will be released after 1 minute + couple of seconds ( slight delay caused by timeout between Publishing Agent and Licensing Server)


Also, to make sure that user closed RDP Client after he completed his work with published apps:

On the RDP Client go to Connection properties > Advanced settings> Connection Advanced settings > Connection Timeout.

alttext

For example, you may change this amount to 1. It means that once customer closes all published apps - RDP Client closes either almost immediately (after 1 second).




1d70d1f9c41d01c5f7202a4290e434e1

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No