Dear All,

ADAGIO Module - Active Users - Not clearing.

Disconnected RDS sessions is the cause of my issue.

My only solution is to reset Server.

Is there not any tool, or a list of temp files I can replace or edit to close Active Users from ADAGIO without needing to re-start the server ?

Any help welcomed ..

IT can setup a script to signoff all the sessions at certain time of the day or by Windows setting after they have been idle for certain amount of minutes. I don't recommend the latter because the users might be in a morning meeting for 4 hours and system will log them off.

Thanks Patricia,

I actually do that now, but for some reason I still have disconnected users who I have ((signed off)) still appearing in my Adagio Active Users listing.

** I a using a Virtual Machine running Server 2019 **.

...

** Script to disconnect Sessions **
query session | findstr "Disc" | findstr /V "administrator, services" >C:\logoff\sessionDisc.txt
for /f "tokens=2" %%I in (C:\logoff\sessionDisc.txt) DO logoff %%I
del C:\logoff\sessionDisc.txt

...

..

I need a manual way to LOG OFF users from Adagio that gets stuck, without having to Re-Start Server ..
Current method to shutdown server not ideal.


Regards
Edward

I've had this issue in some of my RDS servers and I can usually log in to the Admin user and kill the Adagio modules from the Task Manager>Details tab.
As a preventative measure, I've also given the users a shortcut button on their desktop to "Sign out" of the RDS instead of closing it and leaving the user session running.

Hi Edward:

Are all your users running Adagio from the RDS server? Or do you have land users?

Thanks Patricia and Dan, the RDS Server is managed by another (Company) and they put me (Adagio) on a Windows Server Virtual Machine. So all operates in a shell, however the connect the Users are Authenticated from the DC on the Main Server. Hence I think this is why (Disconnected Users) can not get back into the SAME Windows Session they had before..(I think).. On the matter of ADAGIO GHOST users, I remembered a hint (Terry IMS) gave me to delete the (EZSEMADS.?DAT?) file once all users are out of the system.

Hi edward:

It is normal behaviour of an RDS server create a new session number everytime the user logs off and logs back in.

Do you mean under a VM, because my other installs that is on a regular server running RDS does not do that. Users are able to login from multiple machines and (( resume )) work on any Adagio Program Screen they were prior to disconnection... This is my only "forced on me" VM (Virtual Machine) install.

The key thing for me is I figured out how clear ACTIVE GHOST USERS in ADAGIO without restarting the server...

Hi Edward:

I said logged off. If they disconnect, they get in the same session than before.
Yes, you can delete EZSEMADS.XXX when nobody is in the system if you have ghost users.

Hi Edward,
If your user ID connection to the Remote Desk Session has admin rights, you will be able to open the Task Manager as mentioned above, and simply go the the Details Tab, and sort by user or by application, and highlight the task that needs to be closed and close item by clicking on End Task button on the lower right bottom of the window.

Do so with care, because this will end any task without checking on whether the user is posting or not. Normally, you can tell if the session is active with the CPU % moving around or memory useage is moving around or looking at the I/O activity. If you close an active posting session, you will normally corrupt the data.

We often see these phantom user sessions within Gridview that somehow doesn't always close out the session when the process has ended for the workspace.

For most of our client sites that we support on Remote DeskTop, we insist with the IT that we have that ability to End Tasks, which is far superior to rebooting the server.

If the specific issue relates to a Printing job that is lost in the Twilight Zone, you can also open up services on the server, and stop/restart the Print Spooler, which will kill reset all queued print jobs. Again do so with care, because there may be valid print jobs in the print queue that need to be printed and may need to be reprinted.

As Dan has suggested, if this is a recurring issue with users not signing out of their sessions which can happen with situations of many remote uses, the shortcut sign out icon is a good suggestion to reduce the frequency of open Adagio sessions when users need to end their session.

For large sites, we also do the Windows script to close our all users window sessions every night but that still does not close out the phantom Adagio users.

Best,
Brian