I've seen several post that claim that tasks, associated to a 6008 event, do not execute after a 6008 event, I have that same problem. I've also noticed that event 6005 executes after a 6008, 6005 is "The Event log service was started".
There is also an event in the event log 7036, "The Task Scheduler service entered the running state", that occurs even after that.
I don't see how the task in the task manager can run if the process is not even running.
So 3 questions
Is it possible to trap this 6008 event given the above, using the attach a task to an event available in the event log?
Is there a way of delaying the execution of the task attached to the event until everything is up and running
If not what is the most common method of sending notification of these types of event.
Please give examples using powershell
There is not a problem in the existing powershell logic as I have run the task successfully from the task scheduler