- Dec
- 54
- 2
Hi folks, it's been a LONG time since I've been here!
Topic: How to detect (and log) when another application forces a windows restart?
Scenario: I work heavily in my privately licensed copy of TCmd in my job as software engineer. I have it set up so that my command log has in it only "major" events so I can use it to recollect what I might have done two days ago, or what kinds of system interruptions have occurred (WAN connection lost and restored, that sort of thing). Sometimes our IT remotely forces a reboot using a small application we have installed. (I don't have info on that application at present, but I can get it.) When this happens, it is sometimes hard to distinguish between a forced reboot in my absence, a system reboot due to a crash, or something else having happened.
I'd really like to get some details into the command log when that happens, so that I'm not faced with a mystery that I "just have to accept." (Obviously this is not possible during a system crash, but if I can log other scenarios, then the absence of those logs would clearly indicate "system crashed.")
How can I detect when another application forces a windows restart? Preferably, I'd like a belt-and-suspenders approach so that it doesn't matter WHICH application forces it, it gets logged.
Thanks, folks! Hope this is an interesting problem that will be useful to others!
Topic: How to detect (and log) when another application forces a windows restart?
Scenario: I work heavily in my privately licensed copy of TCmd in my job as software engineer. I have it set up so that my command log has in it only "major" events so I can use it to recollect what I might have done two days ago, or what kinds of system interruptions have occurred (WAN connection lost and restored, that sort of thing). Sometimes our IT remotely forces a reboot using a small application we have installed. (I don't have info on that application at present, but I can get it.) When this happens, it is sometimes hard to distinguish between a forced reboot in my absence, a system reboot due to a crash, or something else having happened.
I'd really like to get some details into the command log when that happens, so that I'm not faced with a mystery that I "just have to accept." (Obviously this is not possible during a system crash, but if I can log other scenarios, then the absence of those logs would clearly indicate "system crashed.")
How can I detect when another application forces a windows restart? Preferably, I'd like a belt-and-suspenders approach so that it doesn't matter WHICH application forces it, it gets logged.
Thanks, folks! Hope this is an interesting problem that will be useful to others!
