• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Determine how long a use has been logged in XP (maybe by SCCM?)

TEEZLE

Platinum Member
Basically, need a way to find out how long a user has been logged into a Windows XP system. We want to reboot them if it has been longer than 30 days. It would be great to be able to push a script from SCCM and have it report some how. Or is there a SCCM report that I can run (I can't seem to find it if there is).

Thanks in advance.
 
Last edited:
You used to be able to read "Up Time" via the command line "Systeminfo" command, too. With a script, you could run the command, interpret the result, and tell the PC to reboot if the result exceeds a month.

systeminfo|find "Up Time"

Or something like that. In Win7, I see that a Systeminfo searched for "Boot Time" will give you when the last reboot occurred.
 
Last edited:
hell yeah, if you surf porn you'll need to reboot often.. i have systems here thats been running for 3-4 months.. its xp system.. dont need to reboot it except for patches and stuff..

drop to command, run systeminfo | more and it'll show system up time..

systeminfo /s <machine name> gives you remote users...

you can write a little perl script that reads the machine up time and do a shutdown -r -m \\ <machine> name if it's over 30 days, etc..
 
actually maybe I dont know, you asked for logged in time.. thats different from up time... I dont know how to figure out logged in time because I never had to.. if i find out ill let you know.. maybe someone else here knows..
 
Thanks for all the info guys. For some reason systeminfo is blocked by polcy, keeps saying access denied. I found the jist of what they are trying to do. Essentially, we do a lot of updates when "no user is logged in" with SCCM. Since the packages only can't run with them logged in, we want a way to log them off (but not reboot because of Safeboot).

I don't think it's all that necessary, but our gov. security guy is pushing us to do it!
 
Back
Top