First district-wide patching job attempt

Over the weekend, I have attempted to run a district-wide patch job.  (excluding anyone in the 10.40.52. range, as well as all the server IP ranges)
This included Adobe Security criticals, MS Office security criticals, Windows XP security criticals, and Windows 7 security criticals.

There is bad news and good news:

• The good news is that 100% of the patches have deployed successfully. Of course, that is excluding all patches that will revert back after reboot on all the deepfreeze labs, as well as one particular Adobe Air patch which failed globally. Other than that, everything went through. So I would say this is actually excellent success.
• The bad news, which is potentially good news if we deal with it, is that, out of 2400 computers that I targeted for the patching schedules, only 10% were actually available over the weekend for patching. 

Of course, from my experience over the weekend, I believe that the most effective way of targeting patching is with this method, as opposed when users are at work during the day, as we can do both a detect AND a deploy at the same time.

At this point, it is just a matter of figuring out how to target machines so that they are on, and so that they are thawed when we are trying to patch them.