Tracking Steam Login User for local machine

[Berman]

Hello everyone, I am not sure if this is the right place to post this, I never posted on Steam community before so take it easy on me.

But at my local university we have a new E Sports club and multiple machines. We current have it setup so students can login to the computers using their school accounts. But we running into a storage issue with a massive build up of user accounts on the C: drive. And deleting them from the PC will break the accounts and cause more headaches for us. (Idk why its a school policy thing).

My idea for fixing this is create a new local user account that everyone will login with, and each student will personally sign into their steam/battle net/etc accounts. So this de-clutters our user storage issue. But we need to be able to track who is actually signing into the computers per university rules.

my question,Is there a way to track and see, or maybe a log file in the hidden files in the Steam files that shows which accounts attempted or logged into the Steam application? This will allow us to just see who logged into at what day/time if an issue comes about and cover our ass per the university rules.

[MalikQayum]

the loginusers.vdf file shows user logins made on that pc.

"C:\Program Files (x86)\Steam\config"

"76561198034957967"
	{
		"AccountName"		"HIDDEN"
		"PersonaName"		"MalikQayum"
		"RememberPassword"		"0"
		"mostrecent"		"1"
		"Timestamp"		"1580979241"
		"WantsOfflineMode"		"0"
	}

timestamp only shows when a user logged in and not when logged off.
but since only one person can run the client at a time this should be no issue.
You can then keep a record of when people last "logged on".

you could also use the "mostrecent" key to find out which user is the most recent to had logged in.

(sidenote: this is a vdf format, so you would need to use a vdf parser.)

[ShelLuser]

Sounds quite dodgy to me though. IMO this is a perfect example why you should never log onto your Steam account using a public computer.

And offtopic: also poor systems administration. It shouldn't be too difficult to set up quotas which will limit the amount of storage available to the users. For example by setting up a NAS (or main server) where all data is being kept.