D
Doug Rothen
Guest
We are working with Windows 10 Enterprise edtion and something we've observed is that the Diagnostics-Performance Source, EventID 100 is not being logged when and if a user selects Start/Power/Shutdown or if they go to a CMD windows and type shutdown -s. It appears as though the only Diagnostics-Performance EventID 100 that will log is if the user conducts a restart. Either the Start/Power/Restart or CMD shutdown -r will generate an EventID 100. It typically takes about two minutes after a login to log in the eventviewer which makes sense but it does log.
I'm wondering if this is an expected behavior OR if I should expect to see an Diagnostics-Performane EventID 100 appear as part of a Cold Startup?
We use Aternity for monitoring of endpoints and we'd like to be able to monitor users boot/logon times from all situations. These events, if logged as part of a restart and a cold boot, would do the trick.
More...
I'm wondering if this is an expected behavior OR if I should expect to see an Diagnostics-Performane EventID 100 appear as part of a Cold Startup?
We use Aternity for monitoring of endpoints and we'd like to be able to monitor users boot/logon times from all situations. These events, if logged as part of a restart and a cold boot, would do the trick.
More...