Hi mike. Thanks for the tip. The challenge is that the data is generated only when the application shuts down gracefully, the user logs off totally and there is a 5 minute interval to ensure the data gets to the server. The only way I see we can ensure these things happen is when VCL gives a window to perform some tasks before the reclaim. I was thinking along the lines of how we could have some scripts under tools to be run for specific versions of windows or driver installation. That way the actual script could be separated from the vcl application and could be customized per use case.
Thanks. Junaid Ali On Apr 24, 2014 5:01 PM, Mike Haudenschild <[email protected]> wrote: Junaid, You might try writing that data to a filesystem that's outside VCL and just gets mounted by the VCL VMs, along the lines of creating a "thaw space" when using the lab-locking software DeepFreeze: https://tracermedia.atlassian.net/browse/MCHLEM-307 If your VCL VMs are on your LAN in such a way that they can get to a fileserver where LabStats knows to write its data, it could be a workaround for the more complicated task of changing VCL's reclaim behavior. Regards, Mike On Thu, Apr 24, 2014 at 5:49 PM, Junaid Ali <[email protected]> wrote: > Hello, > > When a user's reservation ends, the VM's are reloaded immediately with the > next image. This includes hard powering off of the VM and any running user > session is lost. We use Labstats to track application usage and user login > times, that depends on a graceful logoff and shutdown of applications to > record usage data. This hard powering off of the VM causes much of the > LabStats data to be lost. Is there a way to hookup processes (e.g. > unreserve) that run at the end of the reservation, maybe like an opposite > of reserve() routine. Would there be enough interest in having this > functionality in the core software, so we don't diverge from the community? > > FYI, we are using VCL 2.2 and plan on an upgrade to 2.3.2 this summer. > > Any thoughts? > > > > Junaid Ali > > >
