Best Practices Question
What are your experiences with patch detection (and deployment)?
10/13/2015 1971 views
So I've prepared patching on the K1000aaS; subscriptions, labels, tested it within IT to get a feel for the process, implemented it on servers. That part is fine.
When I first turned on detect for all computers, ~1150, the K1000 was getting crushed. The load average under Settings > Provisioning > Communication Settings was unbelievably high. 80 was the high score. On a scale of 10. I understand that the first detect generated a lot more data, and all of it hitting at once was probably not good, so I changed the schedule from a specific time, to be once every 24 hours, and now it's only reporting new missing patches, and the computers are naturally staggered throughout the day.
I was always told that detects are a very minor task, and doesn't require many resources, which is why I turned it on with a set schedule. (Users have never noticed anything.) Even though things have calmed down, I still see the load average above 10 or even 20, while the Security > Schedules page shows maybe 50 detects executing, give or take.
When I turn on patching, I plan on having it run at night, so it doesn't impact things during the workday.
The only other things I have running are Inventory and one service desk queue. No scripts, no installations, no provision schedules, no network discovery, no monitoring.
I have a ticket open with support, but they've only said they don't see anything wrong, and I don't feel like I'm getting much help from them.
Environment: K1000 as a service, version 6.3, replication shares in each remote office.
So my questions for anyone are:
Have you seen similar load while doing detects? Does this seem normal?
How are your detects/deploys staggered?