Best Practices Question
K1000 Aggressive Patching schedule, how aggressive can you get?
07/09/2015 2623 views
I'm trying to do something similar to this: https://support.software.dell.com/k1000-systems-management-appliance/kb/147524
I do a scripted install on my K2000, during which the machine gets domained and put in to a New Installs OU. I set up a patching schedule on the K1000 to patch any machine in this OU. There are never any machines in here but newly built ones, so I can be as aggressive as I want. I set my schedule to detect and deploy every 10 minutes, but nothing happens. I set it to 2 hours, and my machine is still patching when I came in this morning sitting on update 158 of 196 on a please don't power off your machine screen.
I'm running about 200-250 patches, as these are from a Windows 7 SP1 build right off the Microsoft ISO with Office
My question is, if I set my detect and deploy time to 10 minutes, will the next detect and deploy interrupt the first, causing the machine to sit there interrupting itself over and over? If so, how fast can I set my schedule? The article I linked mentions 30 minutes to an hour, but if these detect and deploys can interrupt themselves I may have to make it 2-3 hours, or longer. The longer I make it however, the longer my machine initially sits in the New Installs OU not getting patched.
I'm not interested in slipstreaming patches, using imaging, or using WSUS offline. I'm having no problems seeing the machines I want to patch so I don't need help with smart labels or ldap labels. Thank you for your time.