I think I don't understand something. it's like sometimes a computer needs to be rebooted before its can be rebooted. Does that invalidate what I am trying to do? I don't want two reboots, let alone one that's in your face and the second normal. I understand the machine might be in a state where it requires a reboot when this hits them. If so, does that mean I cant really use this? Or do I just not have the combination down.
We were looking into using something like this to schedule a reboot of all machines up x number of days. I know that it will be based on a inventory scan that only runs once a day and not real time. But I was still thinking of using this because our GPO guy is too busy with other items.
Figured it out. We actually had a rogue agent out there on some machines. Not really rogue. How about deployed, updated but update missed. So it WAS doing the initial reboot with the in your face no deferral reboot because that is agent default.
So. my thoughts were right. it needed to run a reboot before it could run shutdown.exe (Yeah, right) It got the In your face reboot from the errant default on rogue agent which essentially said "Hey I need to step in and run this default reboot before I can process your package." Then, after reboot, the nice deferral reboot because that's whet was set on the shutdown,exe delivery.
I realized also that that's why it is best to run only a essentially empty batch file with reboot always in deployment. So I wont get the dual reboot. So, scratch shutdown.exe And to top off, run just as a PUSH and not a policy supported push because sometimes the task appears to fail and just to be sure it never runs again where not needed, make it push only (This may have just been a feel good and not necessary)
So, thanks me for the help. Anytime.