On 13 October 2010 18:37, Kevin Davison <[email protected]> wrote: > We have a large number of XP Virtual Machines that are used for various > software testing requirements. The testers are supposed to notify their > supervisor when an XP instance is no longer required. Unfortunately that > isn’t working very well. The end result is that there are a large number of > XP instances sitting doing nothing for long periods of time. Ideally, I’d > love to receive a notification in the event that any XP instance hasn’t been > used for x period of time. > > > > As the machines are accessed by the testers solely via RDP, I was thinking > that if I could determine how long it had been since someone had logged into > the machine I would be able to judge which machines had been abandoned and > remove them. > > > > I was mulling over using a WMI check to pull what I need from > Win32_NetworkLoginProfile but I’m not getting anything returned that I know > how to make use of. > > > > Has anyone had a need to perform a check like this in the past or can anyone > offer any advice as to where else I should start looking?
Is an entry made in one of the Windows Event Logs whenever a user logs in? If so I guess you could use CheckEventLog in NSClient++ to warn if there have been no logins in x days. For an example, see the section "Check if a script is running as it should" on the page describing the old syntax: http://www.nsclient.org/nscp/wiki/CheckEventLog/CheckEventLog/old hth, Jim ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
